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


OPENRULE command operands

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

ACCEPT | IGNORE | REJECT
Use this operand to identify the action to be taken by DFSMSrmm. The action applies to OPEN processing.
ACCEPT
DFSMSrmm processes the volume. This attempt to open a file on the tape volume is also subject to DFSMSrmm open-time volume validation, and if allowed, the use of the volume and file is recorded by DFSMSrmm. ACCEPT means that the volume is accepted provided that the validation performed by DFSMSrmm at OPEN time allows the volume to be used. See the following for additional information:

ACCEPT is the default value.

IGNORE
DFSMSrmm does not process the volume. When the mounted volume matches the requested volume, the use of the volume is ignored by DFSMSrmm. No validation of the volume is performed, and there is no recording of the volume or file. DFSMSrmm processing is as if the EDG_EXIT100 exit requested the volume be ignored. Volume ignore processing is attempted if either IGNORE is specified or the EDG_EXIT100 exit requests ignore. For ignore processing to be successful, the user must be authorized to ignore the volume. The ignore processing is just as if you coded EXPDT=98000 in the JCL and were using the sample EDGUX100 exit module shipped with DFSMSrmm.
The use of action IGNORE enables you to ignore any specific or non-specific volume requests, including all those for system-managed volumes. However, you must use caution when using the IGNORE action with non-specific requests for system-managed volumes of type NORMM. Ensure that the PRTITION entries for the ignored NORMM volumes also specify IGNORE. If the PRTITION entry does not specify IGNORE, the DFSMSrmm processing of the CUA request (scratch change to private) causes the volume to be added automatically to the DFSMSrmm CDS, however the Open/Close/End-of-Volume (O/C/EOV) processing is not recorded.
Note: For specific volume requests, DFSMSrmm uses the requested volume to determine whether the volume is defined to DFSMSrmm, and uses the VOL1 label volser only to validate duplicate volumes. The requested volume is matched to the correct OPENRULE, and in this way correctly handles the identification and ignore action for duplicate volumes.
REJECT
DFSMSrmm must prevent OPEN processing from allowing use of the volume. For a specific volume, this results in the OPEN request failing. For a non-specific volume, the volume is dismounted by the system and another mount request issued.
ANYUSE | INPUT | OUTPUT (action)
Use this operand to identify the type of OPEN request issued by the application. It reflects the applications intent towards the data.
ANYUSE
The application is attempting either to read from or write to the tape volume. ANYUSE is the default operand. When you specify the INPUT or OUTPUT operands, they override the default.
INPUT
The application is attempting to read from the tape data set.
OUTPUT
The application is attempting to write to the tape data set.
BY(SYSID | CATLG)
Use this operand for volumes of TYPE RMM to specify that the REJECT action only applies if the volume is defined to DFSMSrmm, the request is for a specific volume, and the BY condition is not met. Otherwise, the ACCEPT action is used.

When specified for TYPE(NORMM), the operand is parsed successfully, but is then ignored and never used by DFSMSrmm because volumes of TYPE(NORMM) cannot have existing tape data set records and are not defined to DFSMSrmm.

You can specify one or more of the values: SYSID and CATLG. Use this operand to specify that the REJECT action applies if either applied by SYSID or by CATLG. Otherwise, the ACCEPT action is used. There is no default value.

SYSID
Use this operand to specify that for non-scratch volumes use of a volume is to be rejected if the creating SYSID of the first file does not match the current SYSID. This operand might help you if you have a common scratch pool across multiple systems, but once a volume is used, you only want the volume used or referenced on the system from which the data was created. When the creating SYSID matches the current SYSID, the ACCEPT action is used.
CATLG
Use this operand to specify that existing tape data sets must be referenced by their catalog entry. When the data set is referenced by its catalog entry, the ACCEPT action is used.

DFSMSrmm checks to see if there is an existing data set record defined to RMM and applies this rule if the data set record exists regardless of the disposition specified for the data set. In cases where only the first file is being recorded by DFSMSrmm, a data set record does not exist for file 2 onwards, but DFSMSrmm processing assumes that they exist.

BY(SPECIFIC | NONSPECIFIC | ANY)
Use this operand to identify the requests to which the IGNORE action applies.
SPECIFIC
The IGNORE action only applies if a specific volume is requested. Otherwise, the ACCEPT action is used.
NONSPECIFIC
The IGNORE action only applies if a non-specific request is being processed. The volser in the mount message is either PRIVAT or SCRTCH. Otherwise, the ACCEPT action is used.
ANY
The IGNORE action applies to all types of request.

ANY is the default value.

TYPE(ALL | RMM | NORMM )
Use to identify the type of volumes selected by the OPENRULE command. The volser and other values determined during OPEN are used to determine the TYPE, as follows:
  • 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 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 is 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.

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. Single 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. Single 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.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014