I would love to use this approach but we are a Top Secret Shop and not RACF.
I will see if our security admins can change this to a TSS function.
And yes, both processes are really required. Fail it on systems where it is
not suppose to run, and make it only run on the LPAR of My choice.
Lizette
>
> >I am looking for a good (and easy) way of ensuring that certain
> programs
> only run on a specific LPAR. We are very vanilla z/OS V1.9.
> >
> >I was thinking of either creating a stub module that is the name of
> the
> program and then testing to see if it is submitted with /*JOBPARM or
> creating a TSO Submit exit and Converter exit to add the /*JOBPARM if
> it is
> a specific program name.
> >
> >Are there any better and easier to maintain options for this request?
> >
> >
> >So if JOBA is submitted (either via a scheduler product or TSO) and
> the
> PGM=PROGA then I want to ensure that the job only runs on LPARA.
>
> Are you wanting to provide an automatic mechanism that routes the job
> to the
> right system? Or one that makes the job fail if run on the wrong
> system?
> You've kind of hinted at both approaches.
>
> For the "failure" case, you could use RACF PROGRAM control, and for
> those
> programs that must run on a specific system and are not in LPA you can
> do
> something like:
> RDEFINE PROGRAM program-name ADDMEM('library'//NOPADCHK) UACC(NONE)
> PERMIT program-name CLASS(PROGRAM) ID(*) ACCESS(READ) WHEN(SYSID(smf-
> id))
>
> If the program runs on a system you have not specified then it will
> abend
> with an S306 abend.
----------------------------------------------------------------------
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
