ARC1320I

Explanation
 A request sent to DFSMShsm to back up the data set identified
in the preceding ARC1001I or associated ARC0734I failed because one
of the following occurred:  The data set was cataloged on the wrong volume.  A data set
being cataloged on the wrong volume can result from processing an
uncataloged data set that has the same name as a cataloged data set.
  Another
possibility is that DFSMShsm scheduled a retry of the backup
of a data set in use. When the retry was attempted, the catalog entry
for the data set indicated that the data set was on a different volume,
with a different device type, or using a different access category
(VSAM vs non-VSAM) from the data set of the same name at the time
the retry was scheduled.

The data set is a multivolume or multivolume extended format data
set.  Under DFSMShsm movement,
the only multivolume data sets that are supported are SMS-managed
VSAM data sets. Under DFSMSdss movement, SMS-managed non-VSAM
data sets are also supported if they are not protected by a discrete RACF® profile and if USERDATASETSERIALIZATION
is used. Multiple volume standard user label data sets and multiple
volume unmovable data sets are not supported by either data movement
method.

The device type of the volume on which the data set resides and
as indicated by the catalog, is different from the device type of
the same volume currently mounted.
A VSAM data set contains an invalid expiration date. The expiration
date obtained from the catalog contains a year greater than 2155.
This data set is not supported.
The non-VSAM data set has a format-8 DSCB.
The Catalog has a format-8 DSCB.

System action
 The backup operation for the data set ends. DFSMShsm processing
continues.

Programmer response
 Notify the storage administrator to change
the environment to allow backup. If the data set is cataloged on the
wrong volume, the storage administrator can correct the catalog and
retry the command. Multivolume data sets can only be backed up under
the restrictions above. To process an unsupported multivolume data
set, use another method. If the device type of the volume, as indicated
in the catalog, is incorrect, correct the catalog entry and retry
the command. If the data set is being updated by another processor
in a multiple processing unit environment, review the present status
of the data set and proceed accordingly. If the VSAM data set contains
an invalid expiration date, change the expiration date in the catalog
to a year less than 2155.

Source
 DFSMShsm