Use the EDGUPDT utility with the UPDATE parameter to update the active DFSMSrmm CDS with record updates created during testing or recovery. EDGUPDT uses a journal or journal backup or a concatenation of these data sets, which were created by DFSMSrmm running with the JRNLTRAN(YES) option in use. Using EDGUPDT ensures that, even after testing or recovery actions, you can ensure that the DFSMSrmm CDS reflects the actual content of the tape volumes in your library. The DFSMSrmm started procedure must be active when you run this utility.

When you prepare to run a test or recovery system with JRNLTRAN(YES), you would create a copy of the current production CDS – perhaps using the EDGHSKP/EDGBKUP utility with the BACKUP(COPY) parameter. Before you start DFSMSrmm on the test/recovery system create a new journal data set so that only the journal records created during the current test/recovery are available for use with EDGUPDT after all or part of testing/recovery is completed. You could, for example, backup the test/recovery system journal regularly and use the backup of the journal with EDGUPDT to maintain the production CDS. At the end of the test complete any required updates using the active test/recovery journal.

The EDGUPDT utility can only apply updates from the journal if the records have not been changed in the original CDS. Utility processing ensures that the CDS record has not been changed, deleted or added since the CDS copy was created.

If any errors occur when running EDGUPDT as a result of records being changed in the original CDS, processing continues but skips the update from the journal. Information messages are issued. At the end of processing a summary of record updates is written to the SYSPRINT file. If you rerun EDGUPDT using the same JOURNAL file to recover from a previous run error, you should expect an error message for each record that was successfully processed on the previous run.

DFSMSrmm processing ensures only that the volume and data set information in the CDS reflects processing in the test/recovery environment. DFSMSrmm does not make any changes to, nor validate that other, related system data sets are correct. For example:

TCDB

There is no consideration of whether a volume entry exists or not, or that the volume status remains in synch with the DFSMSrmm status of the volume.

UCAT

There is no consideration of whether data sets which were cataloged on the test/recovery system have corresponding catalog entries in the production environment.

Once your EDGUPDT processing is completed, you can optionally cross-check the DFSMSrmm CDS with related system data by:

1. Running EDGUTIL with PARM=’VERIFY(SMSTAPE)’.

   You can optionally limit the scope of the cross-checking by using the SYSIN DD statement to specify include and exclude conditions for the volumes to be processed.

2. Running EDGHSKP with PARM=’VERIFY,CATSYNCH’.

   Messages are issued during processing for data sets that are missing from the user catalogs, but defined as cataloged in DFSMSrmm.

The IDCAMS utility can be used to maintain either volume entries in the TCDB or data set catalog entries in the user catalogs.