Checking the consistency of multiple sets of RECON data sets
Use the Multiple Resource Checker utility
to check the consistency of definitions across multiple sets of RECON
data sets. When inconsistencies are found, you can request an additional
report that shows which definitions in the RECON data sets are different.
About this task
If you have multiple sets of RECON data
sets and you want to ensure that the definitions in the RECON data
sets are consistent, run the Multiple Resource Checker utility
to generate a Resource Check Summary report. The Multiple Resource Checker utility
checks for inconsistencies in DB record fields and DBDS record fields.
If inconsistencies are found, the utility summarizes the differences
in the Resource Check Summary report. The Multiple Resource Checker utility
also reports the inconsistencies in the RECON record fields, DB record
fields, DBDS record fields, and data group record fields in the RECON
Difference report.
Restriction: The utility
does not check all of the fields in RECON data sets. For the record
fields that are checked by the Multiple Resource Checker utility,
see Fields compared in RECON data sets.
The
following figure illustrates the resources that are compared in this
scenario.
Figure 1. Checking the consistency of multiple sets of RECON data sets
Sample JCL for the Multiple Resource Checker utility
is in the SHPSJCL0 library, member FABWIVP. You can modify this sample
JCL and then use it to run the utility.
Procedure
Code the EXEC statement and DD statements for the Multiple Resource Checker utility.
The following JCL example is for comparing multiple sets
of RECON data sets:
Examine the Resource Check Summary report that is generated
in the FABWSUMM data set. If a RECON Difference report is generated
in the FABWRRPT data set, also examine that report.
The
following figure shows an example of the Resource Check Summary report.
Figure 2. Report example: Resource Check Summary report
for RECON data sets
From this report, you can identify whether
the database definitions in the DB record fields and DBDS record fields
are the same across the sets of RECON data sets.
1 The database definition for DBD00001
is registered in all the specified RECON data sets. However, the definitions
are different in some RECON data sets.
2 The database definition for DBD00002
is registered in all the specified RECON data sets. The definitions
in all the RECON data sets are the same.
The following figure shows an example of the RECON Difference report.Figure 3. Report example: RECON Difference report when inconsistencies are detected
IMS LIBRARY INTEGRITY UTILITIES - MULTIPLE RESOURCE CHECKER "RECON DIFFERENCE REPORT" PAGE: 1
5655-U08 DATE: 04/01/2021 TIME: 11.20.23 FABWMCHK - V2.R2
DBNAME=DB00001 TYPE=DB
FIELD (SAME) DD VALUE FIELD (DIFF) 1 DD VALUE
------------------ -- ---------------- ------------------ -- ----------------
DBD ** DB00001 SHARE LEVEL 01 3
------------------ ------------------ 02 2
03 3
IMS LIBRARY INTEGRITY UTILITIES - MULTIPLE RESOURCE CHECKER "RECON DIFFERENCE REPORT" PAGE: 2
5655-U08 DATE: 04/01/2021 TIME: 11.20.23 FABWMCHK - V2.R2
DBNAME=DB00001 TYPE=DBDS
DDN=DD0000A
FIELD (SAME) DD VALUE FIELD (SAME) DD VALUE FIELD (SAME) DD VALUE
------------------ -- ---------------- ------------------ -- ---------------- ------------------ -- ----------------
DDN ** DD0000A DBD ** DB00001 TYPE ** IMS
------------------ ------------------ ------------------
FIELD (SAME) DD VALUE FIELD (SAME) DD VALUE
------------------ -- ---------------- ------------------ -- ----------------
DBORG ** HDAM DSORG ** VSAM
------------------ ------------------
From this report, you can identify that
in the DB record fields, the value of SHARE LEVEL differs for DBD
DBD00001 1 .
For a description
of the reports, see the following topics: