On Sun, 4 Oct 2009 10:14:59 -0500, Rick Fochtman wrote: > >> - You are NOT allowed to submit production jobs / reruns from your TSO (must >>> go through the job scheduler) > >Absolutely agree. > >>> - You are NOT allowed to submit test jobs using a production jobname. >>> Period. No discussion. Not even on a separate system. >> At first I agreed, but I'm reconsidering.
>Bizarre. Why not? > Some characteristic might be better than jobname. What about jobclass? And I still think about OWNER. Either production jobs run with job scheduler as OWNER, or job scheduler has sufficient authority to control the OWNER of submitted jobs. Some programmers might have both test and production IDs. The production IDs would have no RACF TSO segments, guranteeing that production jobs are not submitted from TSO sessions. RACF profiles would severely limit test ID access to production data sets (likely read-only). Much of the enforcement could be delegated to common RACF facilities, with less than the historical (pre-RACF technology) dependency on user exits sensitive to jobnames. I hope Ed J. would approve. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
