Explanation
A request sent to DFSMShsm to migrate a data set failed. The
data set name is contained in the preceding ARC1001I or associated
ARC0734I message. The values for
reascode in message
ARC1001I or ARC0734I are:
- Reascode
- Meaning
- 1
- The data set is extended format, but DFSMSdss was not the datamover
for extended format data sets.
- 2
- The data set is extended format, but it is on a non-SMS-managed
volume.
- 3
- The data set is large format sequential, but DFSMSdss is not the selected
datamover for large format sequential data sets.
- 4
- A non-SMS-managed data set was cataloged on the wrong volume.
A data set cataloged on the wrong volume can result from processing
an uncataloged data set that has the same name as a cataloged data
set.
- 5
- The current level of DFSMShsm cannot migrate an extended format
data set (sequential striped or compressed). A minimum of DFSMShsm 1.1.0
is required for sequential striped data sets, and a minimum of DFSMShsm 1.2.0
is required for extended format compressed data sets.
- 6
- An attempt was made to migrate a Large Format Sequential data
set on a level of DFSMShsm that
does not support them.
- 8
- The device type of the volume the data set resides on, as indicated
by the catalog, is different from the device type of the same volume
currently mounted.
- 12
- The data set is a non-SMS-managed multiple volume data set. This
type of data set is not supported.
- 16
- The data set is an SMS-managed multiple volume non-VSAM data set,
but the datamover is DFSMShsm. This type of data set is only
supported if DFSMSdss is
the datamover. Multiple volume standard user label data sets are not
supported by either data movement method.
- 20
- The data set is an SMS-managed multiple volume, non-VSAM data
set, and DFSMSdss is
the datamover, but USERDATASETSERIALIZATION is not specified and is
required for support of this data set.
- 21
- The non-VSAM data set has a format-8 DSCB.
- 22
- 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.
- 24
- The data set is an SMS-managed multiple volume, non-VSAM data
set, DFSMSdss is
the datamover and USERDATASETSERIALIZATION is specified; However,
the data set is RACF-indicated. This data set is not supported.
- 26
- The DSCB for this migrated data set indicates DS1LSTAR=0, which
should not occur for a migrated data set.
- 28
- The data set has retained locks.
- 30
- The data set is RLS inconsistent.
- 32
- The data set is empty, SMS-managed, multiple volume, and physical
sequential with a block size of zero.
- 34
- FREEVOL processing on a Pre-V1R11 system does not move a catalog
information data set.
- 60
- Space management is processing a data set on a primary volume,
but the MCD record indicates a valid migrated data set exists with
the same name. Issue a RECALL command in case the previous recall
failed due to a product or system outage.
- 98
- An attempt was made to migrate a data set from ML1 to ML2, but
the data set was either not cataloged or was cataloged with a volume
serial of other than MIGRAT.
System action
The migration operation of the data set ends. DFSMShsm processing
continues.
Programmer response
Notify the storage administrator. If the
data set is cataloged on the wrong volume, the storage administrator
can correct the catalog and retry the migration. Multivolume data
sets can only be migrated 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 migration. If the data set is updated
by another processor in a multiple processing unit environment, review
the present status of the data set and proceed accordingly. The values
for
reascode are:
- Reascode
- Meaning
- 1
- Specify DFSMSdss as
the datamover for extended format data sets.
- 3
- Contact IBM® Support and
indicate to them that your installation has HSM as the default data
mover for migration of Large Format Data sets and that needs to be
changed.
- 2
- Move the data set to an SMS-managed volume.
- 4
- The storage administrator can correct the catalog and retry the
command.
- 5
- No action required.
- 6
- Retry migration on DFSMShsm V1R7 or higher which supports Large
Format Sequential data sets.
- 8
- If the device type of the volume, as indicated in the catalog,
is incorrect, correct the catalog entry and retry the command.
- 12
- No action required.
- 16
- Select DFSMSdss as
the datamover.
- 20
- See the storage administrator.
- 21
- No action required.
- 22
- If the expiration date is invalid, the storage administrator can
correct the catalog and retry the command.
- 24
- Use a generic instead of discrete RACF® profile
to protect the data set.
- 26
- Recall the data set.
- 28
- The RLS backouts pending for the data set must be completed before
the data set is eligible for migration.
- 30
- The data set must be forward recovered before it is eligible for
migration.
- 32
- No action required.
- 34
- Issue the FREEVOL command from a V1R11 or later DFSMShsm system.
- 60
- Issue a RECALL command in case the previous recall failed due
to a product or system outage. If the second recall fails, follow
the instructions applicable for all reason codes for this message
under Application Programmer Response.
- 98
- Issue a TSO LISTCAT command. If the data set is cataloged on a
primary volume, issue a RECALL command in case the previous recall
failed due to a product or system outage. If the second recall fails,
follow the instructions applicable for all reason codes for this message
under Application Programmer Response.