Thank you for all of the suggestions! How do you communicate these restrictions to your developer community? Do you have published policy/process documents?
Karen A. Herle Computing Infrastructure San Diego Gas & Electric Southern California Gas Company 1801 S. Atlantic Blvd., SC711B Monterey Park, CA 91754 Phone: (323) 265-5189 Email: [email protected] -----Original Message----- From: Karen Herle [mailto:[email protected]] Sent: Wednesday, January 07, 2015 10:28 AM To: [email protected] Cc: Herle, Karen A. 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 email originated outside of Sempra Energy. Be cautious of attachments, web links, or requests for information. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
