Coding the JCL statements for comparing control blocks in batch


The following figure shows a generic example of the JCL to compare control blocks in batch.

The example shows all of the statements that Database Integrity ever uses during the comparison process.


//COMPARE  JOB (acct),'name',MSGCLASS=x,CLASS=c,NOTIFY=uuu
//*
//COMP1    EXEC PGM=DBIUBC00,REGION=4096K
//STEPLIB  DD DSN=BMC.XXX.LOAD,DISP=SHR
//*
//PSBLIB   DD DSN=IMSx.PSBLIB,DISP=SHR             <=== IMS PSB library
//PSBLIB2  DD DSN=IMSx.PSBLIB2,DISP=SHR            <=== IMS PSB library 2
//DBDLIB   DD DSN=IMSx.DBDLIB,DISP=SHR             <=== IMS DBD library
//DBDLIB2  DD DSN=IMSx.DBDLIB2,DISP=SHR            <=== IMS DBD library 2
//ACBLIB   DD DSN=IMSx.ACBLIB,DISP=SHR             <=== IMS ACB library
//ACBLIB2  DD DSN=IMSx.ACBLIB2,DISP=SHR            <=== IMS ACB library 2
//DIRLIB   DD DSN=IMSx.BSDS,DISP=SHR               <==== IMS DIR boot strap dataset
//DIRLIB2  DD DSN=IMSx.BSDS,DISP=SHR               <==== IMS DIR boot strap dataset 2
 //*
//DBIPRINT DD SYSOUT=*                             <=== reports
//SYSUDUMP DD SYSOUT=*                             <=== dumps
//PLUSOUT  DD SYSOUT=*                             <=== BMC diagnostics
//*
//DBISYSIN DD *
  COMPARE control statement
//*

When doing a comparison, the significant DD statements are those that describe the DBD, PSB, DIR, and/or ACB libraries that contain Compare Block 1 and Compare Block 2. You do not have to specify the data sets in the JCL. You can specify the data set names with keywords on the COMPARE control statement instead. You can also specify the PSBLIB, DBDLIB, and ACBLIB data sets on the GLBL statement.

 

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

BMC AMI Database Integrity for IMS 5.1