If you have the opportunity to scan archived MSGCLASS-related job-output (e.g., 
utilities like $AVRS, JMR others), the message IEFC001I may also be informative 
in your quest.

Scott Barry
SBBTech LLC


On Wed, 13 Nov 2024 21:44:51 +0000, Pommier, Rex <[email protected]> 
wrote:

>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.
>
>Rex
>
>-----Original Message-----
>From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
>Bob Bridges
>Sent: Wednesday, November 13, 2024 3:33 PM
>To: [email protected]
>Subject: [EXTERNAL] Listing proclibs
>
>Ah, I should have thought long ago to ask this question here!  I'm slow, I am. 
> 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?
>
>---
>Bob Bridges, [email protected], cell 336 382-7313
>
>/* Being famous has its benefits, but fame isn't one of them.  -Larry Wall */
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
>[email protected] with the message: INFO IBM-MAIN
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to