Verifying the contents of the control data set

Specify VERIFY on the EXEC parameter of EDGUTIL to verify the contents of the control data set. For VERIFY processing, EDGUTIL reads sequentially through the different record types in the control data set. The record types are identified by the VERIFY options you specify. For each record DFSMSrmm validates key fields and checks information with related records in the control data set. DFSMSrmm issues an informational message to the SYSPRINT file for each discrepancy that is identified. You can verify all the information in the control data set at once, or select specific values to verify individual pieces of information.

For example, if you specify the STORE value as shown in Figure 1, DFSMSrmm reads all the storage location shelf information in the control data set. DFSMSrmm then reads volume information for only those volumes in the storage locations and verifies that the volumes include the correct location information.

Figure 1. Example of JCL for VERIFY(STORE)

//UTIL     EXEC PGM=EDGUTIL,PARM='VERIFY(STORE)'
//SYSPRINT DD SYSOUT=*
//MASTER   DD DISP=SHR,DSN=RMM.CONTROL.DSET

Note: The SYSIN commands in Figure 1 can be used to select a subset of volumes.

An optional output file, EDGSPLCS, can be specified with VERIFY(SMSTAPE) to request that control statements are generated that can be used with the EDGSPLCS utility. If changes to either the TCDB or library manager data are required, message EDG6846I is issued to SYSPRINT for each change. When VERIFY(SMSTAPE) processing is completed, you can edit the output data set to select those for further processing. When you have reviewed the statements and selected those you wish to process, you can run the EDGSPLCS utility to process the chosen statements. This process might be quicker than running MEND(SMSTAPE) once you have run VERIFY(SMSTAPE). See Using EDGSPLCS to issue commands to OAM for system-managed volumes for additional information about the EDGSPLCS utility. See EDGSPLCS file for the EDGUTIL utility for information about the EDGSPLCS file for the EDGUTIL utility.

When you specify VERIFY(ALL), and this completes successfully, DFSMSrmm resets the error indicator that is set when the control data set recovery processing was not successful. For VERIFY(VOLCAT), DFSMSrmm compares TCDB information with information in the DFSMSrmm control data set. For VERIFY(SMSTAPE), DFSMSrmm also retrieves the library manager information for each system-managed volume and compares the information to the TCDB and DFSMSrmm information. The function uses the DFSMSrmm control data set as the master. Use EDGUTIL MEND(SMSTAPE) to synchronize the TCDB and library manager database from DFSMSrmm. When you specify MEND, without SMSTAPE, EDGUTIL checks that DFSMSrmm is not active or that the DFSMSrmm control data set is not in use. MEND processing is performed the same way as VERIFY(ALL) and VERIFY(VOLCAT) processing. MEND processing cannot fix all discrepancies but those that can be fixed automatically are corrected by updating the control data set.

For some VERIFY functions when EDGUTIL is running, DFSMSrmm uses the information from the parmlib options of the running DFSMSrmm. For example, DFSMSrmm checks LOCDEF entries for the types and names of locations defined, and also checks the access system definitions for system managed libraries. If DFSMSrmm has never been started on the system where EDGUTIL is run, the parmlib options cannot be part of the verification. To cause certain parmlib information to be used, start DFRMM with the chosen parmlib member, and run EDGUTIL.

During VERIFY, EDGUTIL issues messages to indicate what stage of processing has been reached. These messages also go in the SYSPRINT file. An example of the SYSPRINT message file can be seen in Figure 2.

Figure 2. Sample EDGUTIL SYSPRINT output

 EDG6433I STARTING VERIFICATION OF RACK     RECORDS
 EDG6433I STARTING VERIFICATION OF VOLUME   RECORDS
 EDG6433I STARTING VERIFICATION OF DATA SET RECORDS
 EDG6433I STARTING VERIFICATION OF OWNER    RECORDS
 EDG6433I STARTING VERIFICATION OF PRODUCT  RECORDS
 EDG6434I NO PRODUCT      RECORDS IN CONTROL DATA SET
 EDG6433I STARTING VERIFICATION OF STORE    RECORDS
 EDG6434I NO EMPTY BIN    RECORDS IN CONTROL DATA SET
 EDG6434I NO INUSE BIN    RECORDS IN CONTROL DATA SET
 EDG6433I STARTING VERIFICATION OF VRS      RECORDS
 EDG6417I CONTROL DATA SET VERIFY SUCCESSFUL
 EDG6901I UTILITY EDGUTIL COMPLETED WITH RETURN CODE 0

You can correct errors that are found in the control data set by using one of these methods:

Restore the control data set to a level where the errors are not present. See Restoring the control data set for additional information.
Correct information in the control data set by using the RMM TSO ADD, CHANGE, DELETE, and LIST subcommands. See z/OS DFSMSrmm Managing and Using Removable Media for additional information.
Mend the control data set by specifying MEND on the EXEC parameter of EDGUTIL. See Mending the control data set for additional information.
Synchronize the TCDB and the library manager database from the DFSMSrmm control data set by specifying MEND(SMSTAPE) on the EDGUTIL EXEC parameter. See Synchronizing the contents of the control data set for additional information.
Synchronize the DFSMSrmm control data set from the TCDB by specifying MEND(VOLCAT) on the EDGUTIL EXEC parameter. See Synchronizing the contents of the control data set for additional information.

Note: The SYSIN commands in Figure 1 can be used to select a subset of volumes.

While verify is running in parallel with DFSMSrmm active, the DFSMSrmm control data set can be updated by other processing, and as a result, verify can report inconsistencies for resources that are updated during the verify processing. To avoid rerunning verify to clean up these inconsistencies; run EDGUTIL when there is little activity that updates the control data set.

Note: For VERIFY(SMSTAPE), MEND(SMSTAPE), and MEND(VOLCAT) only, DFSMSrmm obtains the latest information from the TCDB and library manager before any inconsistency is reported or corrected. This ensures that concurrent system processing is better tolerated.

DFSMSrmm processes each resource in turn, dependent on the VERIFY parameter, and validates related information as follows:

For every shelf location for a scratch volume, the associated volume must have the correct shelf location and media name and must be recorded as a scratch volume.
For every data set, the corresponding volume must be defined and the next and previous data set names in sequence must also be correctly defined.
For every defined owner, the corresponding volumes are checked for correct information.