Exit 35 – Dump Processing
Use Exit 35 to determine if RSCS should generate a dump, as part of ESTAE exit processing, when a task abends.
Point of Processing
| Process | Exit Attribute |
|---|---|
| Dump processing | Serially reusable |
Exit 35 is called when a task abends and ESTAE processing begins. At this point, interrupts have been disabled.
On return, RSCS issues a CP DUMP or VMDUMP command, as specified on the DUMP configuration file statement, to process the dump. For more information about the DUMP statement, see z/VM: RSCS Networking Planning and Configuration.
Entry Conditions
The following table shows the parameters passed in R0 and R1 to the first exit routine associated with this exit point. For more information about other register contents, see Standard Entry Conditions.
| Register | Contents |
|---|---|
| R0 | A code indicating the task that abended:
|
| R1 | Address of a parameter list that contains:
|
Exit Conditions
On return, Exit 35 sets the standard register contents (see Standard Exit Conditions).
Return Codes
| Return Code | Results |
|---|---|
| 0 | RSCS calls the next exit routine associated with this exit point and continues usual processing. |
| 4 | RSCS does not call any other exit routines associated with this exit point and continues usual processing. |
| 8 | RSCS issues a symptom summary message to the console but does not generate a dump for this abend. |
Programming Considerations
- RSCS does not request a dump or call Exit 35 if an S804, S80A, or S878 abend occurs in a link driver or auto-answer task.
- Return code 8 prevents RSCS from issuing a DUMP or VMDUMP command. However, if GCS does not provide a system diagnostic work area (SDWA), it may perform a dump for RSCS. For example, GCS processes a dump for RSCS if an S13E abend occurs when the FORCE command is issued. Here, the ESTAE exit and Exit 35 are not called.