Explanation
During the recall, delete, recovery, or restore
of a data set, DFSMShsm attempted
to perform a task for a data set that required access to the storage
management subsystem (SMS). The data set name is given in the preceding
ARC1001I message, along with a
reascode. The following
are
reascode values and meanings:
- Reascode
- Meaning
- 01
- An error occurred while attempting to determine the SMS construct
names. Either DFSMShsm encountered
an error attempting to invoke the automatic class selection (ACS)
routines or the ACS routines failed. Check the command activity log
for messages indicating the actual failure reason. Look for ARC0935I
for a failure reason and SMS message IGD306I. If you received SMS
IGD306I— UNEXPECTED ERROR DURING INTEXPDT PROCESSING, RETURN CODE
8, REASON CODE 1017, the problem may be the data set expiration date
in the DFSMShsm MCC
record for a recover function or the data set expiration data in the DFSMShsm MCD
record for a recall function.
- 02
- An error occurred while attempting to allocate space on the target
volume for the recall or recovery of a non-VSAM data set. Either DFSMShsm encountered
an error attempting to invoke the VTOC/Data Set Services’ (VDSS) create
space function or VDSS had a failure creating the space. If the storage class assigned by your ACS routines is
using guaranteed space, ensure that the assigned storage class has
the original volume serials that the data set was created with, otherwise
allocation fails. Check the command activity log for messages
indicating the actual failure reason. Look for ARC0935I for a failure
reason and SMS message IGD306I. If you received SMS IGD306I-UNEXPECTED
ERROR DURING INTEXPDT PROCESSING, RETURN CODE 8, REASON CODE 1017,
the problem may be the data set expiration date in the DFSMShsm MCC
record for a recover function.
- 03
- An error occurred while attempting to create a non-VSAM data set
record (NVR) in the VSAM catalog entry on the target volume. The DEFINE
NVR function failed. Message ARC0950I was issued to the command activity
log with the actual failure reason.
- 04
- An error occurred attempting to alter the BCS entry in the catalog
for a non-VSAM data set. The data set was either SMS-managed before
the recall or recovery and was being recalled or recovered to non-SMS-managed
storage, or the data set was being recalled or recovered to SMS-managed
storage. The target volume, device type, and SMS construct names were
to be altered in the BCS entry. The alter function failed. Message
ARC0950I was issued to the command activity log with the actual failure
reason.
- 05
- An error occurred in obtaining the management class definition
for the data set.
- 06
- The version of DFSMSdss installed
on the system is not of a sufficient level to support SMS-managed
data sets. A sufficient level of DFSMSdss is required to restore an SMS-managed
data set, unless FORCENONSMS is specified.
- 07
- An SMS-managed data set is not eligible for automatic recall through
the OPEN DSCB not found exit (IFG0EX0A). One of the following occurred:
- An allocation (either a batch job or TSO CLIST) with a subsequent
OPEN for an SMS-managed data set specified a non-SMS-managed volume.
- An allocation for an SMS-managed data set specified an SMS-managed
volume, and the SMS subsystem was not installed or was not active.
A 213-2C ABEND will occur. The recall is not permitted because
the results would be unpredictable.
- 08
- SMS is inactive, and the FORCENONSMS parameter was not specified
for a recall or recovery. Interaction with the SMS subsystem is required
in order to process the request.
- 09
- An error occurred attempting to create a non-VSAM entry in the
catalog (BCS entry). The Define BCS function failed. Message ARC0950I
was issued to the command activity log with the actual failure reason.
- 10
- An SMS-managed data set is not eligible for automatic recall directly
from a VSAM OPEN call. One of the following situations occurred:
- An allocation (either a batch job or TSO CLIST) with a subsequent
VSAM OPEN for an SMS-managed data set specified a non-SMS-managed
volume.
- An allocation for an SMS-managed data set specified an SMS-managed
volume, but the SMS subsystem was either not installed or was not
active.
- An OPEN was done without a preceding allocation.
The OPEN will fail. The recall is not permitted because
the results would be unpredictable. The data set would not necessarily
be recalled to the volume that the OPEN request specified.
- 12
- An SMS-managed data set could not be renamed to a temporary name.
Message ARC0780I was issued to describe the problem. Message ARC0950I
was issued to the command activity log with the actual failure reason.
- 13
- A non-SMS-managed data set cannot be recovered to an SMS-managed
volume. The data set being processed was determined by ACS routines
to be a non-SMS-managed data set, but the target volume is an SMS-managed
volume.
- 14
- An SMS-managed data set cannot be restored from a physical dump
copy to a non-SMS-managed volume. The data set being recovered has
been determined by ACS routines to be SMS managed, but the target
volume selected by DFSMShsm is
a non-SMS-managed volume.
- 20
- An SMS-managed data set is to be restored but not cataloged. This
request may be made only by a DFSMShsm authorized user. This condition
arises when a VSAM data set which does not have an applicable backup
version is to be restored. DFSMShsm can catalog a VSAM data set during
restore only by recovering the data set prior to the restore. All
SMS-managed data sets must be cataloged.
- 24
- An error occurred while attempting to allocate space on the target
volume for the recall or recovery of a BDAM data set. Either DFSMShsm encountered
an error attempting to invoke the VTOC data set services (VDSS) create
space function or VDSS had a failure creating the space. The data
set was a direct access data set and DFSMShsm issued an SMS track allocation
request. The target volumes available either have track sizes smaller
than the requested size for the data set, or the target volumes do
not have enough free space available (in tracks) for the request.
If DFSMShsm is
the data mover and the storage class for the data set has guaranteed
space specified, then this error may occur if the data set is being
directed to a volume that is not in a storage group associated with
that storage class. Message ARC0935I was issued to the command activity
log with the actual failure reason.
- 25
- Error in retrieving the management class definition.
- 26
- Error in moving the management class definition.
- 27
- Error in retrieving the default management class definition.
System action
The operation, which is indicated in the ARC1001I
message preceding this message, terminates for the data set. DFSMShsm processing
continues.
Programmer response
- Reascode
- Meaning
- 01
- If the command activity log has an SMS IGD306I—UNEXPECTED ERROR
DURING INTEXPDT PROCESSING RETURN CODE 8, REASON CODE 1017 message
associated with the failing data set, then the problem may be the
data set expiration date. If you were recalling a data set, use the
FIXCDS command to display the MCD record for the data set and check
the MCDEXPDT field. Correct this field and retry recalling the data
set. If you were recovering a data set, use the FIXCDS command to
display the MCC record for the backup version and check the MCCEXPDT
field. Correct the MCCEXPDT field and retry recovering the data set.
Following the RECALL or RECOVER, check the Format1 DSCB expiration
field (dslexpdt) for non-VSAM data sets and correct this field if
necessary. Failing to correct this field will result in the same RECALL
or RECOVER failure for the data set.
- 02
- If the command activity log has an SMS IGD306I—UNEXPECTED ERROR
DURING INTEXPDT PROCESSING RETURN CODE 8, REASON CODE 1017 message
associated with the failing data set, then the problem may be the
data set expiration date. If you were recalling a data set, use the
FIXCDS command to display the MCD record for the data set and check
the MCDEXPDT field. Correct this field and retry recalling the data
set. If you were recovering a data set, use the FIXCDS command to
display the MCC record for the backup version and check the MCCEXPDT
field. Correct the MCCEXPDT field and retry recovering the data set.
Following the RECALL or RECOVER, check the Format1 DSCB expiration
field (dslexpdt) for non-VSAM data sets and correct this field if
necessary. Failing to correct this field will result in the same RECALL
or RECOVER failure for the data set.
- 05
- See message ARC0935I in the command activity log for the specific
failure. List the catalog information to determine the management
class name. Define the management class if it does not exist. If the
management class exists, contact the IBM® Support
Center.
- 08
- Do one of the following:
- Reissue the request when the SMS subsystem is active.
- Reissue the request with the FORCENONSMS parameter specified.
- 06
- Do one of the following:
- Reissue the request when a sufficient level of DFSMSdss is installed.
- Reissue the request without specifying the FROMDUMP parameter.
Instead, use the GENERATION parameter on the command. This causes
an incremental backup version to be used for the recovery of the data
set.
- The FORCENONSMS and TOVOLUME parameters can also be used to force
the data set to a non-SMS-managed volume.
- 07
- An HRECALL command can be used to recall the data set when SMS
is active, or the explicit volume serial can be removed from the JCL
or CLIST.
- 10
- An HRECALL command can be used to recall the data set when SMS
is active or an allocation of the data set can be done without specifying
the volume serial number.
- 13
- Issue a data set RECOVER command with either FORCENONSMS or TOVOLUME,
specifying a non-SMS-managed volume. This recovers the data set to
a non-SMS-managed volume.
- 14
- Issue a data set RECOVER command with the TOVOLUME parameter specifying
an SMS-managed volume that has a device type similar to the original
volume that has been dumped. This restores the data set to an SMS-managed
volume.
- 20
- Do one of the following:
- Preallocate the SMS VSAM data set.
- Have the recover request issued by a DFSMShsm authorized user.
- If the data set is not preallocated, a DEFINE CLUSTER RECATALOG
IDCAMS command must be issued after the restore is complete.
- 24
- Ensure the ACS routine does not target the data set to a pool
of volumes with smaller track sizes than the original source device.
Ensure that at least one volume in the volume pool has enough free
space to honor the allocation request. If DFSMShsm is the data mover,
ensure the data set is not directed to a device that is not in a storage
group associated with the storage class of the data set.
For each of the other error conditions listed
above that have a corresponding message containing more information
about the failure, consult the corresponding message. The corresponding
message is written in the command activity log. See the programmer
response topics of
the appropriate related message for more details.
Retry the
operation after corrective action has been taken, or after investigation
has determined the error will not recur.
If not attempted previously,
an authorized DFSMShsm user
may use the FORCENONSMS parameter to recall or recover the data set
to non-SMS-managed storage. This may provide a temporary bypass for
the problem.