ABEND

Terminate a task abnormally.

Read syntax diagramSkip visual syntax diagram
ABEND

>>-ABEND--+--------------+--+--------+--+--------+-------------><
          '-ABCODE(name)-'  '-CANCEL-'  '-NODUMP-'   

This command is threadsafe.

Description

ABEND terminates a task abnormally.

The main storage associated with the terminated task is released; optionally, a transaction dump of this storage can be obtained.

Options

ABCODE(name)
specifies that main storage related to the task that is being terminated is to be dumped. The ABCODE is used as a transaction dumpcode to identify the dump. ABCODE follows the format rules for DUMPCODE. The EXEC CICS DUMP TRANSACTION command gives the format rules that apply to DUMPCODE, if these rules are not followed, ABEND does not produce a dump.

Do not start the name with the letter A, because this is reserved for CICS® itself.

Note: If ABCODE is not used, the effect is the same as NODUMP.
CANCEL
specifies that exits established by HANDLE ABEND commands are to be ignored. An ABEND CANCEL command cancels all exits at any level in the task (and terminates the task abnormally). If the PL/I STAE execution-time option has been specified, an abnormal termination exit is established by PL/I. This exit is revoked by the CANCEL option.
NODUMP
allows you to request an abend without causing a dump to be taken. Start of change For programs link-edited using the Language Environment® SCEELKED library, when NODUMP is specified, a dump is never taken, regardless of any setting in the transaction dump table. For programs not link-edited with Language Environment,End of change if the transaction dump table already has an entry for the abend code, or if the abend is in Language Environment run-unit initialization or termination, the NODUMP option is ignored.

Examples

The following example shows how to terminate a task abnormally:
EXEC CICS ABEND ABCODE('BCDE')