Try https://github.com/lbdyck/lstproc.
Should give you what you want. Lionel B. Dyck <sdg >< Website: GitHub.com/lbdyck Sent from my iPhone 15 Pro Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden > On Nov 13, 2024, at 6:48 PM, Bob Bridges > <00000587168ababf-dmarc-requ...@listserv.ua.edu> wrote: > > Jack Zukt and J Pohlmann: Actually I was looking for a list of libraries > that MIGHT be proclibs; presumably a command that gives the current list > might change next IPL. > > Rex: SYS1.PROCLIB has only a couple of Java-related jobs in it, and > SYS1.PARMLIB has no member JES2PARM. Presumably something in the IPL points > elsewhere during startup. > > Rex and Dave: Yeah, I already spotted the JCLLIB statement. It's in some > production jobs, but not all of them, so I guess I need to know what the > proclibs will be when no JCLLIB is specified. Still hunting. > > Oh, and by the way, does JCLLIB ~add~ to the proc list, or replace it for > that particular job? > > Jack Zukt: So the current set of proclibs isn't exactly what I wanted, but I > tried PROC in SDSF anyway and got "COMMAND NOT AUTHORIZED". I'm a security > admin so I can change the rules to give me the permission, but I'd rather not > do that until I know more. Maybe later I will. > > Oh, and I can probably do the $D PROCLIB. I have a phobia of using operator > commands, though; it's been decades since I ran a HASP station and nowadays > I'm afraid of mistyping a command and accidentally bringing the system down. > Yeah, I know, all the $D commands are look-only (right?). Maybe I'll do it, > if I gather my courage. > > --- > Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 > > /* I see people wearing winter coats and hats. What a bunch of sheep! LOL! > I did my own research and found that only 1500 people die from hypothermia in > the US per year. That's only 0.0005% of the population. They live in fear > of something 99.9995% of people won't die from. It gets better: A lot of > the people who died from hypothermia were wearing coats and hats, and they > still died! Coats don't work! -not my opinon on COVID vaccinations, just > too much fun to ignore */ > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > Dave Gibney > Sent: Wednesday, November 13, 2024 19:03 > > You also need to remember that a source for PROCs can be defined in the JCL. > > //name JCLLIB ORDER=(pds/pdsename,...) > //step EXEC PROCNAME > > So, the PROC that executes can be in any PDS or PDS/E known to the system > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > J. Pohlmann > Sent: Wednesday, November 13, 2024 18:44 > > The operator command $dproclib if using JES2 will give you the proclib > concatenation. > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > Pommier, Rex > Sent: Wednesday, November 13, 2024 16:45 > > Check your JES2 proc in SYS1.PROCLIB and look for PROCnn DD statements. > Those will be your candidates for system PROCs. Go to SYS1.PARMLIB(JES2PARM) > for JOBCLASS statements and they might have PROCLIB parameters in them. If > they don’t, they'll be using PROC00. If they have something, that's the > PROCnn statement from JES2 they'll be using. > > 2 caveats/notes. Using JCLLIB in the JCL changes everything. If you're > looking for a particular job, the job output will tell you what library it > got pulled from. > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > Jack Zukt > Sent: Wednesday, November 13, 2024 16:38 > > Have you tried PROC at the SDSF command line? > > Or maybe I did not quite understood your request. > >> --- On Wed, Nov 13, 2024, 21:34 Bob Bridges < >> 00000587168ababf-dmarc-requ...@listserv.ua.edu> wrote: >> Is there a way - I expect there is - to look up in z/OS what libraries >> are used as production proclibs? >> >> Lest I discover too late that I phrased the question wrong, let me >> spell it out: I'm told that our scheduler uses four DSNs for the job >> libraries in the production LPAR, but they're all named xxx.CNTL. I >> know some production JCL is kept in various.PROCLIB (and probably >> other PDSs as well, but those at least). What I think is happening is >> that the scheduler submits a job from xxx.CNTL(member), which member >> consists mostly of a JOB card, comments and "//stepname DD EXEC >> procname". The procname is a member in another library, and some time >> during IPL the list possible proclibs is established by some starting >> parm or chain of parms. That list is searched whenever a job says >> "EXEC procname", much as the SYSEXEC and SYSPROC concatenations are >> searched when I say "TSO command" at the ISPF command line. >> >> So now I want to get a complete list of the proclibs, and I suppose if >> I only knew how to look it up I could find it in the startup parms >> somewhere. Better yet, the method is probably documented in the z/OS >> instructions. Can someone fill me in, please? > > ---------------------------------------------------------------------- > 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
