Explanation
A space management operation was requested for
an SMS-managed data set. The data set name was either given in the
preceding ARC1001I message or in the associated ARC0734I message,
along with the
reascode. The reason codes have
the following meanings:
- Reascode
- Meaning
- 1
- The data set is unmatched. VTOC catalog entry access services
indicated the data set being processed does not have all the related
data. A data set VTOC entry was not found for the data set. Refer
to z/OS DFSMS Using Data Sets for
more information.
- 2
- The data set is unmatched. VTOC catalog entry access services
indicated the data set being processed does not have all the related
data. A VVR entry was not found for the data set. Refer to z/OS DFSMS Using Data Sets for
more information.
- 3
- The data set is unmatched. VTOC catalog entry access services
indicated the data set being processed does not have all the related
data. A duplicate VVR entry was found for the data set. Refer to z/OS DFSMS Using Data Sets for
more information.
- 4
- SMS is either not active or not installed.
- 5
- An error occurred while obtaining the management class definition
for the data set.
- 6
- An error occurred while updating the catalog entry for the data
set.
- 7
- DFSMShsm detected
a discrepancy between the data set VTOC entry and the catalog information
for the data set being processed. The discrepancy is one of the following:
- The catalog information indicated this is an SMS-managed data
set (data set is associated with a storage class), but the data set
VTOC entry indicated this is a non-SMS-managed data set.
- The catalog information indicated this is a non-SMS-managed data
set (data set is not associated with a storage class), but the data
set VTOC entry indicated this is an SMS-managed data set.
- 8
- An error occurred while attempting to release unused space for
a data set (DADSM PARTREL function). DFSMShsm was processing a data set associated
with a management class that specified the attribute PARTIAL-RELEASE=YES.
- 9
- An error occurred while locating the ‘minus nth’
GDG when checking the management class attribute #-GDG-ELEMENTS-ON-PRIMARY.
- 10
- An error occurred while deleting an SMS-managed data set.
- 11
- There is no storage class definition in the extract list entry
returned by VTOC catalog entry access services. The data set resides
on an SMS-managed volume and requires a storage class definition to
be processed.
- 12
- An SMS-managed migrated data set was not migrated during level
1 migration. The data set is associated with a management class that
specified the attribute LEVEL-1-DAYS-NON-USAGE=NOLIMIT.
- 13
- The data set is unmatched. The data set being processed is uncataloged
or cataloged to a different volume. VTOC catalog entry access services
indicated the data set has a catalog entry for the volume being processed.
Refer to z/OS DFSMS Using Data Sets for
more information.
- 14
- A failure occurred retrieving catalog information. See the associated
ARC0950I message for the return code and reason code from Superlocate.
- 16
- DFSMShsm detected
a discrepancy between the data set VTOC entry and the catalog information
for the data set being processed. The catalog information indicated
that the data set resides on a single volume, but the data set VTOC
entry indicated the data set resides on multiple volumes.
- 60
- Expiration of a VSAM data set failed, because the data set is
in incomplete status. Issue a RECALL command for the data set.
System action
The migration of the data set ends. DFSMShsm processing
continues.
Programmer response
Perform the action assigned to the
reascode you
received.
- Reascode
- Meaning
- 1, 2, 3
- Run the IDCAMS DIAGNOSE against the catalog and or VVDS for the
unmatched data set. Take corrective action for any problems detected.
- 4
- If SMS is not installed on your system, it must be installed before DFSMShsm can
process any SMS-managed data sets or volumes; if installed, SMS needs
to be activated.
- 5
- Refer to message ARC0935I in the command activity log for the
specific failure. List the catalog information for the data set to
determine the management class name. Define the management class if
it does not exist. If the management class exists, contact the IBM® Support Center.
- 6
- Refer to message ARC0950I in the command activity log for the
specific failure.
- 7
- Correct the discrepancy, and reissue the request.
- 8
- Check for message ARC0938I in the command activity log for the
specific PARTREL failure.
If there is no ARC0938I message, the
exclusive ENQ for the data set failed and the PARTREL was not performed.
In this case, no action is required.
- 9
- Update the catalog entry.
- 10
- Refer to message ARC0528I or ARC0545I in the command activity
log for the specific failure.
- 11, 13, 14
- Correct the discrepancy, and reissue the request.
- 16
- The data set was open and in the process of extending to another
volume when Primary Space Management detected the discrepancy. The
discrepancy should end when the process completes.