The only way I think of is looking at the enque list. However, the master scheduler is marked NDSI in SCHECDxx, so it doesn't enqueue anything.
On Thu, May 30, 2019 at 3:03 PM John McKown <john.archie.mck...@gmail.com> wrote: > On Wed, May 29, 2019 at 5:10 PM Pommier, Rex <rpomm...@sfgmembers.com> > wrote: > > > 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. > > > > I don't have any of that fancy Omegamon type stuff. So I start here: > > > IEE254I 06.47.04 IPLINFO DISPLAY 503 > SYSTEM IPLED AT 15.57.51 ON 03/10/2019 > RELEASE z/OS 01.12.00 LICENSE = z/OS > USED LOAD11 IN SYS1.IPLPARM ON 02BB0 > ARCHLVL = 2 MTLSHARE = N > IEASYM LIST = 11 > IEASYS LIST = (11) (OP) > IODF DEVICE: ORIGINAL(02BB0) CURRENT(02BB0) > IPL DEVICE: ORIGINAL(02BB1) CURRENT(02BB1) VOLUME(I17RS1) > I can then look at the LOAD11 member in SYS1.IPLPARM on I17CAT (D > U,,,2BB0,1 to get the volser, or just assume it is catalogued). I found > this: > > PARMLIB SYS1.LIH1.PARMLIB I17CAT > PARMLIB SYS1.PARMLIB I17CAT > PARMLIB CPAC.PARMLIB I17CAT > PARMLIB SYS1.IBM.PARMLIB I17RS1 > PARMLIB SYS1.LIH1.UNICODE LIHTS1 > > Now, I have a nice little TSO ISPF command called SYSPARM which will bring > up a ISPF 3.4 type display of the current PARMLIB concatenation. You can > get this on http://cbttape.org in file #968. I look and see that my IEASYS > member is 11, which is concatenated before IEASYS00. So I look in those > members, in the aforementioned PARMLIB concatention, I saw MSTRJCL=00 in > IEASYS00. You will need to look at each of the IEASYSnn members, in order > to see where, and if, MSTRJCL=nn is first specified. Using the same ISPF > 3.4 display of the PARMLIBs, I then look at MSTJCL00. Of course, if someone > has modified this member since IPL, it will be inaccurate. > > I don't know if the actual JCL used internally to start the *MASTER* > address space is kept anywhere. Having gone all over this mess, I > remembered that we do have BMC Mainview/MVS (very old). It has RESOLVE. So > I did this: > > > F RES,TIO,*MASTER*,MAP > AMT00DI Enter SYSPROG command (LIH1) > AMTE11I STC41311 MSTJCL00 OPSUSS Prty 255 Page I/Os 9,968 > AMTE12I DD STCINRDR > AMTE13I DSN .MSTR .MS0000.STCINRDR > AMTE12I DD TSOINRDR > AMTE13I DSN .MSTR .MS0000.TSOINRDR > AMTE12I DD IEFPDSI Unit 2BB0 Volume I17CAT > AMTE13I DSN SYS1.LIH1.PROCLIB > AMTE12I Unit 2BB0 Volume I17CAT > AMTE13I DSN SYS1.PROCLIB > AMTE12I Unit 2BB0 Volume I17CAT > AMTE13I DSN CPAC.PROCLIB > AMTE12I Unit 2BB1 Volume I17RS1 > AMTE13I DSN SYS1.IBM.PROCLIB > AMTE12I DD SYSUADS Unit 2BB2 Volume I17RS2 > AMTE13I DSN SYS1.UADS > AMTE12I DD IEFJOBS Unit 2BB0 Volume I17CAT > AMTE13I DSN SYS1.LIH1.STCJOBS > AMTE12I DD IEFPARM Unit 2BB0 Volume I17CAT > AMTE13I DSN SYS1.LIH1.PARMLIB > AMTE12I Unit 2BB0 Volume I17CAT > AMTE13I DSN SYS1.PARMLIB > AMTE12I Unit 2BB0 Volume I17CAT > AMTE13I DSN CPAC.PARMLIB > AMTE12I Unit 2BB1 Volume I17RS1 > AMTE13I DSN SYS1.IBM.PARMLIB > AMTE12I Unit 2401 Volume LIHTS1 > AMTE13I DSN SYS1.LIH1.UNICODE > AMTE12I DD SYSLBC Unit 2401 Volume LIHTS1 Excp 27,395 > AMTE13I DSN SYS1.PLEXLIH1.BRODCAST > AMTE12I DD SYS00001 Unit 2203 Volume LIHTS7 > AMTE13I DSN SYS1.RACF > AMTE12I DD SYS00002 Unit 2501 Volume LIHTSA > AMTE13I DSN SYS1.RACF.MIRROR > AMTE12I DD SYS00003 Unit 2BB1 Volume I17RS1 Excp 102 > AMTE13I DSN SYS1.SCUNTBL > AMTE12I DD SYSLOG81 JES2 > AMTE13I DSN +MASTER+.SYSLOG.STC41311.D0000182.? > > > > > > > TIA, > > > > Rex > > > > 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 > > > > > -- > This is clearly another case of too many mad scientists, and not enough > hunchbacks. > > > Maranatha! <>< > John McKown > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- ITschak Mugzach *|** IronSphere Platform* *|* *Information Security Contiguous Monitoring for Legacy **| * ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
