JCL requirements for the Consistency Checker utility

When you code the JCL to run the Consistency Checker utility, include the EXEC statement and appropriate DD statements.

Subsections:

JCL example
EXEC statement
DD statements

JCL example

The following figure shows the JCL that is required for checking consistency of DBDs and PSBs.

Figure 1. JCL for checking consistency of DBDs and PSBs

//stepname EXEC PGM=FABLECHK
//STEPLIB  DD   DSN=HPS.SHPSLMD0,DISP=SHR
//         DD   DSN=IMSVS.DFSMDA,DISP=SHR
//         DD   DSN=IMSVS.SDFSRESL,DISP=SHR
//DFSRESLB DD   DSN=IMSVS.SDFSRESL,DISP=SHR
//DBDLIB   DD   DSN=IMSVS.DBDLIB,DISP=SHR
//PSBLIB   DD   DSN=IMSVS.PSBLIB,DISP=SHR
//ACBLIB   DD   DSN=IMSVS.ACBLIB,DISP=SHR
//DFSMDA   DD   DSN=IMSVS.DFSMDA,DISP=SHR
//MODBLKS  DD   DSN=IMSVS.MODBLKS,DISP=SHR
//SYSRDDS  DD   DSN=IMSVS.SYSRDDS,DISP=SHR
//NSYSRDDS DD   DSN=IMSVS.NSYSRDDS,DISP=SHR
//SYSOUT   DD   SYSOUT=A
//SYSPRINT DD   SYSOUT=A
//SYSIN    DD   *  
    (control statements)
/*

EXEC statement

The EXEC statement must be in the following format:

//stepname EXEC PGM=FABLECHK,PARM='IMSPLEX=imsplex,DBRCGRP=dbrcgrp'

IMSPLEX=imsplex: A 1 - 5 character IMSplex name used for RECON data sets. This parameter is optional.
DBRCGRP=dbrcgrp: A 1 - 3 character identifier (ID) assigned to a group of DBRC instances that access the same RECON data set in an IMSplex. This parameter is optional.

DD statements

Code the following DD statements to identify the source of input and the placement of output information.

Consistency Checker verifies the libraries that the input DD statements specify, however, depending on the type of database organization, Consistency Checker does not verify certain libraries. For more information, see Verified libraries for each database organization.

STEPLIB DD

Required. This DD statement defines the input data sets as follows:

IMS™ Library Integrity Utilities load module library (required)
The library that contains DFSMDA dynamic allocation members for the RECON data set. When the RECONn DD statement is omitted, this DD is required. When the members are included in the library that the DFSMDA DD statement specifies, this DD is not required.
The library that contains the IMS load modules, and is optional. When CHKRECON=YES is specified, this DD statement is required.
If you use the SCI exit routine for your IMS environment, specify the load module data set that contains the exit routine.

DFSRESLB DD

Required. This input DD statement points to the library that contains the IMS load modules.

DBDLIB DD

Required if the DBD control statement is specified. This input DD statement points to the library that contains the DBDs to check.

PSBLIB DD

Required if the PSB control statement is specified. This input DD statement points to the library that contains the PSBs to check.

ACBLIB DD

Optional. This input DD statement points to the library that contains the ACBs to check. If you specify this DD statement, Consistency Checker verifies whether the ACB member that corresponds to the specified DBD or PSB has been created. If the ACB member exists, Consistency Checker verifies whether the member is consistent with the DBD or the PSB. If this data set is not specified, Consistency Checker does not check ACBs for any DBD or PSB.

DFSMDA DD

Optional. This input DD statement points to the library that contains the DFSMDA dynamic allocation members. If you specify this DD statement, Consistency Checker verifies whether the DFSMDA dynamic allocation member that corresponds to the specified DBD has been created. If the dynamic allocation member exists, Consistency Checker verifies whether the DSG registration record is consistent with the DBD. If this data set is not specified, Consistency Checker does not check DFSMDA members for any DBDs.

MODBLKS DD

Optional. This input DD statement points to the library that contains MODBLKS, which are control block modules created by IMS system definition. If the data set is specified and DRD=NO is specified in the SYSIN data set, Consistency Checker verifies whether an entry that corresponds to the specified DBD or PSB has been created in the MODBLKS module and, if so, whether it is consistent with the DBD or the PSB. If this data set is not specified, Consistency Checker does not check the MODBLKS for any DBD or PSB.

SYSRDDS DD

Optional. This input DD statement points to the data set that contains the system RDDSs, which are defined in DRD environments. If the data set is specified and DRD=YES is specified in the SYSIN data set, Consistency Checker verifies whether a definition that corresponds to the specified DBD or PSB has been created in the RDDS and, if created, whether it is consistent with the DBD or the PSB. If this data set is not specified, Consistency Checker does not check the RDDS for any DBD or PSB. Consistency Checker verifies only the latest RDDS even if multiple RDDSs are specified.

NSYSRDDS DD

Optional. This input DD statement points to the data set that contains the non-system RDDS, which is not defined in DRD environments. If the data set is specified and DRD=YES is specified in the SYSIN data set, Consistency Checker verifies whether a definition that corresponds to the specified DBD or PSB has been created in the RDDS and, if created, whether it is consistent with the DBD or the PSB. If this data set is not specified, Consistency Checker does not check the RDDS for any DBD or PSB. The data set must be created by the EXPORT TYPE(ALL) NAME(*) command to contain all the resource definitions. Concatenated data sets are not used.

RECONx DD

Optional. These input DD statements point to the RECON data sets. If the data set is specified and CHKRECON=YES is specified in the SYSIN data set, Consistency Checker verifies whether a definition that corresponds to the specified DBD has been created in the RECON data set. If the definition exists, Consistency Checker verifies whether the definition and the DBDS records in the RECON data sets are consistent with the DBD. If this DD statement is omitted, DBRC dynamically allocates the data sets by using DFSMDA dynamic allocation members when Consistency Checker issues a DBRC command internally.

SYSOUT DD

Required. This output DD statement points the data set for generating all activity logs and error messages. The record format is fixed-blocked. The logical record length is 133. Block size, if coded, must be a multiple of 133.

SYSPRINT DD

Required. This output DD statement points to the data set in which Consistency Checker generates the DBD check report, the PSB check report, or both. Each report is sorted alphabetically by member name. The record format is fixed-blocked. The logical record length is 133. Block size, if coded, must be a multiple of 133.

SYSIN DD

Required. The SYSIN DD is the control data set for this program. The record format is fixed-blocked. The logical record length is 80. Block size, if coded, must be a multiple of 80. You can specify up to 9999 control statements by using the SYSIN DD statement.

Related reading: See Control statements for the Consistency Checker utility for control statements.