| Nonintegrated catalog facility catalogs |
NO |
NO |
YES |
YES |
| Data sets whose names are SYSCTLG |
NO |
NO |
YES |
YES |
| Integrated catalog facility catalog |
NO |
YES |
YES |
YES |
| Uncataloged data sets |
NO |
NO |
YES |
YES |
| 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 |
YES |
YES |
NO |
NO |
| Partitioned data sets (PO) with non-zero
block size |
YES |
YES |
YES |
YES |
| Non-VSAM (non-SMS-managed) data sets
on multiple volumes |
YES |
YES |
NO |
NO |
| Non-VSAM (SMS-managed) data sets
on multiple volumes |
YES |
YES |
YES |
YES |
| Non-VSAM data sets on multiple volumes
that are RACF® indicated |
YES |
YES |
NO |
NO |
| Direct access (BDAM) data sets on
multiple volumes |
1 |
1 |
NO |
NO |
| 1
These data sets are not fully supported. They can be restored to
multiple volumes only as non-SMS-managed. They can be restored to
a single SMS volume by using the DFSMSdss patch described in z/OS DFSMSdfp Storage Administration. |
| Split-cylinder data sets |
YES |
YES |
NO |
NO |
| User-labeled data sets that are empty |
YES |
YES |
NO |
NO |
| User-labeled data sets that are not
sequential |
YES |
YES |
NO |
NO |
| User-labeled data sets that are sequential
and not empty |
YES |
YES |
YES |
YES |
| Unmovable data sets with one extent |
YES |
YES |
YES |
YES |
| Unmovable data sets with more than
one extent |
YES |
YES |
NO |
NO |
| Absolute track data sets (ABSTR) |
YES |
YES |
YES |
YES |
| Any data set allocated to another
user with a disposition of OLD |
YES |
YES |
YES 2 |
NO |
| 2 These
data sets can be backed up if allowed by the SETSYS BACKUP(INUSE(...))
subparameters or the installation exit ARCBDEXT, or both. |
| List and utility data sets (but not
SMS-managed) |
YES |
YES |
NO |
NO |
| List and utility data sets (SMS-managed) |
YES |
YES |
YES |
YES |
| Data sets whose names begin with
HSM or SYS1 (except SYS1.VVDS) |
YES |
YES |
YES |
YES |
| Data sets with no extents |
YES |
YES |
YES |
YES |
| Data sets cataloged with an esoteric
unit name (for example, D3390 on DASD) |
YES |
YES |
YES |
YES |
| Authorized program facility (APF)
authorized library |
YES |
YES |
YES |
YES |
| 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) |
YES |
YES |
YES |
YES |
| Fully qualified generation data sets
(for example, X.Y.G0001V00) |
YES |
YES |
YES |
YES |
| Relative generation data sets with
zero or negative generation numbers (for example, X.Y(-1)) |
YES |
YES |
NO |
NO |
| Generation data group names |
NO |
NO |
NO |
NO |
| ALIAS names |
NO |
NO |
NO |
YES 3 |
| 3
You can use ALIASes with the HBACKDS and HRECOVER commands. But when
a NONVSAM data set with ALIASes is backed up, DFSMShsm does not save
the ALIASes, so by using the HBACKDS and HRECOVER commands, the ALIASes
are not rebuilt and are lost. |
| Partitioned data sets with more than
one NOTE list or with more than three user TTRs per member |
YES |
YES |
NO |
NO |
| Extended partition data sets and
APF libraries |
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 data sets cataloged
in ICF catalogs without special or unusual characteristics (multivolume,
user labels, and so on) |
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 |
YES |
YES |
NO |
NO |
| VSAM (SMS-managed) data sets whose
components reside on more than one volume |
YES |
YES |
YES |
YES |
| VSAM (non-SMS-managed) data sets
defined with key ranges |
YES |
YES |
NO |
NO |
| VSAM (SMS-managed) data sets defined
with key ranges |
YES |
YES |
YES |
YES |
| VSAM data sets with the page-space
attributes |
NO |
YES |
NO |
NO |
| VSAM open data sets |
YES |
YES |
YES 2 |
YES 4 |
| 4
These data sets can be backed up using inline backup (ARCINBAK). |
| VSAM backup-while-open candidates |
YES |
YES |
YES |
YES |
| VSAM RLS-accessed data sets |
YES |
YES |
YES |
YES |
| VSAM data sets with the erase-on-scratch
bit set in the catalog |
YES |
YES |
YES |
YES |
| 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 |
YES |
YES |
YES |
YES |
| VSAM data sets with more than one
path name associated with the AIX |
YES |
YES |
YES |
YES |
| VSAM data sets whose base cluster
has more than one path name |
YES |
YES |
YES |
YES |
| VSAM (SMS-managed) data sets with
an empty data or index component |
NO |
YES |
YES |
YES |
Note: When a SMS VSAM cluster is backed up, its entire sphere
is backed up; that is, all components and all associations including
AIXs.
|
| 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 |
| Tape data sets in the INCLUDE list
and data sets in the ALLOCATE list that have a BLKSIZE greater than
32␠760 bytes |
YES |
NO |
Not Applicable |
Not Applicable |
| Tape data sets in the INCLUDE list
and data sets in the ALLOCATE list that have an LRECL greater than
32␠760 bytes |
NO |
NO |
Not Applicable |
Not Applicable |
| Tape data sets created by the DFSMSdss
COPYDUMP function using the DFSMSdss defaults for the DCB information
(LRECL = 0) |
NO |
NO |
Not Applicable |
Not Applicable |
| Data sets in the Allocate list that
have a BLKSIZE greater than 32 760 bytes |
NO |
NO |
Not Applicable |
Not Applicable |
| Tape data sets in the INCLUDE list
that have a BLKSIZE less than 524 288 bytes |
YES |
YES |
Not Applicable |
Not Applicable |
| Mounted zFS data sets |
YES |
NO |
YES |
YES |
| Unmounted zFS data sets |
YES |
NO |
YES |
YES |
z/OS DFSMShsm Implementation and Customization Guide
Copyright IBM Corporation 1990, 2014