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


Defining DFSMSrmm to z/OS

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

Add an entry to IEFSSNxx to define the DFSMSrmm subsystem to z/OS. Specify the DFSMSrmm subsystem name shown in Figure 1. Figure 1 shows where to place the subsystem name. Place the DFSMSrmm entry after the JES2 or JES3 entry and before the NetView entry to ensure that NetView automation receives the write-to-operator messages once DFSMSrmm has updated them. Additionally, if you have any software identified as a subsystem that is dependent on open/close/end-of-volume processing, place the names after the DFSMSrmm entry. DFSMSrmm has no other dependencies on the sequence of subsystem names.

Note: The DFSMSrmm subsystem can be defined to allow the SSI initialization routine for DFSMSrmm to be invoked in parallel with other SSI initialization routines. See z/OS MVS Initialization and Tuning Guide for more information.
Figure 1. Defining DFSMSrmm to z/OS through IEFSSNxx with subsystem inactive
SUBSYS SUBNAME(JES2)              /* JES2 PRIMARY SUBSYSTEM START   */
  PRIMARY(YES)  START(YES)
SUBSYS SUBNAME(DFRM)              /* Name of the DFSMSrmm subsystem */
SUBSYS SUBNAME(AOPA)              /* Netview                        */
where:
DFRM
Specifies the subsystem name. You can use any unique subsystem name, one to four characters long.
Although the subsystem name can be one-to-four characters long, the subsystem name must be four characters and must match the first four characters of the procedure name under these conditions:
  • You have not added EDGSSSI, as described in Step 22: Initializing the DFSMSrmm subsystem and tape recording, and you want DFSMSrmm to perform the EDGSSSI processing when it starts by replying RETRY to message EDG0103D.
  • You use the EDGRESET utility or the START command
     S DFRMM,OPT=RESET
    and plan to restart DFSMSrmm without an IPL.

Run DFSMSrmm as a subsystem that is started under the JES2 or JES3 subsystem, rather than under the master subsystem. When choosing the DFSMSrmm subsystem name, the subsystem name must not exactly match the DFSMSrmm procedure name, unless you specify SUB=JES2 or SUBJ=JES3 on each START command. For example, if you use DFRM as the subsystem name, use DFRMM as the procedure name.

You must run DFSMSrmm under the JES2 or JES3 subsystem to use these functions:
  • Use the DFSMSrmm NOTIFY function which automatically notifies volume and product owners when the volumes they own become eligible for release or when product volumes are added.
  • Use the SYSOUT facilities like //SORTOUT DD SYSOUT=*.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014