Coding the JCL statements for generating labels in batch

The following figure shows a generic example of the JCL to generate labels in batch.

The example shows the statements that Database Integrity can use during the label generation process.

Related topic

Generating-labels-in-batch


//LBLGEN   JOB (acct),'name',MSGCLASS=x,CLASS=c,NOTIFY=uuu
//*
//GEN1     EXEC PGM=DBIUBC00,REGION=4096K
//STEPLIB  DD DSN=BMC.XXX.LOAD,DISP=SHR
//         DD DSN=IMSx.RESLIB,DISP=SHR
//*
//DFSRESLB DD DSN=IMSx.RESLIB,DISP=SHR             <=== IMS exec library
//DBDLIB   DD DSN=IMSx.DBDLIB,DISP=SHR             <=== IMS DBD library
//RECON1 DD DSN=IMSx.RECON1,DISP=SHR <=== RECON1 data set
//RECON2 DD DSN=IMSx.RECON2,DISP=SHR <=== RECON2 data set
//RECON3 DD DSN=IMSx.RECON3,DISP=SHR <=== RECON3 data set
//dbilabel DD DSN=IMSx.DBILABEL,DISP=SHR           <=== optional label KSDS
//*
//DBIPRINT DD SYSOUT=*                             <=== reports
//SYSUDUMP DD SYSOUT=*                             <=== dumps
//PLUSOUT  DD SYSOUT=*                             <=== BMC diagnostics
//*
//DBISYSIN DD *
  LBLGEN control statement
//*

When generating labels, the significant DD statements are the ones that describe the DBD library, the label data set, and the IMS execution module library.

You do not have to specify the DBD library and label data sets in the JCL. You can specify them with keywords on the GLBL or LBLGEN control statement instead. The label data set can be dynamically allocated by Database Integrity.

Database Integrity requires the data set name of the library containing the IMS execution modules (the RESLIB). You must code the DFSRESLB DD statement in the JCL to specify the data set name. Note that you cannot use the RESLIB keyword to provide the name. Database Integrity invokes IMS for block building before it processes the control statements.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*