LOCDEF command operands

Specifies the name of the location being defined. installation_defined_location_name can be any 1 to 8 character name or LOCAL, DISTANT, REMOTE, or SHELF. system_managed_library_name can be any 1 to 8 character name starting with a nonnumeric. The DFSMSrmm reserved location names HOME, CURRENT or ALL cannot be used as location names. When you use SHELF or a system-managed library, the only other operands that can be specified are PRIORITY and TYPE.

All LOCDEF location names must be unique. DFSMSrmm issues message EDG0225E if you define duplicate location names. You cannot have a storage location with the same name as a system-managed library. If you specify the same name, DFSMSrmm issues message EDG0233E. You can specify a distributed library name only if the library is an IBM Virtualization Engine. For other libraries, if you specify a distributed library name, DFSMSrmm issues message EDG0235E.

MANAGEMENTTYPE(BINS|NOBINS)

Use this operand to identify the shelf-management technique you want for the location. This operand is required when defining a location of type STORAGE.

BINS: DFSMSrmm shelf-manages the location by assigning bin numbers to volumes in the location.
NOBINS: Specifies that the location is not to be shelf-managed. Volumes sent to this location are not assigned bin numbers. However, they will still only be eligible to be sent to the location if their medianame or * appears in the LOCDEF media name list.

You can change the type of a location by specifying the LOCDEF command with the TYPE operand. During vital record processing, DFSMSrmm changes the required location and location type for each volume. See Changing storage locations for additional information.

Although inventory management vital record processing must be run to implement the new LOCDEF MANAGEMENTTYPE, you can use the new LOCDEF MANAGEMENTTYPE when issuing DFSMSrmm CHANGEVOLUME subcommands with the LOCATION operand.

MEDIANAME(medianame|*)

Specifies a list of the media names that are acceptable for the storage location. medianame can be any 1 to 8 character name you choose to describe a media name, type of media, a shape, or size. Examples of MEDIANAME include: CART, ROUND, SQUARE, 3490, 3590, TAPE, OPTICAL, CASSETTE, and so on. The media names you use on the LOCDEF commands should be the same as or a subset of the media names you use for your installation VLPOOL commands. See Defining pools: VLPOOL.

When you specify MEDIANAME(*) using the parmlib LOCDEF command or the RMM ADDBIN or RMM ADDRACK subcommands, any volume with any media name can be sent to the location and DFSMSrmm does not segregate the volumes by shape. For example, if you specified a LOCDEF command with the media names:

LOCDEF LOCATION(MYLOC) MEDIANAME(3480,*) MANAGEMENTTYPE(BINS)

then you could use these media names on RMM ADDBIN subcommand requests:

RMM ADDBIN KG0002 LOCATION(MYLOC) MEDIANAME(3480)

and

RMM ADDBIN KG0100 LOCATION(MYLOC) MEDIANAME(*)

The example shown in Figure 1 is not valid because the MEDIANAME(3420) was not listed on the LOCDEF parameters for the storage location.

Figure 1. Using a medianame not defined in the LOCDEF command

RMM ADDBIN KG0005 LOCATION(MYLOC) MEDIANAME(3420)

AUTOMOVE

Use this operand to identify libraries or storage locations that hold tape volumes that are not eligible for automated movement initiated by inventory management. During inventory management DSTORE processing the volume’s current location is validated against the matching LOCDEF. Consider this operand for libraries that contain virtual volumes or other volumes that either cannot be moved or for which you do not want DFSMSrmm to initiate the movement.

YES: DSTORE will initiate automated movement when the required location does not match the current location of the volume. This is the default.
NO: DSTORE will not initiate automated movement

PRIORITY(1-9999)

Defines the priority of this location relative to other locations. Lower numbers have higher priorities. PRIORITY is used to determine where to move a volume when a volume is assigned multiple destinations based on matching to two or more vital record specification definitions. PRIORITY is used to select a location in case of a move conflict. Move conflicts include:

Multiple data sets with different required locations on one volume.
Multiple volumes with different required locations in one volume set and the DFSMSrmm EDGRMMxx parmlib option is set for movement by volume set.
Multiple logical volumes with different required locations on one stacked volume.

