Application programmers can't do that at all. SAF controlled, no way around it. Only initiators on test/QA LPAR are open to them.
System programmers and DBA's have different rules. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Karen Herle Sent: Wednesday, January 07, 2015 1:28 PM To: [email protected] Subject: How Does Your Shop Limit Testing in the Production LPAR Hi All, 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. Any and all comments welcome. This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
