DELETEVOLUME: Deleting volume information

Purpose

Before you begin:

If you are a user, to use the RMM DELETEVOLUME RELEASE subcommand:
- You need READ access to the STGADMIN.EDG.RELEASE resource profile to release your own volumes.
- If the STGADMIN.EDG.RELEASE resource profile is not defined, you need READ access to the STGADMIN.EDG.MASTER resource profile to release your own volumes.
- If COMMANDAUTH(DSN) is in effect, you need READ access to the STGADMIN.EDG.MASTER resource profile or the STGADMIN.EDG.RELEASE resource profile. You need ALTER access to the first file data set name in the DATASET class, or if there is no first file defined to DFSMSrmm, you need ALTER access to the volume in the TAPEVOL class.
If you are a storage administrator, there are different authorization possibilities depending on the security roles you have implemented:
- To use the RMM DELETEVOLUME subcommand, you need CONTROL access to the STGADMIN.EDG.MASTER resource profile. This allows all formats of the subcommand, except the use of the FORCE operand.
- To use the RMM DELETEVOLUME subcommand with FORCE, you also need UPDATE access to the STGADMIN.EDG.FORCE resource profile.
- To use the RMM DELETEVOLUME REMOVE subcommand, you need UPDATE access to the STGADMIN.EDG.DV.SCRATCH.volser profile.
- To use the RMM DELETEVOLUME REPLACE subcommand, you need UPDATE access to the STGADMIN.EDG.CRLSE.REPLACE profile.

Related Reading:

See Deleting information for volumes in multivolume sets for information about using the DFSMSrmm ISPF dialog to delete volumes in a multivolume set.
See z/OS DFSMSrmm Implementation and Customization Guide for information about using the DFSMSrmm parmlib OPTION COMMANDAUTH command and authorizing the use of the DFSMSrmm subcommands.

Use the DELETEVOLUME subcommand to delete information recorded by DFSMSrmm about a volume or to manually release a volume. You can release a volume anytime before data sets on the volume expire, or before the end of any retention period set by one or more vital record specifications. You must specify a volume serial number.

Use one of four operands to either schedule the volume for reuse, or to delete information about a volume:

RELEASE: To use the release actions specified for the volume and schedule the volume for reuse.
REMOVE: To delete information about a scratch volume.
FORCE: To delete information about any volume.
REPLACE: To delete information about a volume waiting to be replaced.

When you use RELEASE, DFSMSrmm begins processing any release actions specified for the volume. If you release a volume that resides in a storage location or that is in transit between locations, DFSMSrmm indicates that the volume is in release pending status and waits until the volume returns to the removable media library before scheduling any release actions specified for it.

Note: If the volume HOLD attribute has been set for the volume, DFSMSrmm will not release the volume.

If you use the FORCE, REPLACE, or REMOVE operands to delete information about a volume, DFSMSrmm deletes information about any data sets on the volume. If the volume is in a system-managed tape library, you can also specify the EJECT operand to direct the volume to an exit station. For volumes that reside in an automated tape library, the default is to eject the volume to a convenience output station. You can also specify EJECT(BULK) to eject the volume to a high capacity output station. Specify the EJECT operand with the FORCE, REPLACE, or REMOVE operands. Specify NOEJECT with the FORCE, REPLACE, or REMOVE operands when you do not want to direct the volume to an exit station.

DFSMSrmm ignores the EJECT operand if you specify it for a volume that does not reside in a system-managed tape library or for a logical volume in private status. For a volume in scratch status, DFSMSrmm issues an eject, and the VTS Library Manager database entry for the volume might be purged.

When you use the FORCE, REPLACE, or REMOVE operands for a volume in a system-managed tape library, DFSMSrmm purges information about the volume from the DFSMSrmm control data set based on the setting of SMSTAPE PURGE parmlib option. Any TCDB information is purged once the volume is successfully ejected. DFSMSrmm also purges information for volumes that reside in a non-system-managed tape library that is considered part of a system-managed tape library and is defined in the TCDB as shelf resident.

See Releasing volumes for more information on releasing volumes.

Format


                             .-RELEASE---.   
>>-+-DELETEVOLUME-+--volser--+-----------+---------------------->
   '-DV-----------'          +-REMOVE----+   
                             |       (1) |   
                             +-FORCE-----+   
                             '-REPLACE---'   

>--+--------------------------+--------------------------------><
   |        .-CONVENIENCE-.   |   
   +-EJECT(-+-------------+-)-+   
   |        '-BULK--------'   |   
   '-NOEJECT------------------'

Notes:

You must have CONTROL access to STGADMIN.EDG.MASTER security resource and UPDATE access to STGADMIN.EDG.FORCE security resource to use the FORCE operand.

Parameters

EJECT(CONVENIENCE|BULK)

Specifies directing a volume to an exit station, if you have also specified the FORCE, REPLACE, or REMOVE operands. Specify EJECT(BULK) to eject the volume to the high capacity output station. Specify EJECT(CONVENIENCE) to eject the volume to the convenience output station.

