EXEC parameters for EDGUTIL

Figure 1 shows the EXEC parameters for EDGUTIL.

Figure 1. EDGUTIL EXEC parameters


>>-+-CREATE------------------+---------------------------------><
   +-MEND--------------------+   
   +-+-MEND----+-------------+   
   | +-(-------+             |   
   | +-SMSTAPE-+             |   
   | '-)-------'             |   
   +-+-MEND---------------+--+   
   | +-(------------------+  |   
   | |   .-,----------.   |  |   
   | |   V            |   |  |   
   | +-----+-ALL----+-+---+  |   
   | |     +-DSN----+     |  |   
   | |     +-OWNER--+     |  |   
   | |     +-PP-----+     |  |   
   | |     +-RACK---+     |  |   
   | |     +-STORE--+     |  |   
   | |     +-VOLUME-+     |  |   
   | |     +-VRS----+     |  |   
   | |     '-VOLCAT-'     |  |   
   | '-)------------------'  |   
   +-UPDATE------------------+   
   '-+-VERIFY--------------+-'   
     +-(-------------------+     
     | .-ALL, VOLCAT-----. |     
     | | .-,-----------. | |     
     | | V             | | |     
     +-+---+---------+-+-+-+     
     |     +-DSN-----+     |     
     |     +-OWNER---+     |     
     |     +-PP------+     |     
     |     +-RACK----+     |     
     |     +-STORE---+     |     
     |     +-VOLUME--+     |     
     |     +-VRS-----+     |     
     |     +-VOLCAT--+     |     
     |     '-SMSTAPE-'     |     
     '-)-------------------'

CREATE

Use CREATE to create a new control data set control record.

MEND

Use MEND to detect and fix errors in your control data set. If you have system-managed volumes, DFSMSrmm also uses information from the TCDB and the library manager database. The errors you encounter might have been created during conversion activities or as a result of system failures. When you specify the MEND parameter with no other values, the default processing performed by DFSMSrmm checks for all errors in your control data set, and in addition, if you have system managed volumes, DFSMSrmm uses information from both the TCDB and the library manager data base. Use the MEND function only with guidance from the IBM Support Center or to update the control data set once stacked volumes support is enabled. Run MEND on an unused control data set or with DFSMSrmm inactive. See Mending the control data set for more information.

MEND(SMSTAPE)

Use MEND(SMSTAPE) to update the TCDB and the library manager database using information from the DFSMSrmm control data set. Use MEND to update the DFSMSrmm control data set based on information from the TCDB and the library manager database. Before running MEND(SMSTAPE), you should first use the VERIFY(SMSTAPE) option to find information that is not the same in the DFSMSrmm control data set, TCDB, and the library manager database. After running VERIFY(SMSTAPE) and before running MEND(SMSTAPE), you can update the control data set using DFSMSrmm TSO subcommands to correct DFSMSrmm information.

MEND(ALL,DSN,OWNER,PP,RACK,STORE,VOLUME,VRS,VOLCAT)

Use MEND to correct errors in the control data set. You can correct all the control data set information or select specific types of information.

The values you can specify on MEND are:

ALL: DFSMSrmm uses control data set information only and corrects all control data set information at once. No processing of the TCDB or library manager is performed.
DSN: DFSMSrmm corrects data set information based on comparing data set information to volume information.
OWNER: DFSMSrmm corrects owner information based on comparing owner information to volume information.
PP: DFSMSrmm corrects product information based on comparing software product information to volume and library shelf location information.
RACK: DFSMSrmm corrects rack number information based on comparing library shelf location information to volume information.
STORE: DFSMSrmm corrects bin number information based on comparing storage location shelf information to volume information.
VOLCAT: DFSMSrmm compares volume status and library name information in its control data set with the same information in the TCDB. If the information is different, DFSMSrmm corrects the control data set information.Not all of the information found to be different is corrected by DFSMSrmm MEND processing. EDGUTIL messages will be issued for differences found and whether they are corrected.
VOLUME: DFSMSrmm corrects volume information based on comparing information about data sets, software products, owners, and shelf locations in the library and storage locations.
VRS: When correcting vital record specification errors, DFSMSrmm validates the next vital record specification information to see if a name vital record specification exists. If DFSMSrmm does not find a next vital record specification, DFSMSrmm fixes the information about the next vital record specification. DFSMSrmm checks for generic data set name, job name, and volser masks. DFSMSrmm also checks that the location information in each vital record specification is valid by comparing it to the LOCDEF entries. If an invalid or an unsupported generic mask is found, DFSMSrmm deletes the vital record specification. If an incorrect location type is found, DFSMSrmm corrects it based on the LOCDEF and SMS library definitions.

UPDATE

Use UPDATE to:

Update an existing control data set control record.
Mark the DFSMSrmm control data set as synchronized or not synchronized with the user catalogs so the control data set is synchronized at a later time.
Enable extended bin support.

VERIFY(ALL,DSN,OWNER,PP,RACK,SMSTAPE,STORE,VOLUME,VRS,VOLCAT)

Use VERIFY to verify the information in the control data set and identify errors. You can verify all the information in the control data set at once or select specific values to verify individual pieces of information. If stacked volume support is enabled, DFSMSrmm checks the consistency of stacked volumes and the volumes in the stacked volumes.

To correct inconsistencies found during VERIFY processing, use the DFSMSrmm TSO subcommands to correct the inconsistencies. Use MEND(SMSTAPE) to drive changes to the TCDB and library manager database from the DFSMSrmm control data set or use access method services commands to correct errors in the TCDB.

If both VOLCAT and SMSTAPE are specified with VERIFY, DFSMSrmm does only the SMSTAPE processing.

The values you can specify on VERIFY are:

ALL: DFSMSrmm verifies all information at once, except for VOLCAT and SMSTAPE, which do consistency checking against the TCDB.
DSN: DFSMSrmm validates data set information and compares data set information to volume information.
OWNER: DFSMSrmm validates owner information and compares owner information to volume information.
PP: DFSMSrmm validates product information and compares software product information to volume and library shelf location information.
RACK: DFSMSrmm validates rack number information and compares library shelf location information to volume information.
SMSTAPE: DFSMSrmm performs extra processing with the TCDB and library manager database when SMSTAPE is specified. DFSMSrmm scans both the DFSMSrmm control data set and the TCDB sequentially to find DFSMSrmm volumes that are not in the TCDB and TCDB volumes that are not in the DFSMSrmm control data set. DFSMSrmm also checks any volume that is found to be system-managed, either by definition to DFSMSrmm or retrieved from the TCDB, against the library manager database for an IBM automated tape library.
STORE: DFSMSrmm validates bin number information and compares storage location shelf information to volume information.
VOLCAT: DFSMSrmm compares volume status and library name information in its control data set with the same information in the TCDB. If the information is different, DFSMSrmm issues an information message, but sets a minimum return code of 0.
VOLUME: DFSMSrmm compares volume information to information about data sets, software products, owners, and shelf locations in the library and storage locations.
VRS: For vital record specification checking, DFSMSrmm validates the next vital record specification information to see if a name vital record specification exists. DFSMSrmm checks for generic data set name, job name, and volser masks. DFSMSrmm also checks that the location information in each vital record specification is valid by comparing it to the LOCDEF entries. If DFSMSrmm does not find a next vital record specification, it issues an information message, but sets a minimum return code of 0.

The default is VERIFY(ALL,VOLCAT).