z/OS DFSMShsm Implementation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Data set type support for space management functions

z/OS DFSMShsm Implementation and Customization Guide
SC23-6869-01

Table 1 provides information about supported data set types for space management functions.

Table 1. Space Management—Data Set Type Support
Data Set Type Volume Space Management DBA or DBU Volume Space Management Expire or Delete Volume Space Management Command Data Set Migration
Nonintegrated catalog facility catalogs NO NO NO NO
Data sets whose names are SYSCTLG NO NO NO NO
Integrated catalog facility catalog NO NO NO NO
Uncataloged data sets YES YES NO NO
Cataloged data sets that are not accessible through the standard catalog search (these appear to DFSMShsm as uncataloged data sets) NO NO NO NO
VSAM data sets cataloged in existing catalogs (those not in the integrated catalog facility catalog) NO NO NO NO
Partitioned data sets (PO) with zero block size NO NO NO NO
Partitioned data sets (PO) with non-zero block size YES YES YES YES
Partitioned data sets (SMS-managed) having an AX cell in the VTOC/VVDS NO NO YES YES
Non-VSAM (non-SMS-managed) data sets on multiple volumes NO NO NO NO
Non-VSAM (SMS-managed) data sets on multiple volumes NO NO YES YES
Non-VSAM (SMS-managed) data sets on multiple volumes that are RACF® indicated NO YES NO NO
Direct access (BDAM) data sets on multiple volumes NO NO NO NO
Split-cylinder data sets NO NO NO NO
User-labeled data sets that are empty YES YES NO NO
User-labeled data sets that are not sequential NO NO NO NO
User-labeled data sets that are sequential and not empty YES YES YES YES
Unmovable data sets with one extent NO NO NO NO
Unmovable data sets with more than one extent NO NO NO NO
Absolute track data sets (ABSTR) NO NO NO NO
Any data set allocated to another user with a disposition of OLD NO NO NO NO
List and utility data sets (but not SMS-managed) YES YES NO YES
List and utility data sets (SMS-managed) YES YES YES YES
Data sets whose names begin with HSM or SYS1 (except SYS1.VVDS) NO 1  NO 1  NO 1  NO 1 
 1 This restriction can be removed using the SETMIG LEVEL() command.
Data sets with no extents NO NO NO NO
Data sets cataloged with an esoteric unit name (for example, D3390 on DASD) NO NO NO NO
Authorized program facility (APF) authorized library NO NO NO NO
Password-protected generation data sets (use the information under the heading Generation data groups regarding password-protected generation data sets, and for a method of bypassing this restriction) NO NO NO NO
Fully qualified generation data group names YES YES YES YES
ALIAS names NO NO NO YES 2 
 2  An ALIAS can be used with the HMIGRATE, HRECALL, and HDELETE commands.
Partitioned data sets with more than one NOTE list or with more than three user TTRs per member NO NO NO NO
Extended partition data sets NO NO YES YES
Physical sequential data sets cataloged in ICF catalogs without special or unusual characteristics (multivolume, user labels, and so forth) YES YES YES YES
Physical sequential variable blocked data sets with a logical record length (LRECL) larger than block size (BLKSIZE) YES YES YES YES
Physical sequential large format data set YES YES YES YES
VSAM (non-SMS-managed) data sets whose components reside on more than one volume NO NO NO NO
VSAM (SMS-managed) data sets whose components reside on more than one volume NO NO YES YES
VSAM (non-SMS-managed) data sets defined with key ranges NO NO NO NO
VSAM (SMS-managed) data sets defined with key ranges NO NO YES YES
VSAM data sets with the page-space attributes NO NO NO NO
VSAM open data sets NO NO NO NO
VSAM data sets with the erase-on-scratch bit set in the catalog NO NO NO NO
VSAM data sets with the erase-on-scratch bit set in the RACF profile YES YES YES YES
VSAM data sets with 2 to 17 AIXs  3  NO NO NO YES
VSAM data sets with more than one path name associated with the AIX 3  NO NO NO YES
VSAM data sets whose base cluster has more than one path name 3  NO NO NO YES
 3  If VSAM data sets have more than one AIX, more than one path, or more than one path to the AIX are migrated, all components except the base cluster name are uncataloged. These data sets must be recalled by using the base cluster name.
VSAM data sets with more than 17 AIXs NO NO NO YES
VSAM (SMS-managed) data sets with an empty data or index component NO YES YES YES
VSAM (non-SMS-managed) data sets with an empty data or index component YES NO YES YES
VSAM data sets whose LRECLs are too long to be processed by EXPORT

For relative record data sets (RRDS), the maximum length is 32␠752 bytes.

For entry-sequenced data sets (ESDS) and key-sequenced data sets (KSDS), the maximum length is 32␠758 bytes.

YES YES YES YES
VSAM spheres marked as forward recovery required YES YES NO NO
VSAM spheres with retained locks NO NO NO NO
Mounted zFS data sets NO NO NO NO
Unmounted zFS data sets YES YES YES YES

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014