How to EXEC PROC in a JCL

From: Andr? Queiroz (andre.queiroz_at_netcabo.pt)
Date: 01/21/04 

Date: 21 Jan 2004 08:34:18 -0800

Hello,
 I have a JCL step like:

//XXXPRG EXEC PROC=MYLIB,PG=PGM2,COND=(0,NE)
//FICH1 DD DSN=AAA.DS100.RESULT,
// DISP=(NEW,CATLG,DELETE),
// SPACE=(TRK,(50,50),RLSE),
// DCB=(RECFM=FB,LRECL=128)

 Is there any way of knowing where are the libraries defined by
MYLIB?? I need to know because my system has several PGM2 and I don't
know wich is being used in my JCL execution.

 Thanks in advance,

Andre Queiroz

Relevant Pages

  • Re: How to EXEC PROC in a JCL
    ... Queiroz) wrote: ... > Is there any way of knowing where are the libraries defined by ... >MYLIB?? ... >know wich is being used in my JCL execution. ...
    (comp.lang.cobol)
  • Re: How to EXEC PROC in a JCL
    ... > Is there any way of knowing where are the libraries defined by ... >MYLIB?? ... >know wich is being used in my JCL execution. ...
    (comp.lang.cobol)
  • Re: specifying z/OS load libraries
    ... JCL, and I dislike them. ... It does make it easier to test production JCL ... to specify LNKLST libraries to *not* be in LLA. ... but I am also curious as to why one would prefer a STEPLIB to ...
    (comp.lang.cobol)
  • Re: specifying z/OS load libraries
    ... As for the test JCL, the "copy and change" method is what we use now on VSE. ... It does make it easier to test production JCL in our test environments, but it also makes production JCL harder to read when trying to figure out why a batch job went down at 3 AM. ... If the names seem funny, that's because they aren't exactly the real names, and believe it or not, in each test environment we have TEST and PROD libraries for that environment. ... but I am also curious as to why one would prefer a STEPLIB to a ...
    (comp.lang.cobol)
  • procs and concatenations
    ... to, if desired, add just their own private library statements in their JCL. ... Obviously I could have APPL.PROD.COPYLIB in the proc and just have the ... calling JCL concatenate both libraries explicitly. ...
    (bit.listserv.ibm-main)