You can override this value by specifying a PRIORITY on the vital record specification. If PRIORITY is omitted, priority is based on the location type:

Priority: Location Name or Type
2000: Installation defined STORAGE type, including LOCAL, DISTANT, and REMOTE if they are specified on LOCDEF.
4800: AUTO automated tape libraries
4900: MANUAL manual tape libraries
5000: SHELF location

For each location you do not specify in a LOCDEF, the default priority is determined from this list:

Priority: Location Name or Type
100: REMOTE location
200: DISTANT location
300: LOCAL location
2000: installation-defined STORAGE type
4800: AUTO automated tape libraries
4900: MANUAL manual tape libraries
5000: SHELF location

TYPE(STORAGE|LIBRARY)

Use this operand to identify the type of location you are defining. The value can be either STORAGE or LIBRARY. This operand is optional. If MEDIANAME or MANAGEMENTTYPE are specified, only TYPE(STORAGE) is valid. If you do not specify the TYPE operand DFSMSrmm sets a default value based on whether you specify the MEDIANAME or MANAGEMENTTYPE operands.

STORAGE,HOME

Specifies that the location is a storage location, either shelf-managed or non-shelf-managed. You can identify a storage location as a home location by specifying TYPE(STORAGE,HOME). When you identify a storage location as a home location, you can manage volumes in a storage location like volumes that reside in a LIBRARY location. You can:

Schedule release actions for volumes when they return to their storage home location
Return volumes to scratch status while they reside in their storage home location

You can use STORAGE,HOME to define location names for non-system-managed robot libraries in your installation and assign a storage location name to that library instead of using the default value of SHELF.

LIBRARY

Specifies that the location is either SHELF or a system-managed library. The only reason to define these locations on LOCDEF parameters is to change the default priority for the location. For a LIBRARY type location the only LOCDEF operands you can use are PRIORITY and LOCATION.

Although inventory management vital record processing must be run to implement the new LOCDEF TYPE value, you can use the new LOCDEF TYPE when issuing DFSMSrmm CHANGEVOLUME subcommands with the LOCATION operand.

Points on usage:

A LOCDEF parameter is required in the DFSMSrmm parmlib member for each installation defined storage location name and when you want to define a movement priority for the location.
If you have multiple systems sharing a control data set, use the same LOCDEF commands on all sharing systems. However, you only need to define storage locations to the systems where you will use any RMM ADDVRS, ADDBIN or CHANGEVOLUME subcommands, and where you plan to run inventory management. During storage location management processing, DFSMSrmm ensures that the storage locations used during vital record processing are defined by LOCDEF commands. If you specify a system-managed library name on a LOCDEF command, DFSMSrmm validates that it is a library defined on the current system. If your system-managed libraries are not defined on all systems, DFSMSrmm assumes a TYPE(LIBRARY) location is manual tape library if it is not defined as a system-managed library. During inventory management vital record selection processing, if no priority is obtained from a vital record specification, DFSMSrmm obtains the priority from the LOCDEF commands. If no LOCDEF command is specified and DFSMSrmm knows that the location is a system-managed library, DFSMSrmm uses the default priority for the location type. Otherwise DFSMSrmm uses a priority of 9999.
If a LOCDEF parameter is altered or removed, existing bin numbers that are now in a location that is not defined by LOCDEF, or which have a media name no longer listed under the LOCDEF MEDIANAME operand, are handled correctly. Bin numbers are freed up when a volume is moved from the storage location or can be removed using the RMM DELETEBIN subcommand. You cannot add more bin numbers nor assign the bin numbers to new volumes going to the location.
Changes to LOCDEF PRIORITY or MEDIANAME operands take effect during the first run of vital record processing after DFSMSrmm has been stopped and restarted, or the MODIFY command used to update the changed LOCDEF parameters in parmlib.
Changes to LOCDEF MANAGEMENTTYPE or TYPE operands take effect only after inventory management vital record processing has been run, or when using the LOCATION operand on the RMM ADDVOLUME or CHANGEVOLUME subcommands. See Changing storage locations for additional information.
See Managing storage locations for more information on LOCDEF and storage locations.