Hi:
We did it very simply by jobclass. Only authorized users were allowed
to use production jobclasses. This was enforced by simple exits and
easy checks for accounting codes and SMF exits (and jes exits). We
were a shop where it was easy to differentiate between test and
production. The key was to have strict stands and without standards
it is a lot harder.
Ed
On Jan 7, 2015, at 12:28 PM, Karen Herle wrote:
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.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
