Coding the JCL statements for disassembling control blocks in batch


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

The example shows all of the statements Database Integrity uses during the disassembly process.


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

When disassembling a control block, the significant DD statement is the one that describes the DBD, PSB, ACB, or DFSMDA library containing the control block to disassemble. However, you do not have to specify this data set in the JCL. You can specify the data set name with a keyword on the GLBL or DECODE control statement instead.



 

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

BMC AMI Database Integrity for IMS 5.2