FABADA4 JCL
The FABADA4 program uses the information generated by FABADA3 (sorted) for segments with invalid pointers or user-provided segment information to generate CI Map/CI Dump report and Pointer Chain Reconstruction report.
FABADA4 is run as a standard z/OS® job step. An EXEC statement and DD statements that define inputs and outputs are required.
EXEC statement
This statement must be in the following form:
// EXEC PGM=FABADA4,REGION=1200K
The format of the optional PARM parameter is described as follows.
The PARM parameter of the EXEC statement for module FABADA4 can be used to determine which data set is to be used for input. The PARM parameter for module FABADA4 can be supplied on the EXEC statement in one of the following four formats:
- PARM=
- If the PARM parameter is not selected, the default is the null. Supplying a null PARM (or not supplying a PARM at all) is the ordinary way of running module FABADA4. This causes module FABADA4 to use the sorted DAR4ERRS data set from the SORT4 step as input.
- PARM=DAR4ERRS
- This causes module FABADA4 to use the sorted DAR4ERRS data set from the SORT4 step as input.
- PARM=DAR4USER
- This causes module FABADA4 to use the DAR4USER data set that you provide as input.
- PARM=BOTH
- This causes module FABADA4 to use both DAR4ERRS data set from the SORT4 step and DAR4USER data set that you provide as input.
DD statements
The following table summarizes the DD statements.
DDNAME | Use | Format | Required or optional |
---|---|---|---|
ACBLIB | Input | PDS | Required when IMSCATHLQ=*NO |
DFSUDUMP | Input | Image copy, or Image copy 2 | Optional |
DARVSAM | Input | VSAM ESDS cluster | Optional |
DAR4ERRS | Input | Optional | |
DAR4USER | Input | LRECL=80 | Optional |
DAR13SI | Input | Required | |
SORTIN | Input | Required | |
SORT3CS | Input | Required | |
SYSOUT | Output | SYSOUT | Required |
SYSPRINT | Output | LRECL=133 | Required |
REPORTS | Output | LRECL=133 | Required |
RMODLIB | Input | PDS | Optional |
SNAPPIT | Output | LRECL=133 | Required |
SORTOUT | Work data set | Required | |
SORTWK01 | Work data set | Required | |
SORTWK02 | Work data set | Required | |
SORTWK03 | Work data set | Required |
- ACBLIB DD
- This statement defines the library that contains the DBD member that describes the database
analyzed by FABADA1. For example:
//ACBLIB DD DSN=IMSVS.ACBLIB,DISP=SHR
If the IMSCATHLQ=bsdshlq keyword is specified as a site default keyword (specifies to retrieve ACB definitions from the IMS directory instead of the ACB library), ACBLIB DD statement is ignored.
- DFSUDUMP DD
- This statement defines the image copy data sets of the areas to be analyzed. The data sets must
have been previously generated using the IMS Image Copy utility
(DFSUDMP0), the image copy function of IMS Image Copy Extensions, or
the Image Copy 2 utility (DFSUDMT0). Concatenating the data sets from different utilities is
prohibited. The data sets can reside on a tape or a direct-access device. You do not need to specify
this DD statement if input is a VSAM data set. Notes:
- When you use compressed data sets generated by IMS Image Copy Extensions, you must specify RMODLIB DD, which defines the library in which the IMS Image Copy Extensions compression routine resides.
- When you use data sets generated by the Image Copy 2 utility, DCB is required if the input data set is not labeled.
- When you use compressed data sets generated by the Image Copy 2 utility, you must apply DFSMSdss APAR 0W50226.
- LBI (Large Block Interface) image copy can be specified on this DD statement, but under the
following conditions, LBI image copy cannot be processed:
- DEDB Pointer Checker runs on an operating system that does not support LBI.
- An LBI compressed image copy that is produced by IMS Image Copy Extensions.
- DARVSAM DD
- This statement defines the VSAM cluster (area) which was analyzed by FABADA1. This DD statement is omitted if input is an image copy data set.
- DAR4ERRS DD
- This statement defines the input data set that contains the segment information records for all segments with invalid pointer. It is the SORTOUT data set from SORT4.
- DAR4USER DD
- This statement defines the input control statement data set. The data set can reside on a direct-access device, or be routed through the input stream.
- DAR13SI DD
- This statement defines the input data set that contains the segment information records. It is the DAR13SO data set from FABADA1.
- SORTIN DD
- This statement defines the input data set that contains the sorted segment and pointer information records. It is the SORTOUT data set from SORT3CS.
- SORT3CS DD
- This input data set contains information for DFSORT control statements. It is the output data set of FABADA1 defined by SORT3CS DD statement.
- SYSOUT DD
- This output data set contains the message produced by DFSORT.
- SYSPRINT DD
- This statement defines the output message data set. The data set can reside on a direct-access
device or printer, or be routed through the output stream. You should code your DD statement as
follows:
//SYSPRINT DD SYSOUT=A
- REPORTS DD
- This statement defines the output data set for the Pointer Chain Reconstruction report. The data
set can reside on a direct-access device or printer, or be routed through the output stream. You
should code your DD statement as follows:
//REPORTS DD SYSOUT=A
- RMODLIB DD
- This statement defines the library in which the IMS Image Copy Extensions compression routine resides. This DD statement is needed only if the input data set is compressed by IMS Image Copy Extensions.
- SNAPPIT DD
- This statement defines the output data set for the CI Map/CI Dump report. This data set can reside on a direct-access
device, or be routed through the input stream. You should code your DD statement as follows:
//SNAPPIT DD SYSOUT=A
- SORTOUT DD
- This work data set contains the sorted records. Required space is as same size as the SORTIN data set. Do not code DCB information in your JCL.
- SORTWKnn DD
- These are intermediate storage data sets used by DFSORT. See DFSORT Application
Programming Guide for more information about coding the
SORTWKnn DD statements.
Allocating twice the space used by the SORTIN data set is usually adequate for each work data set.