Moving volumes

During inventory management, DFSMSrmm identifies the destination for a volume. DFSMSrmm uses the location priority value to resolve movement conflicts when a volume is destined for more than one location. Priority values as shown in Table 1 are purely relative and do not have any further significance. If more than one destination is identified, and the locations are not the same, the DFSMSrmm default priorities are based on these conditions:

If none of the locations are storage locations, DFSMSrmm selects the most automated location that is based on the location priority.

If one or more storage locations is specified for a single volume, DFSMSrmm stores the volume in the location based on the DFSMSrmm default location priority, the priority set in the LOCDEF command for the location, or the priority specified in a vital record specification. The lower priority numbers take precedence. For example, a volume would move to a location with a priority value 100 before moving to a location with a priority value of 200. You can set a priority value with the PRIORITY operand on the LOCDEF parmlib command to define the relative importance of locations.

You can define PRIORITY on RMM ADDVRS subcommands to override default or assigned priorities at the data set level. When you do not set a priority value, DFSMSrmm uses the priority shown in Table 1.

Table 1. DFSMSrmm movement priority default values
Priority Number	Location Name or Location Type
100	REMOTE DFSMSrmm built-in storage location name
200	DISTANT DFSMSrmm built-in storage location name
300	LOCAL DFSMSrmm built-in storage location
2000	Installation defined storage locations
4800	AUTO automated tape libraries
4900	MANUAL manual tape libraries
5000	SHELF location name

For stacked volumes, DFSMSrmm determines the required location using the required location of each of the volumes in the same container that is retained by a vital record specification. Conflicts in locations are resolved using movement priority.

Volumes requiring movement are identified for storage location management processing. Storage location management processing sets the destination for the volume and allocates shelf locations, based on the destination specified in the vital record specification. See How storage location management processing works for more information.

You can identify locations that are not applicable for automated movement by using the LOCDEF operand AUTOMOVE(NO) in the EDGRMMxx parmlib member. When the volume’s current location is defined with AUTOMOVE(NO), DSTORE processing will not change the destination from the required location.

You can request that DFSMSrmm retain a volume in its existing location instead of specifying a storage location or the home location. You define the location in a vital record specification by using the CURRENT reserved location name. When you run vital record processing, DFSMSrmm keeps the volume in the current location rather than scheduling the volume for a move.