TSO/ISPF Diagnostics

Because of the recovery mechanisms within TSO/ISPF, most dumps automatically generated by TSO/ISPF do not contain any useful information. You must take certain specific steps to prevent normal TSO/ISPF abend recovery. Without these steps, the resulting dump information is insufficient and unusable.

Typical examples of TSO/ISPF dumps that are insufficient and unusable are as follows:

  • S0C4 in LMOD(ISPMAIN) CSECT(ISPMRO)

    ISPMRO invokes SVC13 to generate an additional abend after ISPF has already terminated and recovered from an ISPF dialog error. This is normal processing when ISPF is not in test mode.

  • S0C4 in ISPSUBS, ISRSUBS, or ISPTASK

    These are the names of ISPF load modules containing common service subroutines. You need to research the dump further or redocument the problem to identify the original abend and the abending CSECT.

    When an ISPF-related problem can be duplicated, BMC Software Customer Support personnel may occasionally ask you to perform certain steps to obtain a dump of the TSO/ISPF address space. These steps typically include invoking TSO/ISPF in test mode, pre-allocating a SYSMDUMP DD statement, reproducing the original abend, or inducing a diagnostic abend via the DBC¢ command. You must follow these steps exactly to generate an TSO/ISPF dump with meaningful and usable information.

Was this page helpful? Yes No Submitting... Thank you

Comments