Step 8: Updating the procedure library

DFSMSrmm sample provided in SAMPLIB

EDGDFRMM Sample to Create a Procedure in SYS1.PROCLIB

Perform this step once for each z/OS image.

Create a procedure in SYS1.PROCLIB to start the DFSMSrmm subsystem address space.

Tip: Figure 1 shows sample JCL that you can use to create the procedure.

Figure 1. Creating a procedure in SYS1.PROCLIB using the recommended JCL

 //DFRMM PROC M=00,OPT=MAIN
 //IEFPROC EXEC PGM=EDG&OPT.,PARM='&M',TIME=1440,REGION=40M
 //EDGPDOX DD DISP=SHR,DSN=RMM.&SYSNAME..RMMPDOX
 //EDGPDOY DD DISP=SHR,DSN=RMM.&SYSNAME..RMMPDOY
 //dispdd OUTPUT DEST=SYSTEMX,FORMS=LABEL,CLASS=L

The sample JCL in Figure 2 shows the use of additional parameters for specifying the MASTER DD statement, the JOURNAL DD statement, the PARMLIB DD statement, and the IEFRDER DD statement.

Figure 2. Creating a procedure in SYS1.PROCLIB using additional parameters

  //DFRMM PROC M=00,OPT=MAIN
  //IEFPROC EXEC PGM=EDG&OPT.,PARM='&M',TIME=1440,REGION=40M
  //PARMLIB DD   DDNAME=IEFRDER
  //IEFRDER DD   DISP=SHR,DSN=SYS1.PARMLIB
  //MASTER  DD   DISP=SHR,DSN=RMM.CONTROL.DSET
  //JOURNAL DD   DISP=SHR,DSN=RMM.JOURNAL.DSET
  //EDGPDOX DD   DISP=SHR,DSN=?UID..?HOSTID..RMMPDOX
  //EDGPDOY DD   DISP=SHR,DSN=?UID..?HOSTID..RMMPDOY
  //dispdd OUTPUT DEST=SYSTEMX,FORMS=LABEL,CLASS=L

where:

DFRMM

Specifies the procedure name. You can use any procedure name, one-to-eight characters long, subject to the restriction documented under IEFSSNxx parmlib member.

dispdd

dispdd is an OUTPUT JCL statement that you code when you want to create label output data. The name of the output statement must match the name you specified in the DFSMSrmm EDGRMMxx parmlib OPTION DISPDDNAME operand as described in Defining system options: OPTION. You can use any JCL keywords supported on the OUTPUT statement as described in z/OS MVS JCL Reference.

EDGPDOX DD and EDGPDOY DD

EDGPDOX DD and EDGPDOY DD are required statements for external trace output recording. If you do not specify these DD statements, no logging of the PDA trace output is performed. When DFSMSrmm swaps the PDA log data sets EDGPDOX and EDGPDOY, DFSMSrmm uses an intermediate data set name for the log data sets. The started task must have ALTER access to this intermediate data set. The data set name is ?UID.RMMPDO.TEMP.RMMPDO.H?SYSID. The ?UID is the DFSMSrmm ID, and ?SYSID is the first seven characters of the DFSMSrmm SYSID that is defined in the DFSMSrmm EDGRMMxx parmlib OPTION SYSID operand, as described in Using the parmlib member EDGRMMxx.

IEFRDER DD

IEFRDER is an optional statement. Use the IEFRDER DD statement to enable operators to specify PARMLIB DD keywords on the START command for the DFRMM procedure. If you do not code the IEFRDER DD and code the PARMLIB DD, you will not be able to specify a different PARMLIB data set name when starting the DFRMM procedure. If you do not code SYS1.PARMLIB, it is not necessary to code the IEFRDER DD statement.

JOURNAL DD

JOURNAL is an optional statement. If you code the JOURNAL DD statement to name the DFSMSrmm journal data set, you cannot easily change the journal name by switching to a different PARMLIB member. You must supply the journal data set name in the DFSMSrmm EDGRMMxx parmlib member if you do not code the JOURNAL DD statement and if you require journaling. You must catalog the journal.

