-----------------------------------<snip>-----------------------------
On 10/4/2009 at 9:14 AM, in message <[email protected]>, 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.
Bizarre. Why not?
--------------------------<unsnip>------------------------
Some automation packages are quite capable of triggering product streams
when a particular ad-hoc jobname completes. You wouldn't want your development
team triggering production streams at the wrong time of day would you?
----------------------------------<snip>--------------------------
Certainly not. If I had a job scheduler that treated a test job as if it were
a production job I would treat that as a bug in the scheduler and have the
vendor fix it. Certainly there are several ways of distinguishing between a
production job and a test job. For instance the scheduler user ID is used to
submit production jobs...
-----------------------------------------<unsnip>-----------------------------------------
But you still need to prevent testers from submitting jobs with a
production USERID. We used a TSO exit to remove USER/PASSWORD parms from
the JOB statement. Got a better idea?
Please remember: much of what I describe was developed before RACF was
able to filter job submission.
Rick
----------------------------------------------------------------------
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
