Implementation depends on whether you already use REJECT commands.

If you use REJECT commands, you have to convert from the use of REJECT commands in order to use the PRTITION and OPENRULE commands. See Converting REJECT commands to PRTITION and OPENRULE commands for information about converting from the use of REJECT commands.

If you do not use REJECT commands or PRTITION and OPENRULE commands, DFSMSrmm processing uses the default PRTITION and OPENRULE commands. These default commands implement almost all of the default processing for releases prior to z/OS V1R10 DFSMSrmm. In addition, they offer the ability to dynamically add non-system managed volumes to the CDS as volumes are used. The OPENRULE and PRTITION commands can be used on z/OS V1R10 and later releases. Releases prior to z/OS V1R10 use REJECT commands, if they are defined in parmlib.

To start implementing PRTITION and OPENRULE commands, do the following:

1. Review the customization of your installation exits, and identify the OPENRULE and PRTITION commands that can be used instead. See Reviewing installation exits for additional information.
2. Identify the global PRTITION and OPENRULE commands that can be used. See Identifying basic rules for additional information.
3. Review your requirements across all systems images, and identify the sets of volumes that are to be used on each system. Identify the PRTITION and OPENRULE commands required for each system to minimize parmlib maintenance as your storage requirements change.
4. Code the parmlib commands. DFSMSrmm has an option to have a shared or common parmlib member and then a system specific parmlib member for each system. The global PRTITION and OPENRULE commands are good candidates for the common parmlib member, and the more specific volume sets related commands are best placed in the system specific parmlib member.
5. Create new parmlib members that are ready for implementation, leaving the existing parmlib member as a fallback.
6. Refresh the DFRMM started procedure to use the new parmlib members (F DFRMM,M=xx).
7. At a later time, remove any unnecessary exit customization, and remove the old parmlib member that is no longer required for fallback.