I think that is the best idea, if changing the job JCL is an option. But it may be that it's more feasible to change one proc instead of who knows how many jobs. That's one of the reasons to have procs.
Also, I believe your "plexname" should be "systemname". sas On Wed, Feb 8, 2023 at 10:28 AM Sri h Kolusu <skol...@us.ibm.com> wrote: > >> I was asked to add a step that would check that the JOB is running on > the correct LPAR. > > Gadi, > > I agree with Mikael of using SYSAFF parm to route the JOB to that LPAR it > needs to run. This will not only eliminate making any changes to the PROC > and you don't need to add a rexx exec to determine the Lpar it is running > in. > > So, change the Job in question to have the SYSAFF in either of these 2 > different ways > > //SAMPJCRD JOB (aaaa,bbbb,cccc,dddd),&SYSUID,SYSAFF=plexname, > // MSGCLASS=H,MSGLEVEL=(1,1),CLASS=A,NOTIFY=&SYSUID > /* > > Or > > /*JOBPARM SYSAFF=plexname > > Thanks, > Kolusu > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
