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


Using the tape relabeling resources

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

DFSMSrmm supports three basic label types: NL, SL, and AL. You can switch between any of these basic types by specifying the new label type in your JCL when creating the first file on a volume.

Using EDGINERS to relabel tape volumes requires a separate mount of the volume and must be performed prior to the use of the volume.

Changing volume labels at OPEN time when creating the first file does not require EDGINERS or the INIT release action. Tape volume labels can be created or destroyed at any time regardless of volume status when the user has the required access to a security resource. Scratch volumes can only be used for nonspecific output requests.

To enable this processing, use the STGADMIN.EDG.LABEL.volser and STGADMIN.EDG.NOLABEL.volser profiles in the FACILITY class. These profiles are described in Authorizing DFSMSrmm users and ensuring security. If you do not create the appropriate security profiles in FACILITY class, the volume must be in user status.

When DFSMSrmm allows the tape labels to be created or destroyed, it automatically replies to the operator WTOR to provide the required information. In addition, for any volume with the return to scratch release action, which has a NL label type at release time, DFSMSrmm sets the INIT release action to ensure that only standard label tapes are returned to the scratch pool.

Your installation can bypass this processing for any volume by using the EDG_EXIT100 installation exit to request that DFSMSrmm ignore the volume. EDG_EXIT100 is called before any tape label conflicts are resolved. See Using the DFSMSrmm EDG_EXIT100 installation exit.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014