SDUMP NOT SCHEDULED FOR REMOTE DUMP. INCIDENT TOKEN:intoken REASON
- reason
Explanation
The system was unable to write an SVC dump for
another system in a sysplex.
In the message text:
- intoken
- The incident token for the dump. The token contains the name
of the sysplex, the name of the system that originated the dump request,
and the date and time of the request.
- reason
- One of the following:
- DUMP=NO WAS SET AT IPL
OR INDICATED BY CHNGDUMP
- The installation indicated that no SVC dumps are to be written.
- NO SRBS COULD BE SCHEDULED TO START THE DUMP
- A system error occurred.
- SVC DUMP ABNORMALLY TERMINATED
- A system error occurred.
- A STATUS STOP SRBS CONDITION WAS DETECTED
- A system error occurred.
- NO STORAGE AVAILABLE
- The system could not acquire the storage needed to build the dump
request; no dump was written.
- UNKNOWN
- A system error occurred.
System action
The system continues processing but does not write
the requested SVC dump.
This message is sent to the console
on which the DUMP command was entered or, if the dump was requested
by another system in the sysplex but not by a DUMP command, to console
ID 0.
System programmer response
Determine why the system could not
write an SVC dump requested by another system in the sysplex. If the
problem cannot be corrected, search problem reporting data bases for
a fix for the problem. If no fix exists, contact the IBM® Support Center.
Source
Module
Routing code
Descriptor code