IEA998I

Explanation
The system could write only a partial SYSMDUMP
ABEND dump to the data set on a direct access storage device (DASD)
and defined on the SYSMDUMP DD statement. In the message text: dsname
The data set specified on the SYSMDUMP DD statement.
rsn
Specific codes to identify what caused the dump to be considered
partial.

An error occurred as indicated
by the reason code. The explanation of the hex reason code is as follows:Reason Code
Explanation

00
A potential lockout was
detected (timeout). Tasks in the address space were prematurely reset
dispatchable before all data could be put into the dump. The resulting
SYSMDUMP is likely still usable for analysis.

04
Data spaces were requested,
but were not available.

08
The coredump byte limit
was exceeded for a z/OS® UNIX System Services task. 

0C
SDUMP returned a return
code of 4. The most likely reason is that the dump data set was filled
before the system finished writing all dump data. But it could also
be due to other reasons such as unexpected abends in SDUMP, or an
I/O error occurred while the system was writing the dump to the dump
data set. Other messages were probably also issued.

System action
The system continues processing.

System programmer response
Involvement is only
needed for I/Oerror cases and unexpected abends. The device  may need
servicing or defragging. LOGREC should have records for the unexpected
abends. 

Programmer response
For problems other than those relating to I/O, use the SYSMDUMP
data set. While not all of the virtual storage requested was collected,
enough may have been dumped to diagnose the problem that caused the
dump.
I/O errors or, running out of space, result in other messages
being issued. For the space problem, increase the size of the DASD
data set specified on the SYSMDUMP DD statement.

Source
SVC Dump (SCDMP)

Module
IEAVTSYS

Routing code
11

Descriptor code
6

Reason Code	Explanation
00	A potential lockout was detected (timeout). Tasks in the address space were prematurely reset dispatchable before all data could be put into the dump. The resulting SYSMDUMP is likely still usable for analysis.
04	Data spaces were requested, but were not available.
08	The coredump byte limit was exceeded for a z/OS® UNIX System Services task.
0C	SDUMP returned a return code of 4. The most likely reason is that the dump data set was filled before the system finished writing all dump data. But it could also be due to other reasons such as unexpected abends in SDUMP, or an I/O error occurred while the system was writing the dump to the dump data set. Other messages were probably also issued.