Locate generated SVC dump
MVS will generate a notification message that the SVC dump has been created. You should locate the SVC dump that is produced by the product abend. The data set name for the SVC dump can be found in the JES messages in the JOBLOG. BMC might request that you supply the SVC dump with other requested documentation.
If the Fast Path product is unable to generate an SVC dump automatically following a product abend, message BMC110980E might be generated with return code 8. The following table lists explanations for reason codes that might be issued with the RC=8.
No SVC dump was requested.
An SVC dump was successfully started.
An SVC dump was suppressed because the capture phase of another SVC dump was in progress.
AN SVC dump was suppressed by a request by the installation (example: DUMP=NO at IPL or CHNGDUMP SET, NODUMP).
An SVC dump was suppressed by a SLIP NODUMP command.
An SVC dump was suppressed because a SYS1.DUMP data set was not available.
An SVC dump was suppressed because an I/O error occurred during the initialization of the SYS1.DUMP data set.
An SVC dump was suppressed because an SRB could not be scheduled to activate the dump tasks in the requested address spaces.
An SVC dump was suppressed because a terminating error occurred in SVC dump before the first dump record was written.
An SVC dump was suppressed because a status stop SRB condition was detected.
An SVC dump was suppressed by Dump Analysis and Elimination (DAE).
The parameter list address is zero.
The parameter list is not a valid SVC or SNAP parameter list.
The caller-supplied data set is not supported.
The start address is greater than or equal to the end address in a storage list.
The caller-supplied header is longer than 100 characters.
The caller requested a 4K buffer, but did not reserve it.
A storage list overlaps the 4K buffer.
The caller-supplied DCB is not valid.
An ASID in the ASID list is syntactically not valid.
The 4K buffer was requested with an SVC dump already in progress.
A subpool ID that was not valid was specified in the subpool list.
Part of the parameter list is inaccessible.
The caller-supplied DCB is inaccessible.
The caller-supplied storage list is inaccessible.
The caller-supplied header data is inaccessible.
The caller-supplied ECB is inaccessible.
The caller’s ASID list is inaccessible.
The caller’s SUMLIST/SUMLSTA is inaccessible.
The caller’s SUBPLST is inaccessible.
The caller’s KEYLIST is inaccessible.
Copies of the SLIP register and PSW are inaccessible.
The caller-supplied SRB is inaccessible.
The version number in the parameter list is not valid.
The caller’s LISTD is inaccessible.
The caller’s SUMLISTL is inaccessible.
The parameter list contains conflicting parameters.
The ID is longer than 50 characters.
The ID is not addressable.
The PSWREGS area is an incorrect length.
The PSWREGS area is not addressable.
The symptom record is not valid.
The symptom record is not addressable.
The DEB for the caller-supplied DCB is inaccessible.
SVC dump is already using the maximum amount of virtual storage (as determined by the installation, using the MAXSPACE parameter on the CHNGDUMP command) to process other dumps.
The caller-supplied STRLIST area is inaccessible.
The caller-supplied INTOKEN area is inaccessible.
The caller-supplied REMOTE area is inaccessible.
The caller-supplied PROBDESC area is inaccessible.
The caller-supplied JOBLIST area is inaccessible.
The caller-supplied DSPLIST area is inaccessible.
The caller-supplied REMOTE area is not valid. The length of a field in the REMOTE area is specified as less than 4 bytes.
SVC dump stopped the dump because the system resources manager (SRM) detected a critical shortage of auxiliary storage.