Create the control data set control record the first time you run EDGUTIL. This normally occurs during DFSMSrmm implementation or conversion to DFSMSrmm. The control data set control record contains information about the number of shelf locations in the library and storage locations. To create or update the control record, the user of EDGUTIL must have UPDATE or higher RACF access to the DFSMSrmm control data set.

Once you have created a control record, defined shelf locations to your installation, and have begun managing these shelves with DFSMSrmm, use the RMM ADDRACK subcommand to add shelf locations to DFSMSrmm. Do not use EDGUTIL to change the number of shelf locations.

You should only need to update the control record to correct rack or bin counts. DFSMSrmm lets you update the control data set and the control record only if inventory management and backup, restore and reorganize are not in progress.

As part of CREATE processing or UPDATE processing, EDGUTIL ensures that DFSMSrmm is not active and opens the control data set for load processing. The information provided on the CONTROL command in SYSIN is used to build a control record, which is written to the control data set.

The SYSIN commands in Figure 1 is required to create or update the control data set control record.

>>-CONTROL--+---------------------+--CDSID(id)------------------>
            '-CATSYNCH(-+-NO--+-)-'              
                        '-YES-'                  

>--+------------------+--+-----------------+-------------------->
   '-EXTENDEDBIN(YES)-'  '-DBINFREE(count)-'   

>--+---------------+--+-----------------+--+---------------+---->
   '-DBINNO(count)-'  '-LBINFREE(count)-'  '-LBINNO(count)-'   

>--+-----------------+--+---------------+----------------------->
   '-RACKFREE(count)-'  '-RACKNO(count)-'   

>--+-----------------+--+---------------+----------------------->
   '-RBINFREE(count)-'  '-RBINNO(count)-'   

>--+--------------------+--+----------+------------------------><
   '-STACKEDVOLUME(YES)-'  '-UTC(YES)-'   

CATSYNCH(NO|YES)

Specifies whether or not the DFSMSrmm control data set and system catalogs are synchronized or not. When the DFSMSrmm control data set is not synchronized with the system catalogs, DFSMSrmm always retrieves catalog information to determine the catalog status of a data set.

When you indicate that catalogs are fully shared with the EDGRMMxx parmlib OPTION CATSYSID(*) as described in Defining system options: OPTION, DFSMSrmm automatically marks the DFSMSrmm control data set as synchronized when you run the EDGHSKP utility with the CATSYNCH parameter as described in EXEC parameters for EDGHSKP. You must use CATSYNCH(YES) to indicate to DFSMSrmm that catalogs are synchronized when you use DFSMSrmm with unshared catalogs. Do not specify CATSYNCH(YES) if you have not run the EDGHSKP utility with the CATSYNCH parameter on each system to synchronize the DFSMSrmm control data set with the user catalogs.

CATSYNCH(YES) sets the last synchronization date and time to the current date and time. CATSYNCH(NO) clears the last synchronization date and time. Specify CATSYNCH(NO) to force synchronization of the DFSMSrmm control data set and user catalogs the next time inventory management is run. DFSMSrmm cannot track catalog updates when the DFSMSrmm subsystem is stopped and issues messages when the updates cannot be made.

CDSID(id)

Specifies one-to-eight characters that identify the control data set by name. There is no default.

At DFSMSrmm startup time, DFSMSrmm matches this CDSID value with the CDSID operand in parmlib member EDGRMMxx. The CDSID value in EDGUTIL will set or change the control data set ID. EDGUTIL does not validate the CDSID in the control data set control record; it simply sets the new value into the control record. When you change the CDSID, any running systems that shares the control data set detects the change in CDSID and changes the ENQ name they use for serialization. Ensure that the GRSRNLxx parmlib member is updated to reflect any CDSID changes you make. See Step 5: Updating SYS1.PARMLIB members.

You must always set a CDSID using the EDGUTIL utility. The CDSID ensures that only the correct DFSMSrmm systems start up and use the control data set that you created for them.

This operand is required.

CONTROL

Specifies to update or create the control record.

DBINFREE(nnnnnn)

Specifies the number of empty bin numbers in the DISTANT storage location in a range from 0 to 999999.

DBINNO(nnnnnn)

Specifies the number of bin numbers in the DISTANT storage location in a range from 0 to 999999.

EXTENDEDBIN(YES)

Enables DFSMSrmm extended bin support, which allows the reuse of bins at the start of a move.

When extended bin support is enabled, DFSMSrmm records additional information in the volume and bin record while a volume is moving from or to a bin-managed storage location.

Do not enable extended bin support until you have made sure that the same level of code has been installed for all the DFSMSrmm systems that share a control data set.

Once it is enabled, extended bin support cannot be disabled.

Extended bin support must be enabled, if you want to use DFSMSrmm parmlib OPTION command REUSEBIN(STARTMOVE) operand to reuse bins when a volume moves from a bin.

LBINFREE(nnnnnn)

Specifies the number of empty bin numbers in the LOCAL storage location in a range from 0 to 999999.

LBINNO(nnnnnn)

Specifies the number of bin numbers in the LOCAL storage location in a range from 0 to 999999.

RACKFREE(nnnnnn)

Specifies the number of empty rack numbers in the library for location SHELF and for system-managed libraries in a range from 0 to 2147483647.

RACKNO(nnnnnn)

Specifies the number of rack numbers in the library for location SHELF and for system-managed libraries in a range from 0 to 2147483647.

RBINFREE(nnnnnn)

Specifies the number of empty bin numbers in the REMOTE storage location in a range from 0 to 999999.

RBINNO(nnnnnn)

Specifies the number of bin numbers in the REMOTE storage location in a range from 0 to 999999.

STACKEDVOLUME(YES)

Enables DFSMSrmm stacked volume support.

When stacked volumes have been defined to DFSMSrmm but you have not enabled stacked volume support, DFSMSrmm manages the movement of the volumes that are in containers using the individual volume location. Volume movement is limited to non-shelf-managed storage locations. When you enable stacked volume support, DFSMSrmm uses the stacked volume records to manage the movement of the volumes contained in the stacked volumes. See Setting up DFSMSrmm stacked volume support.

You cannot remove stacked volume support after it is enabled.

UTC(YES)

Enables DFSMSrmm common time support. Prior to enabling this support, ensure all systems in the RMMplex have toleration maintenance installed or are at the current z/OS release, and all applications dependent on the correct date and time information from DFSMSrmm are updated to support the new time zone support, if required.

You must only enable common time support if the time of day clocks of all systems in the RMMplex are set to GMT.

Once you enable common time support, DFSMSrmm starts to record the control data set record dates and times in common time and converts existing values, as required, from local times to common time. See Setting up DFSMSrmm common time support for more information.

You cannot disable common time support after it is enabled.