Specifying data set names

When you specify a data set name with a DFSMShsm user command, the data set name must conform to TSO data set naming conventions. The qualified name consists of the following fields:

Your user prefix (required; defaults to user ID; can be redefined by using the TSO PROFILE command)
A user-supplied name (required)
A descriptive qualifier (optional)

The following example shows all three fields:

USER.PART.DATA

where:

USER is the user prefix
PART is the user-supplied name
DATA is the descriptive qualifier

You may specify a fully qualified name (a name with all three qualifiers) by enclosing it in apostrophes, for example:

'USER.PART.DATA'

The system does not append the user prefix and descriptive qualifiers to data set names that are enclosed in apostrophes. If you use a fully qualified name without enclosing it in apostrophes, the system appends the user prefix, for example:

USER.PART.DATA

becomes:

USER.USER.PART.DATA

For the HBACKDS, HDELETE, HMIGRATE, HRECALL, and HRECOVER commands, you can specify a partly qualified data set name using a filter, which can contain certain symbols (“wild cards”), interpreted as follows:

%: one and only one character in a qualifier
%%...: up to eight percent signs can be specified in each qualifier
*: one or more characters in one qualifier
**: zero or more qualifiers (the double asterisk cannot precede or follow any characters; it must be preceded and followed by either a period or a blank)

Given such a filter, DFSMShsm uses catalog services to locate all non-VSAM data sets, generation data sets, and VSAM clusters with names that match the pattern specified in the filter. From these data sets, DFSMShsm performs the desired function on those that meet any other qualifications in the command, such as CHANGEDONLY for HBACKDS.

For example, if you specify HBACKDS ‘HLQ.MLQ.DATA%’, DFSMShsm will back up data set HLQ.MLQ.DATA1 but not VSAM cluster HLQ.MLQ.DATA25.

If you specify HDELETE HLQ.MLQ.*.DATA, DFSMShsm will delete migrated data sets USERID.HLQ.MLQ.A.DATA and USERID.HLQ.MLQ.XYZ.DATA, but not USERID.HLQ.MLQ.ABC.

If you specify HRECALL ‘HLQ.MLQ.**’, DFSMShsm will recall migrated data sets HLQ.MLQ.DATA4 and HLQ.MLQ.Z.LIST, but not USERID.HLQ.MLQ.DATA.

If you specify HMIGRATE **.DATA, DFSMShsm will migrate data sets USERID.HLQ.DATA and USERID.DATA, but not USERID.HLQ.LIST.

Note:

If you specify a list of data sets in the command, any of the data set names in the list can be filters.
Any fully qualified data set name in the list can be an alias for a true data set name. However, the HRECOVER command fails if a user substitutes an alias for the data set name of an ICF catalog, even if the user is DFSMShsm-authorized.
If a filter within apostrophes has a wild card as the first character, DFSMShsm asks to search all the user catalogs in the system. This search has a negative effect on system performance.