Analyzing abends
An abend is an abnormal end.
Table 1 describes the types of abends that can
occur.
Type of abend | Description | Where to find help |
---|---|---|
User Abends | User abends are generated by C run-time routines. They usually start with U409x. | |
Platform abends | Abend 3C5 and abend 4C5 are internal abends generated by TCP/IP. Note the reason code stored in register 15 and check the IBM® database for known problems. | See z/OS Communications Server: IP and SNA Codes. |
System abends | 0C4, 0C1, and 878 are system abends. | See z/OS MVS System Codes. |
0D6/0D4/0C4 abends can occur when an application is removed from VMCF/TNF with the F VMCF/TNF, REMOVE command, or if VMCF is not active when an application or command, which requires it is started or issued. | See z/OS MVS System Codes. Can occur when an application
is removed from VMCF/TNF with the F VMCF/TNF, REMOVE command. It can
also occur when an application or command, which requires it is started
or issued. The following TCP/IP applications and commands will abend
if VMCF is not active:
|
|
CEEDUMPs | Language Environment® produces certain types of abends detected for z/OS UNIX applications such as z/OS UNIX Telnet. CEEDUMPs are usually written to the current working directory in the hierarchical file structure. | See z/OS Language Environment Debugging Guide. |
A dump is usually produced when TCP/IP or a TCP/IP component address space experiences an abend. If an abend occurs and no dump is taken, the dump files or spools might be full or a SYSMDUMP DD statement might not have been specified in the failing procedure. If TCP/IP or a TCP/IP component was not able to complete the dump, gather a console dump of TCP/IP or the failing TCP/IP component, the external trace data set if available, and system log as soon as possible. Otherwise, you must re-create the abend or wait for it to occur again.
For more information about debugging the abends and the system abends (for example, abends 0C4, 0C1, and 878), see z/OS Problem Management.