Thanks David et al, I knew system told me somewhere but for the life of me, I couldn't find it. The confusion on my part came from the fact that I have the IEASYS00 line to use MSTJCL00. However, member MSTJCL00 doesn't exist in SYS1.PARMLIB but it is in a concatenated PARMLIB library. Being the master scheduler starts so early, I didn't know if the system was up far enough to use concatenated PARMLIBs or if it was just using SYS1.PARMLIB. Hence I didn't know which MSTJCL00 was being used. Digging back through the syslog tells me that the concatenated PARMLIB is in effect, as my IEFJ200I says it is coming from PARMLIB.
Thanks again, all. Rex -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of David Spiegel Sent: Wednesday, May 29, 2019 6:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: master JCL Hi Skip, This is a SYSLOG excerpt. IEE252I MEMBER MSTJCL00 FOUND IN ADCD.Z23A.PARMLIB . . . IEFJ200I MASTER SCHEDULER JCL FOR THIS IPL TAKEN FROM MEMBER MSTJCL00 OF PARMLIB IEF196I 1 //MSTJCL00 JOB MSGLEVEL=(1,1),TIME=1440 IEF196I 2 // EXEC PGM=IEEMB860,DPRTY=(15,15) IEF196I 3 //STCINRDR DD SYSOUT=(A,INTRDR) IEF196I 4 //TSOINRDR DD SYSOUT=(A,INTRDR) IEF196I 5 //IEFPDSI DD DSN=USER.&SYSVER..PROCLIB,DISP=SHR IEF196I IEFC653I SUBSTITUTION JCL - DSN=USER.Z23A.PROCLIB, IEF196I DISP=SHR IEF196I 6 // DD DSN=FEU.&SYSVER..PROCLIB,DISP=SHR IEF196I IEFC653I SUBSTITUTION JCL - DSN=FEU.Z23A.PROCLIB, IEF196I DISP=SHR IEF196I 7 // DD DSN=ADCD.&SYSVER..PROCLIB,DISP=SHR IEF196I IEFC653I SUBSTITUTION JCL - DSN=ADCD.Z23A.PROCLIB, IEF196I DISP=SHR IEF196I 8 // DD DSN=SYS1.PROCLIB,DISP=SHR IEF196I 9 //SYSUADS DD DSN=SYS1.UADS,DISP=SHR IEF196I 10 //SYSLBC DD DSN=SYS1.BRODCAST,DISP=SHR IEF196I 11 //IEFPARM DD DISP=SHR,UNIT=SYSALLDA,VOL=SER=A3CFG1, IEF196I // DSN=USER.Z23A.PARMLIB IEF196I 12 // DD DISP=SHR,UNIT=SYSALLDA,VOL=SER=A3CFG1, IEF196I // DSN=FEU.Z23A.PARMLIB IEF196I 13 // DD DISP=SHR,UNIT=SYSALLDA,VOL=SER=A3SYS1, IEF196I // DSN=ADCD.Z23A.PARMLIB IEF196I 14 // DD DISP=SHR, IEF196I // DSN=SYS1.PARMLIB IEF196I //* LOADxx parmlibs put in MSTRJCL concatenation IEF403I MSTJCL00 - STARTED - TIME=12.38.58 Regards, David On 2019-05-29 18:52, Jesse 1 Robinson wrote: > For a reeeeeeealy lonnnnnnnnnng time MVS has supported member MSTJCLxx in > PARMLIB for master JCL. As for finding the content of MSTJCLxx at NIP for the > current IPL, I'm at a loss. Does not seem to be captured in operlog. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office ⇐=== NEW > robin...@sce.com > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > Pommier, Rex > Sent: Wednesday, May 29, 2019 3:10 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):master JCL > > Hello listers, > > I'm apparently having a case of brain-drain. Is there an easy way to display > the currently used master JCL? I know I can look at LINKLIB and PARMLIB and > see what's there, but is there a way of displaying what's actually running? > I thought at one point in time I could see it in Omegamon or someplace. In > this case, google was not my friend. :-( Any assistance would be greatly > appreciated. > > TIA, > > Rex > > > ---------------------------------------------------------------------- > 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 The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
