Defining tapes not available on systems: REJECT

Note: While the REJECT command is still supported by DFSMSrmm, you should use the OPENRULE (described in Controlling the use of tape volumes: OPENRULE) and PRTITION (described in Partitioning tape volumes: PRTITION) commands to prevent a range of tapes from being used on a particular system. If you are already using REJECT commands, you should consider converting them to OPENRULE and PRTITION commands. See Converting REJECT commands to PRTITION and OPENRULE commands.

Use the REJECT command to prevent a range of tapes from being used on a particular system. For example, you can reject production tapes on a development system.

This command is useful under these conditions:

Using a shared RACF data set and the security profiles for a volume allow the volume to be used on all systems.
To partition tape libraries as described in Partitioning system-managed tape libraries.
Preventing a stacked volume from being used outside a VTS.

The REJECT command helps you limit tape usage at the system level. Figure 1 shows an example of the REJECT command and the operands you can code in the parmlib member EDGRMMxx.

Figure 1. Parmlib member EDGRMMxx REJECT command examples

REJECT OUTPUT(CC12*)
REJECT ANYUSE(VM1*),OUTPUT(VM*)
REJECT ANYUSE(DD0*)
REJECT ANYUSE(*)