TMS:Engine abend and snap dump codes
This section describes the TMS:Engine abend codes and snap dump codes.
TMS:Engine can issue the following abend codes:
| Code | Description |
|---|---|
| U0000 | After TMS:Engine termination is requested and confirmed, a program timer is set limiting the shutdown time to 30 seconds. If the timer expires, user abend 0 is invoked to purge TMS:Engine from the system. The unexpected halt of a component usually causes. If the problem persists, contact IBM® Software Support. |
| U0004 | The TMS:Engine load library cannot be opened during initialization. This is usually the result of an invalid RKANMODL DD statement in the TMS:Engine JCL procedure. There should also be z/OS® messages in the JES sysout log indicating a specific reason why the library could not be opened. Use this information to correct the error and restart TMS:Engine. |
| U0008 | During start-up, TMS:Engine detected an exception condition. While trying to issue a WTO indicating the source of the error, the integrity of the TMS:Engine address was found to be corrupted. Contact IBM Software Support. |
| U0012 | During start-up, TMS:Engine detected an exception condition. A message indicating the source of the error is written to the TMS:Engine log. Refer to the error message to determine your course of action. |
| U0100 | This is a run-time abend invoked by the TMS:Engine product to generate dump
documentation for a recoverable software failure. The abend is accompanied by a message written to
the TMS:Engine log, which explains the reason for the abend. Most of the reasons refer to storage
allocation/deallocation errors. After a system dump is taken, the product attempts to recover from
this failure automatically. Successful recovery is indicated by the message KLVER011 Note: You
should shut down the TMS:Engine product and restart as soon as possible after receiving this abend
code. Although recovery may be successful, the address space may be damaged.
|
| U0200 | This is a run-time abend invoked by the TMS:Engine product to generate dump documentation for a non-recoverable software failure. The abend is accompanied by a message written to the TMS:Engine log, which explains the reason for the abend. These abends are generally caused by storage exhaustion or storage overlays and cannot be retried. This abend can also be forced by the SHUTDOWN ABEND operator command. TMS:Engine terminates after a system dump is taken. |
TMS:Engine can generate the following snap dumps.
| Code | Description |
|---|---|
| 10 | An abend has occurred in TMS:Engine and the scheduled abend is intercepted by the ESTAE exit routine. All resident TMS:Engine load modules and various TMS:Engine control blocks and tables are dumped. Message KLVER001 is also issued, and gives the reason for the abend. |
| 11 | An abend has occurred in TMS:Engine and the scheduled abend is intercepted by the ESTAE exit routine. For each TMS:Engine subtask, the contents of the JPA, control blocks, queue control blocks, error control blocks, data management information, and I/O control areas are dumped. Message KLVER001 is also issued, and gives the reason for the abend. |
| 99 | An TMS:Engine application has requested a snap dump. Message KLVER001 is also issued, and identifies who requested the snap. |