Go to:  Davar site entry | Site contents | Site index | Mainframe | JCL | Text bottom

CRETLIB  Job

        

CRETLIB job creates and catalogs development libraries using MVS Job Scheduler (IEFBR14 is a "do-nothing" dummy system program).  The job is self-contained and consists of an in-stream procedure and a series of its calls to create individual libraries.

CRETLIB needs to be run only once on the new site to establish development environment.  Normal procedure is to use ISPF option =3.2 to create &SYSUID..PGMR.JOB library and to upload CRETLIB job into it (best by using FTP which is simple, reliable, quick and is now universally available).

It is necessary to adjust VOL=SER= value in the in-stream procedure so that your libraries won't be wiped out by SMS (System Managed Storage).  Normally the best way to find appropriate VOL=SER= for your libraries is to use ISPF option =3.4 to check what volumes are used by other members of the development team to allocate their libraries.  It might also be necessary to adjust the list of libraries to be allocated and their SPACE parameters.  After that CRETLIB job can be submitted to create all other development libraries in one shot. 


      //DEVVLADL JOB CLASS=D,MSGCLASS=H,NOTIFY=&SYSUID TYPRUN=SCAN
      //*
      //CRETLIB PROC G=PGMR,  - Library group
      //             N=,      - Library name
      //             P=10,    - Number of primary    memory units
      //             A=6,     - Number of additional memory units
      //             D=10,    - Number of library directory blocks
      //             R=FB,    - Record format (RECFM)
      //             L=80     - Record length (LRECL)
      //*
      //*            Adjust VOL=SER= value in the in-stream procedure
      //*                                  |    |
      //IEFBR14 EXEC PGM=IEFBR14           V    V
      //SYSUT     DD UNIT=SYSALLDA,VOL=SER=TSO001,DSN=&SYSUID..&G..&N,
      //             SPACE=(TRK,(&P,&A,&D)),DISP=(,CATLG,DELETE),
      //             DCB=(DSORG=PO,RECFM=&R,LRECL=&L,BLKSIZE=0)
      //        PEND
      //*
      //PCList  EXEC CRETLIB,N=CList,P=20,A=12,D=20
      //PREXX   EXEC CRETLIB,N=REXX
      //PPROC   EXEC CRETLIB,N=PROC
      //PCONTRL EXEC CRETLIB,N=CONTROL,P=5,A=3,D=10
      //PCOBOL  EXEC CRETLIB,N=COBOL
      //PPLI    EXEC CRETLIB,N=PLI,P=20,A=12,D=20
      //PPANEL  EXEC CRETLIB,N=PANEL
      //POBJECT EXEC CRETLIB,N=OBJECT,P=5,A=3,R=U,L=0
      //PLOAD   EXEC CRETLIB,N=LOAD,R=U,L=0
      //*
      //UJOB    EXEC CRETLIB,G=USER,N=JOB
      //UPROC   EXEC CRETLIB,G=USER,N=PROC
      //UCONTRL EXEC CRETLIB,G=USER,N=CONTROL,P=5,A=3,D=10
      //UCOBOL  EXEC CRETLIB,G=USER,N=COBOL,P=20,A=12
      //UCOPY   EXEC CRETLIB,G=USER,N=COPY
      //ULOAD   EXEC CRETLIB,G=USER,N=LOAD,R=U,L=0
      //
        

Notes:
 •

Job name here is composed of my most typical TSO user ID DEVVLAD (you can't use &SYSUID in JCL name field) and a one letters postfix L (that's all they'll normally leave for you to distinguish between your jobs).

 • Development (test) job CLASS is assumed to be D.
 • Held MeSsaGe CLASS is assumed to be H.
 •

TSO user submitting the job (&SYSUID) will be NOTIFied about job completion.

 •

High-level qualifiers of all created libraries is the TSO ID of the user submitting the job (&SYSUID).

 •

In order to SCAN job for the JCL errors change temporarily space into comma in the JOB line as shown:  ...NOTIFY=&SYSUID , TYPRUN=SCAN

 •

You may find a detailed explanation of library creation parameters in the generalized data set creation cataloged procedure CRETDS (CREaTe Data Set).

         
View [and save] CRETLIB.JCL text
(Use [Back] button or [Alt]+[CL] to return here from the viewed text)
Go to:  Davar site entry | Site contents | Site index | Mainframe | JCL | Text top