When volumes move to the wrong storage location

Use Table 1 to determine why DFSMSrmm applied a vital record specification to a data set.

Table 1. How DFSMSrmm matches data set names to data set masks
Order (OLD) (NEW)	Description	Command Example
1 1	A reserved name, ABEND, DELETED, or OPEN, matches a data set before any other data set mask.	`RMM ADDVRS DSNAME('ABEND') - LASTREFERENCEDAYS COUNT(1) RMM ADDVRS DSNAME('OPEN') - LASTREFERENCEDAYS COUNT(2)`
2 7	A management class name matches the management class value after ABEND, DELETED, or OPEN and before any other data set mask. The management class value is set using the RMM EDGUX100 installation exit and matches management calls names set using ACS routines.	`RMM ADDVRS DSNAME('M99000') WHILECATALOG`
3 2	A fully qualified data set name matches a data set name before any mask containing %, ¬, or *.	`RMM ADDVRS DSNAME('PRITCHAR.BACKUP.DATA')`
4 3	Any data set name mask that includes a % or a ¬ matches a data set name before masks containing an *. % and ¬ are treated equally.	`RMM ADDVRS DSNAME('PRITCHAR.%.DATA') RMM ADDVRS DSNAME('PRITCHAR.¬.DATA')`
5 4	Any data set name mask that includes single *'s preceded or followed by any character is the next best match.	`RMM ADDVRS DSNAME('PRITCHAR.*BACK.DATA')`
6 5	Any data set name mask that includes an * is the next best match.	`RMM ADDVRS DSNAME('PRITCHAR.*.DATA')`
7 6	A data set name mask that includes ** anywhere in the mask is the next best match. When matching the data set mask to the data set name, the mask where the non-generic characters occur earlier in the mask is most specific.	`RMM ADDVRS DSNAME('PRITCHAR.')` `RMM ADDVRS DSNAME('.PRITCHAR')` `RMM ADDVRS DSNAME('.*')`
8 8	A vital record specification management value set by using the DFSMSrmm EDGUX100 exit.	`RMM ADDVRS DSNAME('D99000') WHILECATALOG`
9 9	A data set name mask of ** indicates the policy applies to all data sets not managed by any other vital record specification.	`RMM ADDVRS DSNAME('**')`

If volumes are moving to the wrong storage location, check the vital record specifications that you have defined. For example, if you expected volumes to move to the LOCAL storage location, but DFSMSrmm moves them to the REMOTE storage location, check these conditions:

A vital record specification was defined with the wrong location. For example, LOCATION(LOCAL) is specified with the RMM ADDVRS subcommand instead of LOCATION(REMOTE).
More than one vital record specification was defined for a volume or a data set. Use the EDGHSKP VRSEL report in the REPORT file, the DFSMSrmm ISPF dialog, or the RMM LISTDATASET subcommand to identify the vital record specification that is retaining a data set.
Possible solutions include:
- Deleting a matching vital record specification so a less specific vital record specification is used
- Changing LOCDEF priority so that one vital record specification is dominant and is used before others

To resolve any movement conflicts that arise when a volume matches more than one vital record specification, DFSMSrmm uses the location priority value. Priority values are purely relative and do not have any further significance. If there are two or more vital record specifications with conflicting move requirements that apply to a volume, DFSMSrmm uses the location priority to resolve any conflict. 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 of the LOCDEF command to define the relative importance of locations.

You can define the PRIORITY operand on RMM ADDVRS subcommand 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 2.

Table 2. 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

Use the RMM LISTVRS subcommand to list the details for vital record specifications that need to be changed. If volumes have already moved to incorrect locations, delete the existing vital record specification and add a vital record specification that contains the correct location information.

Related Reading: For information on using the RMM DELETEVRS TSO subcommand and the RMM ADDVRS TSO subcommand to make the changes, see z/OS DFSMSrmm Managing and Using Removable Media.