Explanation
During a space management operation, the dynamic
allocation routine has attempted to allocate a migration data set.
The allocation has failed with other than a no space indication. In
message ARC1001I or ARC0734I, the reason codes
reascode have
the following values:
- Reascode
- Meaning
- 4
- More than one data set exists with the same name (migration version)
on the volume.
- 6
- The SDSP serialization check indicates that SDSP is in use.
- 7
- The SDSP is needed by recall.
- 8
- The volume could not be mounted.
- 10
- The DFSMShsm-owned copy of the data set to be migrated is estimated
to be greater than 64K tracks. Data sets greater than 64K tracks cannot
be migrated to DASD if the owned copy will also be greater than 64K
tracks.
- 16
- There is another dynamic allocation error.
- 20
- An installation-wide exit has cancelled the request.
- 24
- There is an invalid parameter list.
- 37
- The unit type and volume serial number from the mounted volume
table are inconsistent.
- 39
- An error has occurred in setting the RACF® indicator on in the DSCB of the migration
copy.
- 40
- The volume is SMS managed.
- 41
- The volume where the migration copy has been allocated (as returned
by DYALLOC) is not the same volume that DFSMShsm has requested. In an SMS environment,
the data set is allocated to SMS-managed storage.
System action
The space management operation for the data set
ends. DFSMShsm processing
continues.
Programmer response
Reason codes received in message ARC1001I
or ARC0734I have the following meanings:
- Reascode
- Meaning
- 7
- Retry the operation at a later time.
- 8, 16, 20
- Contact the storage administrator or system programmer to correct
the problem, and retry the operation.
- 10
- If you want to migrate the data set, migrate it to tape. Or, if
the data mover is DFSMSdss and
less than 64K tracks of data are actually in use, try migrating the
data set using DFSMShsm as
the data mover if the DFSMShsm data mover supports the data set’s
organization. If compaction is not in use for the data set, try migrating
the data set with compaction.
- 24, 37
- A logical error has occurred and has built an invalid parameter
list.
- 39
- An error has occurred in accessing the DSCB to set the RACF indicator on. The errors are
either failure to read the JFCB, failure to open the VTOC, or the
wrong record has been returned from the read.
- 40, 41
- Update the SMS storage class routine so migration copies are filtered
to a null storage class. See z/OS DFSMShsm Implementation and Customization Guide for an explanation on how to code
the storage class routine.