Returning volumes to scratch status

The way in which volumes are returned to scratch depends on whether they are retained by the EXPDT retention method or the VRSEL retention method:

For volumes that use the EXPDT retention method, DFSMSrmm returns volumes to scratch when their expiration date has been reached and they require no other action than returning to scratch.
For volumes that use the VRSEL retention method, DFSMSrmm returns volumes to scratch that are already in pending release status, that can be returned to scratch on the running system, and require no other action than returning to scratch. These volumes are available to satisfy scratch mount processing or RMM TSO GETVOLUME subcommand requests.

To determine if a volume can return to scratch on the running system, DFSMSrmm considers if the scratch action has been manually confirmed, the TCDB, and catalog sharing. If the scratch action has been manually confirmed, the return to scratch can be processed on any system; otherwise, these conditions must be considered: The volume must be in the TCDB and the system-managed library must be defined. When catalogs are not fully shared, the volume must be returned to scratch on a system with access to the catalogs where the first file was created.

Return to scratch processing for system-managed volumes can be either synchronous or asynchronous with EXPROC processing. You use the SYSIN EXPROC command EDGSPLCS operand to select the type of processing you want. Asynchronous processing is handled by the EDGSPLCS utility.

When DFSMSrmm returns a volume to scratch status, DFSMSrmm clears this information from the control data set:

Volume description.
Jobname.
Accounting information.
Access list.
Volume owner.
Owner access.
Software product details. DFSMSrmm removes the volume from the product's list of volumes.

DFSMSrmm updates the volume information to indicate that the volume is no longer retained by a vital record specification. When a volume has been released manually using the RMM DELETEVOLUME subcommand, but is still retained by a vital record specification, DFSMSrmm sets the retention date to the current date and updates the volume information to indicate that the volume is no longer retained by a vital record specification.

When a volume returns to scratch status, DFSMSrmm also updates the related rack number record in the control data set. For volumes where the rack number matches the volume serial number, you can avoid this processing by removing the rack numbers. You can use the RMM CV volser NORACK subcommand followed by the RMM DR volser subcommand to remove the rack numbers from the control data set.

During inventory management expiration processing, DFSMSrmm calls the EDG_EXIT200 installation exit. The exit is called every time a volume is identified as ready to return to scratch. See Using the EDG_EXIT200 installation exit for information on the EDG_EXIT200 installation exit processing.

In addition, DFSMSrmm requests that all data sets recorded in the control data set for the volume are uncataloged. DFSMSrmm performs RACF processing as described in Table 1.