Thank you all for your suggestions. We do have separate LPAR and DB2 subsystems for testing. This works for the most part. When they behave. We do have a WLM class that puts any non production job in a very low resource class. This helps too but still we can have batch jobs negatively impacting production.
To complicate matters, production data owners are approving data security requests for programmer access to production data. The data owners are the business clients and any security access request must be approved by them. Here is part of the problem, they approve. So now programmers have access to production data. One in house suggestion was to prevent all programmers from logging onto the production lpar. That "bully" method may not be the best since they are still responsible for their production applications and may need to logon for support. I think if we only allow test jobs to run in initiators that have been started on the development lpars only, that would limit the risks to production . ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
