Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Keeping system-managed volume information consistent z/OS DFSMSrmm Implementation and Customization Guide SC23-6874-00 |
|
DFSMSrmm uses information in the TCDB to verify requests or to obtain information about volumes that are being added to DFSMSrmm. When you define volumes to DFSMSrmm by using the RMM ADDVOLUME subcommand with the STATUS(VOLCAT) operand, DFSMSrmm uses TCDB information to update the DFSMSrmm control data set. When there is a conflict between information in the TCDB and information in the control data set, DFSMSrmm uses the value in the TCDB. To control the way DFSMSrmm updates the information in the TCDB,
specify the DFSMSrmm EDGRMMxx parmlib OPTION command SMSTAPE
operand and the OPTION command OPMODE operand. See Defining system options: OPTION for
information about the DFSMSrmm EDGRMMxx parmlib OPTION command.
When you run DFSMSrmm in PROTECT mode, DFSMSrmm updates the TCDB.
If you are running DFSMSrmm in other modes, you can decide if and
when you want DFSMSrmm to update the TCDB. DFSMSrmm updates this TCDB
information:
You can use the DFSMSrmm EDGUTIL utility to perform these tasks:
Use the RMM CHANGEVOLUME subcommand with the LOCATION(mtl_name) operand to rebuild manual tape library information in the TCDB. If you use DFSMSrmm, ISMF, or operator commands to eject a volume, DFSMSrmm notes that the volume is 'intransit'. During eject processing, DFSMSrmm checks the setting of the DFSMSrmm EDGRMMxx OPTION SMSTAPE(PURGE) operand to determine whether to request deletion of volume information from the TCDB. This optionally overrides the ISMF default cartridge eject option you might have specified. If the volume record is not deleted, DFSMSrmm sets the volume destination information into the TCDB volume shelf location field. |
Copyright IBM Corporation 1990, 2014
|