Skip to Content

Coding the JCL statements for DBD Audit

The following figure shows a generic example of the JCL to audit DBD libraries in batch.

The example shows the statements Database Integrity can use during the auditing process.

Related topic

Auditing-DBD-libraries-in-batch


//DBDAUDIT JOB (acct),'name',MSGCLASS=x,CLASS=c,NOTIFY=uuu
//*
//AUDIT1   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
//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          <=== dynamic alloc library
//MODBLKS  DD DSN=IMSx.MODBLKS,DISP=SHR         <=== online modules library
//RECON    DD DSN=IMSx.RECON1,DISP=SHR          <=== RECON data set
//*
//DBIPRINT DD SYSOUT=*                             <=== reports
//SYSUDUMP DD SYSOUT=*                             <=== dumps
//PLUSOUT  DD SYSOUT=*                             <=== BMC diagnostics
//*
//DBISYSIN DD *
  DBDAUDIT control statement
//*

When auditing a DBD library, the significant DD statements are those that describe the input libraries. However, you do not have to specify these data sets in the JCL. You can specify the data set names with keywords on the GLBL or DBDAUDIT 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.1