On Wed, 7 Jan 2015 12:28:25 -0600 Karen Herle <[email protected]> wrote:
:>I am curious about how other mainframe shops deal with AD-HOC and test batch jobs that run in the PRODUCTION LPAR. :>We have encountered several issues with programmers or DBAs running non production jobs on our production LPAR which cause CPU resource issues or DB2 contention issues that have resulted in performance degradation to our CICS and production batch jobs. :>How does your shop deal with this? Do you restrict access to your production LPAR? Are there processes to follow to request test or data mining, non production jobs in your production LPAR? Do you use your security product (RACF/ACF2) to control the access to production data? :>We are actively looking at our options at this time and I am trying to balance the need for programmers to access the production environment but also need to protect our 4 hour rolling average and contention with DB2/CICS. Simply do chargebacks with production time being at a premium. EMAIL daily reports when numbers are out of average. Let the local management police their own people. -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
