Explanation
During processing of a DFSMSdss function, a system
utility was invoked to process the specified data set or volume. The
utility encountered errors, and processing failed.
System action
The data set is not processed. The return code
is 8.
Operator response
Programmer response
Take one of the following actions:
- For abending utilities, see z/OS MVS System Codes for
an explanation of the abend code. If the abend is caused by insufficient
storage (DASD or virtual), you must run the utility itself (not through DFSMSdss),
as described in z/OS DFSMSdfp Utilities.
If IEHMOVE abends with code 0C4, it could be because DFSMSdss called
it with a task I/O table (TIOT) referring to more DD statements than
IEHMOVE can handle. In this case, change the DFSMSdss filtering to select
fewer data sets.
- For IEHMOVE, IEBCOPY, or IEBISAM error return codes, run the job
with UTILMSG=ERROR or UTILMSG=YES to propagate the utility's
SYSPRINT data set. See z/OS MVS System Messages, Vol 7 (IEB-IEE) and z/OS MVS System Messages, Vol 8 (IEF-IGD) for
explanations of the utility messages.
- For IDCAMS error return codes, run the job by specifying the DFSMSdss UTILMSG=YES parameter.
See z/OS MVS System Messages, Vol 6 (GOS-IEA) for
an explanation of the messages.
- For ICKDSF error return codes, run the job with UTILMSG=ERROR or UTILMSG=YES to
propagate the utility's SYSPRINT data set. See the Device Support Facilities (ICKDSF) User's Guide and Reference for
an explanation of the messages.
Note: When performing in-place operations, the source data
sets have been left unusable by the failure of the job. Check and
restore all data sets from backup if necessary.
Source