M

Use M on the PROC statement to specify a parmlib member suffix. When you specify M=00, DFSMSrmm uses member EDGRMM00.

MASTER DD

MASTER is an optional statement that identifies the DFSMSrmm control data set name. If you code the MASTER DD statement to name the DFSMSrmm control data set, you cannot easily change the control data set name by switching to a different parmlib member. You must supply the control data set name in the DFSMSrmm EDGRMMxx parmlib member if you do not code the MASTER DD statement.

OPT

Use OPT on the PROC statement to specify whether to enable or disable subsystem interface:

OPT=RESET to disable the subsystem interface
OPT=MAIN to enable the DFSMSrmm subsystem

PARMLIB DD

PARMLIB is an optional statement. Use the PARMLIB DD statement to identify the data set that contains DFSMSrmm startup parameters when you do not use the system PARMLIB concatenation. If you do not code the PARMLIB DD statement, do not code the IEFRDER DD statement because it is not required. See Step 19: Starting DFSMSrmm for parameters you can specify with the START command if you specify the PARMLIB DD statement.

If you specify the parmlib data set in the DFSMSrmm procedure, the data set remains allocated while DFSMSrmm is active. If you do not specify the parmlib data set name, DFSMSrmm dynamically allocates PARMLIB by using the concatenated parmlib function of the z/OS system.

Recommendation: Do not specify the PARMLIB or IEFRDER DD statement in the DFRMM procedure. Let DFSMSrmm dynamically allocate the PARMLIB to 'SYS1.PARMLIB' or use the concatenated parmlib support.

REGION

As you determine the REGION size for the DFSMSrmm started procedure, the amount of virtual storage that DFSMSrmm uses depends on the resources you have defined. DFSMSrmm virtual storage usage can be affected by any REGION size controls or restrictions that your systems might have in place such as in IEFUSI. The sample DFRMM procedure specifies REGION=40M, which normally provides all the private region below 16MB and 40MB above 16MB. To enable DFSMSrmm to use all available virtual storage, specify REGION=0M. If you want to set a specific region size, consider these tips along with the current region size of your DFRMM started procedure, to determine if you need to make any changes to the REGION size:

The VSAM local shared resources (LSR) buffer pool that is built by the DFSMSrmm subsystem for the control data set is obtained above 16 MB.
DFSMSrmm builds an LSR buffer pool for the DFRMM started procedure, and also for the EDGUTIL utility batch address space, which has a predetermined size. The LSR buffer pool is 800*data CISZ + 200*index CISZ. Assuming 10 240 for the control data set data CISZ and 2 048 for the control data set index CISZ, the value is 800*10 240+200*2 048=8.4 MB. If you use larger CI sizes, more buffer space is required. For example, if you use a 26K data CISZ, a 21.2 MB buffer size is required.

Recommendation: If the buffer space is larger than 8.6 MB, add the difference to the 40 MB region size that is used by DFSMSrmm and use this value as the REGION size for the DFRMM started procedure.
DFSMSrmm uses DFSORT during inventory management. Increase the DFSMSrmm REGION size to allow DFSORT to use storage rather than SORTWKxx DASD files. The use of storage rather than DASD files can potentially decrease the time that is needed to run DFSMSrmm inventory management. If you change the REGION size, use 1 additional MB for every 2 000 data sets on private volumes.

If you code the MASTER DD statement and the JOURNAL DD statement in the started procedure, you can switch to different data set names by specifying the names in the EDGRMMxx parmlib member. To make the switch:

Quiesce DFSMSrmm by specifying:
```
 F DFRMM,QUIESCE
```
DFSMSrmm frees the current file allocations and pauses the DFSMSrmm processing.
Specify the new parmlib member name that contains the data set names.
Start DFSMSrmm by specifying:
```
 F DFRMM,M=xx
```

If you decide to use EDGLABEL or EDGXPROC, you must update the procedure library to include them as well. See Using the LABEL procedure for information on the supplied EDGLABEL procedure. See Replenishing scratch volumes in a system-managed library for information on the supplied EDGXPROC procedure.