If you specify EJECT for a volume residing in a system-managed tape library, information about the volume is purged from the TCDB once the volume has been successfully ejected, and it is deleted from the DFSMSrmm control data set. If you specify EJECT for a logical volume in SCRATCH status, DFSMSrmm deletes the volume but does not perform an EJECT to the convenience station.

If you specify EJECT for a volume that is currently not in a system-managed library, DFSMSrmm ignores the EJECT. However, if the volume is considered part of the system-managed tape library and is defined in the TCDB as shelf resident, information about the volume is purged from the TCDB and from the DFSMSrmm control data set based on the setting of SMSTAPE PURGE parmlib option.

When specifying the FORCE, REPLACE, or REMOVE operands for a volume in a system-managed library , the volume is ejected to the convenience output station if you do not specify EJECT. CONVENIENCE is the default.

FORCE

Specifies deleting all information about a volume regardless of its current status, and to change the status of the rack number or bin number associated with the volume to empty. DFSMSrmm also uncatalogs all data sets on the volume.

If the volume resides in a system-managed library, DFSMSrmm ejects the volume and deletes the volume information in the DFSMSrmm control data set. Any volume information in the TCDB is purged once the volume is successfully ejected. If the volume resides in a non-system-managed library, DFSMSrmm simply deletes information from the DFSMSrmm control data set, unless the volume is considered part of a system-managed tape library and is defined in the TCDB as shelf resident.

You can specify the EJECT operand with FORCE to direct the volume to an exit station other than the convenience output station. During error recovery, you can use NOEJECT with FORCE to prevent the volume from being ejected. You can use FORCE to delete an empty stacked volume. Prior to using the FORCE operand to delete an empty stacked volume, you must remove all the contained volumes in a stacked volume using the RMM CHANGEVOLUME subcommand for each volume in the stacked volume container.

To use the FORCE operand, you must have CONTROL access to the STGADMIN.EDG.MASTER resource profile and UPDATE access to the STGADMIN.EDG.FORCE resource profile.

FORCE is mutually exclusive with RELEASE, REMOVE, and REPLACE. RELEASE is the default.

NOEJECT

Specifies preventing the volume from being ejected, if you also specified the FORCE, REPLACE, or REMOVE operands. For example, you can specify DELETEVOLUME FORCE NOEJECT to purge information about the volume from the DFSMSrmm control data set without ejecting the volume. Volume information in the TCDB remains unchanged. You can use this function during error recovery processing.

RELEASE

Specifies releasing the volume according to the release actions set for the volume. You can use RELEASE only for logical and physical volumes for which the volume HOLD attribute has not been set.

RELEASE is mutually exclusive with REMOVE, FORCE, and REPLACE. RELEASE is the default.

REMOVE

Specifies deleting information recorded by DFSMSrmm about a scratch volume that is no longer wanted, and changing the status of the rack number associated with the volume to empty. You can only specify REMOVE for a scratch volume.

You can use REMOVE to delete an empty stacked volume. Prior to using the REMOVE operand to delete an empty stacked volume, you must remove all the contained volumes in a stacked volume using the RMM CHANGEVOLUME subcommand for each volume in the stacked volume container.

You can specify the EJECT operand with REMOVE to direct the scratch volume to an exit station other than the convenience output station. During error recovery, you can use NOEJECT with REMOVE to prevent the volume from being ejected.

REMOVE is mutually exclusive with RELEASE, FORCE, and REPLACE. RELEASE is the default.

REPLACE

Specify to delete all information about a volume that is waiting to be replaced. REPLACE can only be specified when REPLACE is the only release action.

You can specify the EJECT operand with REPLACE to direct the volume to an exit station other than the convenience output station. During error recovery, you can use NOEJECT with REPLACE to prevent the volume from being ejected.

REPLACE is mutually exclusive with RELEASE, REMOVE and FORCE. RELEASE is the default.

volser

Specifies the volume serial number of the volume to be deleted. A full volume serial number is one-to-six alphanumeric, national, or special characters. Enclose it in single quotation marks if it contains any special characters. You can only specify a particular volume serial. A volume serial number is required and must follow the DELETEVOLUME subcommand.

Examples

Task: Delete information about the scratch volume with volume serial number 8E1U01.

Command:

RMM DELETEVOLUME 8E1U01 REMOVE

Task: Delete a volume if the SMS-managed library is no longer available.

Command:

RMM DELELETEVOLUME volser NOEJECT FORCE

Return codes

See DFSMSrmm return codes and reason codes for DFSMSrmm reason codes.

0: Subcommand completed normally.
4: Warning. Subcommand completed but some operands could have been ignored or modified. DFSMSrmm sets a reason code.
8: User not authorized.
12: Subcommand ended with an error. DFSMSrmm sets a reason code.
16: Error. The DFSMSrmm subsystem is not active.
20: Error. The data is incomplete or incorrect and the TSO user has set NOPROMPT.
24: The TSO subcommand is not APF authorized.
28: The user pressed the attention key.