Explanation
Space management was attempted for a data set, but was unsuccessful. The data set name and reason codes are given in message ARC1001I or ARC0734I.
The values for reascode are:
- Reascode
- Meaning
- 4
- The data set VTOC entry for a non-VSAM data set indicates that it is possibly multivolume but the catalog entry indicates it is a single volume.
- 5
- The catalog entry is a generation data group (GDG) entry name.
- 6
- There was an error in a catalog entry for a data set.
- 7
- An error occurred trying to convert the symbolic volser to a real volser.
- 8
- No catalog entry was found.
- 9
- Unsupported data set for migration. The catalog entry shows the data set as a non-SMS-managed VSAM data set defined with key ranges.
- 10
- The catalog entry indicates that the data set is multiple volume. If the data set is a VSAM data set, it is not an SMS-managed data set, and one component is multiple volume.
- 11
- Unsupported data set for migration. 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 might be a VSAM page space, or a locate error occurred for the data set name.
- 15
- A component of the VSAM data set has a logical record length that is too large for DFSMShsm. The maximum allowable 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 in the VSAM base cluster.
- 19
- A LOCATE error occurred for a path component in the VSAM base cluster.
- 20
- The data set name is a VSAM component name instead of a cluster name.
- 28
- A LOCATE error occurred for the VSAM alternate index (AIX) cluster.
- 38
- A LOCATE error occurred for the data or index component in a VSAM AIX cluster.
- 39
- A LOCATE error occurred for a path component in the VSAM AIX cluster.
- 40
- A least one component of the VSAM data set is empty. The VSAM data component had no data for IDCAMS to move.
- 48
- A LOCATE error occurred for the data set or its alias.
- 52
- Two or more directory entries for a partitioned data set had the same TTR.
- 53
- A directory entry in a partitioned data set has an invalid length value.
- 54
- An imbedded record has a zero or negative length. The member name is reported in the associated ARC0901I message with module ARCMPDS.
- 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.
- 57
- A generated name was not found in MCDMCANM for a data set not in an SDSP and migrated by DFSMShsm R 1.3 or later. Space management is not performed on this data set.
- 58
- The authorized program facility (APF) is not available to DFSMShsm to determine if the data set being processed is in the APF list.
- 60
- An SMS definition conflict is detected. DFSMShsm indicates an SMS-managed data set. The APF QUERY function indicates a non-SMS-managed data set.
- 62
- An error occurred while invoking APF for determining if a data set is in the APF list.
- 64
- The system list of APF libraries is not available.
- 66
- The data set is greater than 2 Terabytes in size. This exceeds the architectural limit for systems prior to z/OS® V1R13.
67
- The data set being migrated 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 migration in pre-V2R1 systems.
- 89
- The data set being migrated is a VSAM keyrange data set. This data set type is not supported for migration if DFSMShsm (IDCAMS) is the specified datamover.
System action
The data set is not space managed. DFSMShsm processing continues.
Programmer response
If a LOCATE error occurred,
update the catalog entry, and retry the command. If reascode is
40, load data in all the components. If reascode is 57, contact your
storage administrator or the IBM® Support
Center for help. If reascode is 66, use DFSMShsm V1R13
to migrate this data set. If the reascode code
is 67, use DFSMShsm V2R1 or higher to migrate this data set. If reascode is
89, DFSMSdss needs
to be the datamover. In order to use DFSMSdss as the datamover, do not use the
"PATCH .DMVST.+0" command.
Source
DFSMShsm