Explanation
During a DFSMShsm backup operation, the dynamic allocation
routine has been called to allocate a backup version of a data set.
The allocation has failed with other than a no space indication. The
data set name is in message ARC1001I. In message ARC1001I and ARC0734I,
the reason code
reascode has the following values:
- Reascode
- Meaning
- 4
- There is more than one data set with the same name on the volume.
- 8
- The volume is not mounted.
- 10
- The DFSMShsm-owned copy of the data set to be backed up is estimated
to be greater than 64K tracks. Data sets greater than 64K tracks cannot
be backed up to DASD.
- 16
- There has been another dynamic allocation error.
- 20
- An installation-wide exit has cancelled the request.
- 24
- There is an invalid parameter list that has been passed to dynamic
allocation from DFSMShsm.
- 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.
- 40
- The volume is SMS managed.
- 41
- The volume where the backup 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 backup operation ends. DFSMShsm processing continues.
Programmer response
Reason codes received in message ARC1001I.
- Reascode
- Meaning
- 8, 16, 20
- Enlist the aid of the storage administrator or system programmer
to correct the problem, and retry the operation.
- 10
- If you want to back up the data set, back it up to tape. Or, if
the data mover is DFSMSdss and
less than 64K tracks of data are actually in use, try backing up 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 backing
up 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
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 backup copies are filtered
to a null storage class. See the topic on "Writing an Automatic
Class Selection Routine that Directs DFSMShsm-Owned Data Sets to Non-SMS-Managed
Storage" under the topic, "Specifying Commands that Define Your DFSMShsm Environment" in z/OS DFSMShsm Implementation and Customization Guide, for an explanation on coding the storage class routine.