Explanation
A backup command was issued for a data set. The data set name and reason codes are given in message ARC1001I.
- 5
- An attempt was made to backup a GDG base entry. The data set is only an entry in the catalog and not a cataloged data set.
- 6
- There was an error in a catalog entry for a non-VSAM data set.
- 7
- An error occurred trying to convert the symbolic volser to a real volser.
- 8
- No catalog entry was found for a VSAM data set.
- 9
- Unsupported data set for backup. The catalog entry shows the VSAM data set to be a non-SMS-managed data set defined with key ranges.
- 10
- The catalog entry indicates that the data set is a multivolume data set. If the data set is VSAM, it is not an SMS-managed data set, and one component is multivolume.
- 11
- Unsupported data set for backup. The catalog entry shows at least one AIX® defined with key ranges and the base cluster is not defined with key ranges.
- 12
- The components of the non-SMS-managed VSAM cluster are on different volumes.
- 14
- The catalog entry is not a VSAM base cluster or a non-VSAM data set; the catalog entry is a VSAM page space, or a locate error occurred for the data set name.
- 14
- The catalog entry is not a VSAM base cluster and not a non-VSAM data set, or the catalog entry is a VSAM page space or swap space, or a locate error occurred for the data set name.
- 15
- A component of the VSAM data set has a logical record length too large for DFSMShsm. The maximum allowable logical record length is 32 752 bytes for a relative record data set and 32 756 bytes for entry-sequenced or key-sequenced data sets.
- 16
- A component of the VSAM data set is open for output.
- 18
- A LOCATE error occurred for the data or index component of the VSAM base cluster.
- 19
- Locate error on base path component.
- 20
- The data set name is a VSAM component name instead of a cluster name.
- 24
- The catalog entry indicates that the data set is a non-VSAM multivolume data set. The data set’s volser list also indicates multiple volumes.
- 28
- A LOCATE error occurred for a VSAM alternate index (AIX) cluster.
- 38
- A LOCATE error occurred for the data or index component of the VSAM AIX cluster.
- 39
- Locate error on AIX path component.
- 40
- At least one component of the VSAM data set is empty.
- 48
- A LOCATE error occurred for the data set.
- 52
- A GETMAIN error occurred during the process of getting the catalog information about a VSAM data set.
- 54
- Backup-While-Open data sets are not supported when bypass of the data set enqueue is requested through the ARCHBACK macro or the ARCBDEXT user exit. They are also not supported by the inline backup function.
- 56
- A VSAM data set has an invalid expiration date. The expiration date obtained from the catalog contains a year greater than 2155. This data set is not supported.
- 60
- Backup of a VSAM data set failed because the data set is in incomplete status. Issue a RECALL command for the data set.
- 62
- The return code passed back from the data set backup exit (ARCBDEXT) indicates that the data set should not be backed up.
- 64
- The ESTAE setup for the data set backup exit (ARCBDEXT) failed.
- 65
- The migration copy has a format-8 DSCB.
- 66
- Data set size exceeds 2 Terabytes. This exceeds the architectural limit for systems prior to V1R13.
67
- The data set being backed up is a non-SMS-managed VSAM linear
data set which has the Extended Addressable(EA) attribute specified.
This data set type is not supported for backup in pre-V2R1 systems.
- 405
- The VTOC entries for the data set indicate that there are more tracks allocated to a VSAM data set on the first volume than the total number of tracks allocated to the data set.
System action
The data set is not backed up. If the reason code is 48, no VSAM data sets are backed up from the volume. DFSMShsm processing continues.
Programmer response
If a locate error occurred, fix the catalog
entry and retry the command. If the reason code is 40, load data in
all the components. If the reason code is 405 examine the VTOC entries
for the data set on all volumes to ensure that they are correct. Backing
up a component of a VSAM cluster or an association such as an AIX results in a reason code 14. DFSMShsm backs
up the entire VSAM base cluster, which includes all the components
and associations. If the reason code is 62 and the
data set should be considered eligible for backup, the data set backup
exit (ARCBDEXT) must be updated so that it does not exclude the data
set from backup. If the reason code is 64, contact the IBM® Support Center. If the reason code is 66,
use DFSMShsm V1R13
or higher to backup this data set. If the
reason code is 67, use DFSMShsm V2R1 or higher to backup this data
set.
Source
DFSMShsm