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


Ejecting volumes from system-managed libraries

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

You can eject physical volumes from a system-managed library by using various methods. One way is to list a number of volumes and then enter eject commands from the list. You normally use export processing to eject logical volumes. For information about export processing, see Using DFSMSrmm with the IBM totalstorage virtual tape server.

You can also eject volumes from a system-managed library by changing the library name with the RMM CHANGEVOLUME subcommand. When you issue the command, DFSMSrmm requests that the volume is ejected from the original library. Information about the volume is changed in the control data set, and the TCDB record is optionally deleted. If the target library is an automated tape library, the operator must physically transfer the volume. If the source and target libraries are both manual tape libraries, then physical movement is only needed if the volume is to be moved to another shelf location.

You can also mark a volume as ejected from a system-managed library or change the location name to SHELF when the library is not known or offline by using the RMM CHANGEVOLUME subcommand with the FORCE operand. To use the FORCE operand, you must have access to the STGADMIN.EDG.MASTER and STGADMIN.EDG.FORCE RACF® profiles. When you use the FORCE operand to update a volume in a system-managed library, DFSMSrmm attempts to update the TCDB. Your request to update DFSMSrmm is completed even when the TCDB is not updated.

DFSMSrmm does not automatically eject volumes from system-managed libraries after completing vital record processing and storage location management processing. See How storage location management processing works for information about adding a job step to eject volumes at a time you determine.

The DFSMSrmm control data set is updated even if ejects are not driven by DFSMSrmm. The eject is detected using the OAM eject installation exit, and DFSMSrmm can control the disposition of the TCDB volume information. 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.

Figure 1 shows how you can eject a volume from an automatic tape library or from a manual tape library to a convenience output station using the RMM CHANGEVOLUME subcommand or the RMM DELETEVOLUME subcommand.

Figure 1. Requesting the eject of a volume
RMM CHANGEVOLUME A12345 EJECT(CONVENIENCE)
RMM CHANGEVOLUME A12345 LOCATION(new_lib)
RMM CHANGEVOLUME A12345 LOANLOC(set_loc)
RMM DELETEVOLUME A12345 REMOVE
RMM DELETEVOLUME A12345 FORCE

You can specify the EJECT operand on the RMM CHANGEVOLUME and DELETEVOLUME subcommands. Specify the EJECT(BULK) operand to direct the ejected volume to the high capacity input/output station. Specify the EJECT(CONVENIENCE) operand to direct the ejected volume to the convenience output station. If you specify EJECT(BULK) and the high capacity output station is not installed, then the eject is routed to a convenience output station. If there is no convenience output station, the eject is then routed to a single cell facility. In a manual tape library, DFSMSrmm ignores the BULK values and the CONVENIENCE values and the cartridge is ejected.

The RMM CHANGEVOLUME subcommand with the HOME operand does not cause an eject or a move as it is only used to update the home location name.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014