A system dump contains the storage information needed to diagnose
errors. You can use
Language Environment to generate
a system dump through any of the following methods:
- DYNDUMP(hlq,DYNAMIC,TDUMP)
- You can use the DYNDUMP runtime option to obtain IPCS-readable
dumps of user applications that would ordinarily be lost due to the
absence of a SYSMDUMP, SYSUDUMP, or SYSABEND DD statement.
- TERMTHDACT(UAONLY, UATRACE, or UADUMP)
- You can use these runtime options, with TRAP(ON), to generate
a system dump if an unhandled condition of severity 2 or greater occurs.
For more details about the level of dump information produced by each
of the TERMTHDACT suboptions, see Generating a Language Environment dump with TERMTHDACT .
- TRAP(ON,NOSPIE) TERMTHDACT(UAIMM)
- TRAP(ON,NOSPIE) TERMTHDACT(UAIMM)
generates a system dump of the user address space of the original
abend or program interrupt prior to the Language Environment condition
manager processing the condition.
- ABPERC(abcode)
- The ABPERC runtime option specifies
one abend code that is exempt from the Language Environment condition
handler. The Language Environment condition
handler percolates the specified abend code to the operating system.
The operating system handles the abend and generates a system dump.
ABPERC is ignored under CICS®.
- Abend Codes in Initialization Assembler User Exit
- Abend codes
listed in the initialization assembler user exit are passed to the
operating system. The operating system can then generate a system
dump.
- CEE3ABD
- You
can use the CEE3ABD callable service to cause the operating system
to handle an abend.
See system or subsystem documentation for detailed system dump
information.
The method for generating a system dump varies for each of the Language Environment runtime
environments. The following sections describe the recommended steps
needed to generate a system dump in a batch, IMS™, CICS,
and z/OS UNIX shell
runtime environments. Other methods may exist, but these are the recommended
steps for generating a system dump.
For details on setting Language Environment runtime
options, see z/OS Language Environment Programming Guide.