Identifying basic rules

To start implementing PRTITION and OPENRULE commands, you should first list the basic rules you want to implement. For example:

For partitioning, all non-defined volumes are to be ignored.
For open rules, only volumes defined to DFSMSrmm can be used for both input and output.

After you have the basic rules identified, you have to identify the sets of volumes and how each is to be treated or managed. For example, the only volumes to be used on a system or partition might be all those volumes with the 'A' prefix. You can create a command that uses VOLUME(A*) and then select the TYPE based on whether you will always pre-define the volumes or allow them to be defined during cartridge entry, OPEN processing, or both.

For the PRTITION commands, you must consider the system-managed and non-system managed volumes separately. Be careful not to specify TYPE(RMM|ALL) with NOSMT(IGNORE) unless you really want EXPROC processing to skip the volumes. However, TYPE(RMM|ALL) with SMT(IGNORE) makes sense because DFSMSrmm causes OAM to ignore the volume and leave for another system or partition, and it also causes DFSMSrmm to skip EXPROC without checking if the volume is in the TCDB.

Consider the function provided by PRTITION and OPENRULE commands and whether it makes sense to exploit it. For example:

You can have separate commands based on whether the volume is defined to DFSMSrmm.
OPENRULE provides an automated way to ignore volumes at open time without the need to customize EDGUX100 or use EXPDT=98000 in JCL.
OPENRULE allows you to control the use of existing data sets, such as enforcing cataloging and reference only from the creating system.