Examples of converting REJECT commands to OPENRULE and PRTITION commands

Table 1 provides simple examples that show the conversion of REJECT commands to OPENRULE and PRTITION commands.

Note: For simplicity, the examples in Table 1 only show how OPENRULE and PRTITION commands can be constructed from existing REJECT commands, considered one command at a time. While that approach will work, it might lead to unnecessary effort and complexity. A better method is to simplify the task by first determining a global policy and then adding to a parmlib only the OPENRULE and PRTITION commands required to implement that policy.

Table 1. Converting REJECT commands to OPENRULE and PRTITION commands
Example	REJECT Command	OPENRULE and PRTITION Commands
1	REJECT ANYUSE(prefix)	OPENRULE VOLUME(prefix) TYPE(RMM) ANYUSE(REJECT) PRTITION VOLUME(prefix) TYPE(NORMM) SMT(IGNORE) NOSMT(IGNORE)
In example 1, the existing REJECT ANYUSE command is being used to control partitioning and to reject volumes at OPEN time. The right most column shows the equivalent PRTITION and OPENRULE commands. Remember that a REJECT with a prefix, when used at OPEN time, applies only to volumes defined to RMM, so TYPE(RMM) is used for OPENRULE with an action of ANYUSE(REJECT). However, for partitioning, REJECT ANYUSE applies only to volumes not defined to RMM, so TYPE(NORMM) with ACTION(IGNORE) is used for PRTITION.
2	REJECT OUTPUT(prefix)	OPENRULE VOLUME(prefix) TYPE(RMM) OUTPUT(REJECT) INPUT(ACCEPT)
The sample commands in example 2 show REJECT is used only for OPEN time rejects. A REJECT with a prefix, when used at OPEN time, applies only to volumes defined to RMM so TYPE(RMM) is used for OPENRULE. The REJECT OUTPUT allows input processing, so the INPUT(ACCEPT) option is coded on the OPENRULE for completeness, although INPUT(ACCEPT) is the default.
3	REJECT ANYUSE(*)	OPENRULE VOLUME() TYPE(NORMM) ANYUSE(REJECT) PRTITION VOLUME() TYPE(NORMM) SMT(IGNORE) NOSMT(IGNORE)
The sample commands in example 3 show REJECT is used by both partitioning and for OPEN time rejects. A REJECT with PREFIX() applies only to volumes not* defined to RMM, so TYPE(NORMM) is used for both OPENRULE and for PRTITION.
4	/* Example for SYSA only / REJECT ANYUSE(JP) REJECT ANYUSE(JX) REJECT ANYUSE()	/* Allow read of undefined volumes / OPENRULE VOLUME() TYPE(NORMM) - OUTPUT(REJECT) /* Ignore for input selected system managed volumes if authorized / OPENRULE VOLUME(JP) TYPE(NORMM) - INPUT(IGNORE) OUTPUT(REJECT) OPENRULE VOLUME(JX) TYPE(NORMM) - INPUT(IGNORE) OUTPUT(REJECT) / Global partition rule - ignore all smt volumes / PRTITION VOLUME() TYPE(RMM) - SMT(IGNORE) NOSMT(ACCEPT) PRTITION VOLUME() TYPE(NORMM) - SMT(IGNORE) NOSMT(IGNORE) / This partition owns JT* volumes if predefined / PRTITION VOLUME(JT) TYPE(RMM) SMT(ACCEPT)
The sample commands in example 4 shows the following: Three systems, SYSA, SYSB, and SYSC, that are each allowed to use only a single range of system-managed volumes (JT, JP, JX). The example shows the commands for SYSA only. Each system has its own CDS and TCDB. System-managed volumes are not to be automatically defined to DFSMSrmm. Private volumes can be shared. Undefined non-system-managed volumes can be used for input. EDGUX100 is customized to automate the ignoring of private system-managed volumes from other partitions, and the ignoring of undefined non-system-managed volumes. This is based on the RMM API checking if a volume is defined to RMM. The following RACF FACILITY class profiles are also required: `STGADMIN.EDG.IGNORE.TAPE.NORMM.JP* STGADMIN.EDG.IGNORE.TAPE.NORMM.JX*` The customization in the EDG_EXIT100 installation exit is no longer needed and can be removed. The OPENRULE with INPUT(IGNORE) provides the same function.