PRTITION command operands

VOLUME | VOLUMERANGE

Use these operands to select volumes that are to be managed by this command. You must specify either VOLUME or VOLUMERANGE, and each command defines a set of one or more volumes. Sets cannot overlap within a TYPE, but a set can be a subset of another and such a subset is more specific. When you code a set with TYPE(RMM) and repeat that set with TYPE(NORMM), you can specify different operands for each set. If you want to use the same operands for the sets, you can do so by coding a type of ALL.

VOLUME: You can specify the volume as fully qualified or a volser prefix ending in *. A fully qualified volume is one to six alphanumeric, national or special characters. A volser prefix is zero to five alphanumeric, national, or special characters ending in an asterisk. Quotation marks are required for special characters, and the first character must not be blank. Any value ending in *, even if enclosed in quotation marks, is considered to be a volser prefix.
VOLUMERANGE: Use to select a subset of volumes based on starting and ending volser. Specify each volser value as one to six alphanumeric, national, or special characters. Quotation marks are required for each value regardless of the use of special characters, and the first character must not be blank. The end of range must not be lower than the start of the range.

TYPE(ALL | RMM | NORMM )

Use to identify the type of volumes selected by the PRTITION command. The volser is used to determine whether the volume is defined in the RMM CDS, and, depending on the function, the VOL1 label and HDR1 can be used. Therefore, DFSMSrmm cannot always determine if the volume is an existing one defined to DFSMSrmm. TYPE is determined as follows:

For system-managed library functions such as import/export, insert/entry, CUA, and eject, only the volser is used to determine whether the volume is defined in the RMM CDS.
For OPEN processing, the same rules as volume ignore processing are used (see Ignoring duplicate or undefined volume serial numbers), and the TYPE that is assigned is based on the following:
- TYPE(RMM)
  1. The volume serial number is defined in the control data set, and there is no HDR1 tape label for the volume.
  2. The volume serial number is defined in the control data set, and no labels are used (NL, NSL, or BLP with an NL tape).
  3. The 17 characters read from the HDR1 label of the mounted volume match the last 17 characters of the data set name in the control data set.
- TYPE(NORMM)
  1. The volume serial number is not defined in the control data set.
  2. The volume is defined, but the 17 characters read from the HDR1 label of the mounted volume do not match the last 17 characters of the data set name in the control data set.
For EXPROC processing, TYPE(RMM) always applies because EXPROC is driven only by volumes defined to DFSMSrmm.

For each set of volumes, you can code one command with RMM and another with NORMM, but only a single command if ALL is used.

RMM: The volume must already be defined to DFSMSrmm.
NORMM: The volume is not defined to DFSMSrmm.
ALL: Applies to all volumes regardless of whether they are defined to DFSMSrmm.

ALL is the default value.

SMT | NOSMT(action)

Use the SMT or NOSMT operands to select the action you want based on whether the volume is system-managed or not. You can specify a different action for NOSMT and SMT volumes.

System managed volumes are identified as follows:

Any request made through the EDGLCSUX programming interface that is used from the OAM installation exits: CBRUXCUA, CBRUXENT, CBRUXEJC, and CBRUXVNL.
During OPEN processing, the tape drive is identified as being in a system-managed library.
During EXPROC processing, the volume is in the TCDB, or the current location, or the home location is a system managed library.
In any other case, the volume is treated as non-system managed.

ACCEPT | IGNORE

Use this operand to identify the action to be taken by DFSMSrmm. The action applies to library entry/insert/import, eject/export, and CUA processing, OPEN processing, and to EXPROC processing. During OPEN processing, once the decision is taken about IGNOREing the volume, the PRTITION checking occurs first, and the action taken before the OPENRULE REJECT/ACCEPT processing occurs. As a result, the action taken by PRTITION can influence the TYPE processing by OPENRULE.

ACCEPT

DFSMSrmm processes the volume. During entry/insert import/export, CUA, and OPEN processing, the volume is added to the DFSMSrmm CDS if not yet defined. For NOSMT volumes, the location from the LOCATION operand is used to set the volume current and home locations. During EXPROC processing, the volume is processed for return to scratch. Note that a volume identified as TYPE(NORMM) with an action of ACCEPT, that is added to the CDS, now becomes a TYPE(RMM) volume for subsequent processing including OPENRULE processing.

By default, all volumes are processed during EXPROC, and all volumes are accepted during library entry/insert/import or OPEN processing. During OPEN processing and during library entry/insert/import processing, any undefined volumes are automatically added to the DFSMSrmm CDS using the library default volume entry status.

During OPEN processing, volumes are added to the CDS only if the current OPMODE is either WARN or PROTECT.

IGNORE

DFSMSrmm does not process the volume. During entry/insert/import processing, DFSMSrmm requests that OAM ignore the volume and leave it in the 'insert' category. During CUA and eject/export processing, the request for the volume is ignored. During EXPROC processing, the return to scratch processing is skipped. During OPEN processing:

For NORMM volumes, the volume is not added to the CDS
For RMM volumes, processing depends on the OPENRULE entries.

ACCEPT is the default value.

For system-managed volumes, DFSMSrmm EXPROC processing normally skips volumes that are not defined in the current TCDB or volumes in libraries that are not online and available. This means that you do not need to create commands for these cases.

During EXPROC processing, DFSMSrmm inventory management considers your PRTITION commands as well as any EXPROC control commands specified in the SYSIN file.

LOCATION(SHELF | LocdefHome)

Use this operand for NOSMT volumes that are of TYPE(NORMM) with action ACCEPT. DFSMSrmm's add volume processing uses the defined location value as the volume's home location and current location.

You can specify either SHELF or the name of a LOCDEF defined location that has a specified TYPE(STORAGE,HOME). DFSMSrmm validates this value against the LOCDEF commands.

Although the operand is only used for NORMM volumes, DFSMSrmm does not prevent you from specifying it on a PRTITION command for volumes of TYPE RMM or ALL.

The default value is SHELF.