Final responds .. before we hit the weekend : a) Have you got any User exits in your shop b) have you got any Dataset naming conventions
Then : a) Drop the ALIAS on the LPAR for those users that are not suppose to be on that LPAR b) User your IEFUJV to validate the users JCL c) or Jesexit6 to insert a /*XEQ card... i think it's JESEXIT6 Summary: No user exits and no naming conventions ? Then just allow them to only LOGON to the LPAR where they are suppose to be. Anton On Fri, 31 Oct 2008 17:23:58 -0400, Lizette Koehler <[EMAIL PROTECTED]> wrote: >The intent was to do it for the users, rather than have them change their JCL. As you know, it is not always guarantee that the user will do what is needed. > >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. > >---------------------------------------------------------------------- >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 ---------------------------------------------------------------------- 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
