Explanation
An error occurred during the processing of a DFP
program that could not be attributed to incorrect user input.
In
the message text:
- rc
- Associates this message with system completion code 315 and with
the return code.
- jjj
- Job name.
- sss
- Step name.
- ddname
- DDname, or ******** if unable to locate the DDname.
- smsrc
- The SMS return code.
- smsrs
- The SMS reason code.
The SMS return and reason codes caused STOW
to initiate the 315 ABEND while processing a PDSE. If error return
codes from SMS were not the cause of the abend, these fields will
contain the characters 'N/A'.
The explanation for the hex return
code is as follows:
- Return Code
- Explanation
- 00
- No dump was taken and no software record was written by STOW.
An X'0F4' abend preceded this X'315' abend and resulted
in an SVC dump. The dump contains the values in the SMSRC and SMSRS
fields of this IEC911I message as return and reason codes in the dump
title.
- 01
- SDUMP successfully completed.
- 02
- The dump data set contains a partial dump.
- 03
- Unable to dump.
- 04
- SWAREQ macro failed. SWAREQ is required to determine the data
set name, so that the DS1NOBDB field in the format 1 DSCB can be updated.
The SWAREQ return code can be found in the SMSRC field of the IEC911I
message. For SWAREQ return codes, see z/OS MVS Programming: Authorized Assembler Services Reference SET-WTO.
STOW issues SWAREQ with UNAUTH=NO.
- 05
- DADSM update function failed. The return code and diagnostic information
returned from DADSM update are in the SMSRC and SMSRS fields of the
IEC911I message. For help interpreting these DADSM codes, see z/OS DFSMSdfp Diagnosis.
- 0C
- STOW attempt failed because of a data set out-of-space error.
System action
An SVC Dump is issued. A software error record
is written to the logrec data set and the task is ended.
System programmer response
If the error recurs and the program
is not in error, look at the messages in the job log for more information.
search problem reporting data bases for a fix for the problem. If
no fix exists, contact the IBM® Support
Center. Provide the JCL, the program listing for the job, the logrec
data set error record, and all printed output and output data sets
related to the problem.
Programmer response
Make sure that the STOW macro instruction
is correctly coded, and that the parameter list and DCB involved are
not modified by your program during the processing of SVC 21.
Source
Module
Routing code
Descriptor code