Control statements for the Multiple Resource Checker utility

The input to the Multiple Resource Checker utility consists of control statements in the FABWCTL data set. These control statements contain keywords that specify the function and the names of the DBDs, PSBs, or ACBs to check.

If the FABWCTL data set is not specified, the default options are used in the job, and all the members and databases in the specified libraries and RECON data sets are checked.

You can specify up to 9999 control statements in the FABWCTL statement.

This data set usually resides in the input stream. However, it can be defined as a sequential data set or as a member of a partitioned data set. It must contain one 80-byte fixed-length record for each control statement. Block size, if coded, must be a multiple of 80.

A Resource Check Summary report is always generated. In the report, the members are reported in alphabetical order, regardless of the order they are specified in the control statements.

Subsections:

Control statement example
Syntax rules
Control statement keywords

Control statement example

Control statements can be coded as follows:

//FABWCTL DD *
    NOCOMP=parameter,parameter
    CHKONLY=parameter,parameter
    CHKRECON=parameter
    DIFFREP=parameter
    DBD=member
/*

Syntax rules

The control statements for Multiple Resource Checker must adhere to the following syntax rules:

Control statements can be coded on any columns in the range of 2 - 80.
In the control statement fields, keywords, equal signs (=), and member names must not be separated by blanks. Because a blank serves as the delimiter, only a comment can be written after a blank.
A statement with an asterisk (*) in column 1 is treated as a comment.

The control statements can be specified in any order. For example:

  DBD=member
  CHKONLY=parameter
  CHKRECON=parameter
  NOCOMP=parameter
  DIFFREP=parameter

Control statement keywords

The following keywords are supported:

CHKONLY=parameter

This keyword causes the utility to check only the specific resources.

For example, if you specify DBDLIBxx DD and ACBLIBxx DD statements and CHKONLY=DBD,ACB, the utility checks the consistency of DBD members across the DBD libraries and the consistency of ACB members across the ACB libraries. Without the CHKONLY control statement, the utility checks the consistency between the DBD libraries and the ACB libraries.

DBD: Compares the members in the libraries that are specified by the DBDLIBxx DD statements.
PSB: Compares the members in the libraries that are specified by the PSBLIBxx DD statements.
ACB: Compares the members in the libraries that are specified by the ACBLIBxx DD statements.
RECON: Compares the database definitions in the RECON data sets that are specified by the RECONxxn DD statements.

CHKRECON=DBDEF | DBDEF_RCV

Specifies the scope of the fields to compare when the utility checks the consistency of definitions across multiple sets of RECON data sets.

DBDEF: Compares the fields that relate to database definitions. CHKRECON=DBDEF is the default value.
DBDEF_RCV: Compares the fields that relate to database definitions and the fields that relate to the database recovery environment.

For a list of the record fields that are compared by this option, see Fields compared in RECON data sets.

NOCOMP=parameter

Specifies the fields that you do not want to check.

IMSREL: The utility compares the DBD, PSB, ACB members that are generated by the DBDGEN, PSBGEN, or ACBGEN utility of different IMS™ release levels or sets of RECON data sets that are generated by different IMS release levels. If you specify this parameter, IMS release levels are not checked. Also the fields that were added or deleted in a higher release of IMS are not checked.
The DBD and PSB fields that are not checked when NOCOMP=IMSREL is specified are the same as the fields that are not compared by the DBD/PSB/ACB Compare utility. For such fields, see NOCOMP control statement.
VERSION: The field that is related to the VERSION= statement of the DBDGEN utility in DBD and ACB members is not checked.
METADATA: The metadata field in DBDs, PSBs, and ACBs are not checked.
Instead of specifying NOCOMP=METADATA, you can specify NOCOMP=CATALOG. CATALOG is an alias for METADATA.

DIFFREP=YES|NO

Specifies whether to generate the RECON Difference report. This keyword can be specified only once.

YES: Generate the RECON Difference report when inconsistencies are found in the RECON data sets.
NO: Do not generate the RECON Difference report. DIFFREP=NO is the default value.

DBD=member

The name of the member to check.

PSB=member

The name of the member to check.

For DBD= and PSB= keywords, you can specify a wildcard in any position of a character string. The asterisk (*) and the percent sign (%) are supported as wildcard characters. An asterisk represents 0 - 8 characters, and the percent sign represents a single character. If two or more asterisks are specified sequentially, only the first asterisk is recognized.