z/OS DFSMSrmm Implementation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Confirming global release actions

z/OS DFSMSrmm Implementation and Customization Guide
SC23-6874-00

If the RMM CHANGEVOLUME subcommand with * CONFIRMRELEASE operands is issued to confirm global release actions, for any volume with the action outstanding, DFSMSrmm marks the corresponding action complete. Global release action confirmation takes place during expiration processing, but only if all volumes are processed, just prior to when DFSMSrmm performs a check for outstanding global confirmation or if the volume expiration date has been reached.

When you use the NOTIFY release action, the NOTIFY release action must be confirmed in order for any other release action to be processed. DFSMSrmm can confirm this automatically by sending a notify message, or you can confirm it manually. See OPTION command operands for more information about the NOTIFY parmlib OPTION.

If the ‘return to owner’ action is confirmed, the volume is deleted from the DFSMSrmm control data set. If the erase or initialize release actions are confirmed, DFSMSrmm deletes the data set information for those volumes with the actions outstanding. If erase is confirmed, DFSMSrmm sets the initialize action as outstanding so that the correct volume labels can be written to the erased volume.

When you use global confirmation for the ERASE release action, you process the volume outside the control of DFSMSrmm. Possibly, you could have degaussed the volume or used a bulk degaussing machine. Remember that you should only degauss certain types of tape volumes.
Note: Do not degauss IBM 3592, 3590, or similar media that are pre-formatted with servo tracks. Use of a degausser renders the volume unusable.

If the RMM DELETEVOLUME subcommand with the RELEASE operand was issued, DFSMSrmm changes the volume status to ‘pending release’ during subcommand processing. Use expiration processing to complete the release process. These volumes are returned to scratch during the first EDGHSKP run, if no other release actions are required.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014