Allocating data sets for inventory management

DFSMSrmm samples provided in SAMPLIB

EDGJHKPA Sample JCL for Allocating the Data Sets Required for Inventory Management
EDGPHKPA Sample OPC for Allocating the Data Sets Required for Inventory Management

Before running EDGHSKP, you must define several data sets. The data sets that are used by both the EDGHSKP utility and the DFSMSrmm subsystem address space must be pre-allocated and cataloged as shown in Table 1. These data sets can be directed to EAS by exploiting DC attributes, SMS ACS routines, and JCL keywords.

Table 1. DFSMSrmm EDGHSKP data sets
DD Statement	Preallocated, Cataloged, DASD Data Set	Description
ACTIVITY	Yes	Contains detailed information about data set related changes DFSMSrmm makes to the control data set during inventory management. This data set is required when you specify the VERIFY parameter.
BACKUP	No	Contains the backup copy of the DFSMSrmm control data set. Specify this data set to run backup processing for the control data set. You can back up directly to tape when you specify the BACKUP(DSS) parameter even when DFSMSdss concurrent copy is not available. BACKUP DD is optional when you specify BACKUP(COPY) and your environment is SMS managed.
DSSOPT	No	Contains COPY, DUMP, or RESTORE command options used by DFSMSdss during backup processing. See Customizing the DSSOPT DD statement for information about changing the commands.
EDGSPLCS	Yes	Contains statements to be used with the EDGSPLCS utility. They are created by EXPROC when you use the SYSIN EXPROC option EDGSPLCS(YES).
JRNLBKUP	No	Contains the backup copy of the DFSMSrmm journal. Specify this data set to run backup processing for the journal. DFSMSrmm uses IDCAMS to back up the journal when you specify the BACKUP(AMS) or BACKUP(DSS) parameter. You can back up directly to tape when you specify the BACKUP(DSS) parameter even when DFSMSdss concurrent copy is not available.
MESSAGE	Yes	Lists the messages the DFSMSrmm subsystem issues during inventory management. This data set is required.
REPORT	Yes	Contains a detailed report of DFSMSrmm vital record specification processing. Specify if you want a report when you have specified the VRSEL parameter.
REPTEXT	Yes	Contains the extract copy of the DFSMSrmm control data set. The extract copy is called the extract data set. You must specify either the REPTEXT DD statement or the XREPTEXT DD statement when you use the EDGHSKP RPTEXT parameter. If the DD name is XREPTEXT, RMM creates only extended records. If the DD name is REPTEXT, RMM creates all records except extended records.
SYSIN	No	An optional file that can contain commands to tailer inventory management processing. See SYSIN file for the EDGHSKP utility.
SYSPRINT	No	Contains the utility program messages that IDCAMS and ADRDSSU issue when backing up the DFSMSrmm control data set. The SYSPRINT data set is required when you specify the BACKUP parameter. This data set can be a SYSOUT file.
XREPTEXT	Yes	Contains the extract copy of the DFSMSrmm control data set. The extract copy is called the extract data set. You must specify either the REPTEXT DD statement or the XREPTEXT DD statement when you use the EDGHSKP RPTEXT parameter.

To avoid enqueue contention, consider these conditions:

These data sets cannot be created in the same job as they are used. If you plan to retain multiple versions of these data sets, consider using a subsequent job step to copy the data sets to a new GDG generation.
The JCL used to run EDGHSKP should specify DISP=SHR for these data sets.
Recommendation: For your regularly scheduled inventory management, use a data set to serialize the jobs that run EDGHSKP to ensure that only one copy of EDGHSKP is running on a system. You can run EDGHSKP with RPTEXT, EXPROC, or CATSYNCH options at the same time on different systems. You can also run EDGHSKP with the RPTEXT option at the same time on the same system. To run each of these tasks in parallel, for example, to run EXPROC on each system in a complex at the same time, use a different preallocated and cataloged data set for each job instead of including the ENQDSN DD statement.
To avoid problems that might occur when multiple EDGHSKP jobs are running together, add a DD statement to the job step that runs EDGHSKP as shown in Figure 1:
Figure 1. JCL for adding a DD statement to the EDGHSKP job step
```
//ENQDSN   DD DISP=OLD,DSN=RMM.HSKP.ENQ
```

Alternatively you can use the sample RMM OPC application which uses OPC special resources to prevent multiple jobs running together as described in Running DFSMSrmm with the IBM Tivoli Workload Scheduler for z/OS.

To protect the data sets that must be preallocated, cataloged, and on DASD, ensure that the RACF user ID associated with the DFSMSrmm subsystem has authority to write to the data sets.

Recommendation: Always run DFSMSrmm with the optional files ACTIVITY and REPORT. Maintain these files, as well as the MESSAGE, BACKUP, JRNLBKUP, SYSPRINT, REPTEXT, and XREPTEXT files, as GDGs or copy them to GDGs. You might find that multiple versions of the files are helpful for use in diagnosing problems or for creating reports.