Explanation
A backup command was issued for an SMS-managed
data set. The data set name is given in the preceding ARC1001I or
ARC0734I message, along with the
reason-code. The
reason code has the following meanings:
- 1
- The data set is unmatched: The catalog indicates that the data
set processing does not have all related data. A data set VTOC entry
is not found for the data set.
- 2
- The data set is unmatched: The catalog indicates that the data
set processing does not have all related data. A VVR entry is not
found for the data set. This condition could be the result of a recall
being in process at the same time that backup is processing the volume.
- 3
- The data set is unmatched: The catalog indicates that the data
set processing does not have all related data. A duplicate VVR entry
is found for the data set.
- 4
- DFSMS is
not active or is not installed.
- 5
- Error obtaining the management class definition for the data set.
- 7
- DFSMShsm detected
a discrepancy between the data set VTOC entry and the catalog information
associated with the data set processing. The discrepancy is one of
the following:
- The catalog information indicates that this is an SMS-managed
data set (data set is associated with a storage class), but the data
set VTOC entry indicates this is a non-SMS-managed data set.
- The catalog information indicates that this is a non-SMS-managed
data set (data set is not associated with a storage class), but the
data set VTOC entry indicates this is an SMS-managed data set.
- 10
- Error deleting an SMS-managed data set.
- 11
- There is no storage class name in the extract list entry of catalog
information. The data set resides on an SMS-managed volume and requires
a storage class definition to be processed.
- 13
- The data set is unmatched. The data set processing is uncataloged
or cataloged to a different volume than the volume DFSMShsm processed on which
the data set is found. The data set is not indicated as being an uncataloged
data set, and hence DFSMShsm attempts to process a cataloged
data set.
DFSMShsm was
attempting to process the data set as cataloged and found it to be
unmatched for one of the following conditions:
- The data set is uncataloged.
- The data set was deleted by another job or user while backup was
processing the volume.
- The data set was found on the volume being backed up, but is cataloged
to a different volume.
System action
Backup command processing of the data set ends. DFSMShsm processing
continues.
Programmer response
- 1, 2, 3
- Run 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 the system, it must be installed before DFSMShsm can
process any SMS-managed data sets or volumes. If SMS is installed,
it needs to be activated.
- 5
- List the catalog information for the data set to determine the
management class name. See message ARC0935I in the command activity
log for the specific failure. Define the management class if it does
not exist. If the management class exists, contact the IBM® Support Center.
- 7
- Correct the discrepancy and reissue the request.
- 10
- See message ARC0528I or ARC0545I in the backup activity log or
to message ARC0937I or ARC0950I in the command activity log for the
specific failure.
- 11
- Correct the discrepancy and reissue the request.
- 13
- If the data set is uncataloged, recatalog the data set using the
IDCAMS DEFINE RECATALOG function.
If a catalog entry exists for
the same named data set, the data set which failed to be backed up
may have been erroneously uncataloged and a new data set with the
same name may have been created. If you wish to delete the uncataloged
data set in order to prevent DFSMShsm from producing this error for the
data set, use the IDCAMS DELETE NVR function.