Explanation
The caller passed incorrect parameters in a request
for an SVC dump.
Register 15 contains a hexadecimal reason code
that explains the error:
- Code
- Explanation
- 04
- The address of the parameter list is zero, or the caller is in
AR ASCMODE and the access register of the parameter list is non-zero.
- 08
- The parameter list is not a valid SVC dump or SNAP parameter list.
- 0C
- The caller-supplied data set is on an unsupported device.
- 10
- One of the following:
- In a caller-supplied storage range, the start address is greater
than or equal to the end address.
- For any of the LIST, STORAGE and SUMLIST parameters, the high-order
bit of the last ending address was not set to B'1'.
- For any of the LISTA, LISTD, LIST64, SUMLSTA, SUMLSTL and SUMLIST64
parameters, the length of the list or the number of ranges was not
correctly specified.
- 14
- The caller-supplied data for the HDR or HDRAD option is greater
than 100 characters.
- 18
- The caller requested the 4-kilobyte system queue area (SQA) buffer,
but it is not serialized.
- 1C
- The parameter list or what it points to is in the 4-kilobyte SQA
buffer.
- 20
- The caller supplied a data control block (DCB) address, and the
DCB is not open or the address is not valid.
- 28
- An address space identifier (ASID) specified in the ASIDLST, ASID,
or SUBPLST parameter is incorrect. The ASID is less than zero or greater
than the maximum value.
- 38
- The caller specified the 4-kilobyte SQA buffer, but an SVC dump
function was already in progress.
- 44
- The caller specified a subpool greater than the maximum value
allowed (255).
- 47
- An inconsistency was detected in the SDUMP parameter list that
might be resolved by zeroing the storage for the list before calling
the SDUMPX macro.
- 50
- Not all of the parameter list is accessible.
- 54
- The caller-supplied DCB is not accessible.
- 58
- The caller's storage list is not accessible.
- 5C
- The caller's header data is not accessible.
- 60
- The caller-supplied event control block (ECB) is not accessible.
- 64
- The caller's ASID list is not accessible.
- 68
- The caller's SUMLIST is not accessible.
- 6C
- The caller's subpool identification (ID) list is not accessible.
- 70
- The caller's storage key list is not accessible.
- 74
- A copy of SLIP registers and a copy of the program status word
(PSW) are not accessible.
- 78
- The caller-supplied SRB is not accessible.
- 7C
- An incorrect version number is in the parameter list.
- 80
- The caller-supplied LISTD or LIST64 list is not accessible.
- 84
- The caller-supplied SUMLSTL or SUMLIST64 list is not accessible.
- 88
- SDUMPX parameter list contained conflicting parameters.
- 8C
- The ID is longer than 50 characters.
- 90
- The ID is not addressable.
- 94
- The PSW/register area is an incorrect length.
- 98
- The PSWREGS is not addressable.
- 9C
- The symptom record is incorrect.
- A0
- The symptom record is not addressable.
- A4
- The data extent block (DEB) for the caller-supplied DCB is not
accessible.
- AC
- The STRLIST area supplied by the caller is not accessible.
- B0
- The caller-supplied INTOKEN area is not accessible.
- B4
- The caller-supplied REMOTE area is not accessible.
- B8
- The caller-supplied PROBDESC area is not accessible.
- BC
- The caller-supplied JOBLIST area is not accessible.
- C0
- The caller-supplied DSPLIST area is not accessible.
- C4
- The caller-supplied REMOTE area is not valid; the length of a
field in the area is specified as less than 4 bytes.
System action
The system writes a logrec data set error record.
SVC dump processing attempts retry and gives the caller a return code
of 8 and an associated reason code. If retry is not possible, the
system abnormally ends the caller. SVC dump processing issues message
IEA911E or IEA611I. This message indicates whether the dump is complete
or partial.
System programmer response
For reason code X'AC',
make sure the STRLIST area specified is addressable from the caller's
current address space. Then request the dump again.
For all
other reason codes, correct the incorrect parameters and issue the
SDUMP macro again.
If the problem persists or is in an IBM-provided
program, search problem reporting data bases for a fix for the problem.
If no fix exists, contact the IBM® Support
Center. Provide the assembly listing for the job.
Source