AL - Message origin abend control statements

This reference topic describes how to add, modify or delete a message origin abend record.

Adding and modifying a message origin abend record

The control statement format for adding and modifying a message origin abend record is:

AL <lterm>
   <lterm/type/code>
   <tpipe>
   <tpipe/type/code>
   <luname>
   <luname/type/code>

Example:

AL  LTERM001
AL  LTERM001/U/1000

When adding and modifying a message origin abend record, you can specify the following keyword parameters:

LTRM=

APPC=

OTMA=

Specifies the disposition of the message that caused the abend based upon the specified message origin.

DEFAULT: Specifies that IMS is to determine the disposition of the message that caused the abend based upon the specified message origin.
DISCARD: Specifies that IMS is to discard the input message that caused the abend based upon the specified message origin.
SUSPEND: Specifies that IMS is to put the input message that caused the abend in the suspend queue.
This option is not applicable to IFP regions; it is treated as DEFAULT by IMS.
REQUEUE: Specifies that IMS is to requeue the input message that caused the specified abend.
This option is not applicable to IFP regions; it is treated as DEFAULT by IMS.

LTRMDEST=

APPCDEST=

OTMADEST=

Specifies the 1- to 8-character transaction name where IMS is to queue the input message that caused the abend.

LTRMSUPP=

APPCSUPP=

OTMASUPP=

Specifies whether message DFS555I is to be suppressed from the device where the message that caused the abend originated.

Y: Suppress message DFS555I from being returned to the device where the input message that caused the abend originated.
N: Allow message DFS555I to be sent to the device where the input message that caused the abend originated.

LTRMWTO=

APPCWTO=

OTMAWTO=

Specifies whether WTO IZT9201I is issued when message DFS555I is suppressed for an abend.

Y: Issue WTO IZT9201I when message DFS555I is suppressed.
N: Do not issue WTO IZT9201I when message DFS555I is suppressed.

LTRMTRXPSB=

APPCTRXPSB=

OTMATRXPSB=

Specifies the state of the IMS TRAN/PSB following an application program abend. The state can be specified based upon the message point of origin (LTRM, APPC, or OTMA).

Restriction: If you specify the REQUEUE option, only TRAN/PSB options PSTOP and STOP behave as defined in this topic. The other TRAN/PSB options cause the transaction to enter a USTOP state and the PSB is not stopped.　

Recommendation: Certain TRAN/PSB options can produce undesirable results, so test the results of your options before deploying your user exit into your production environment.

NOUTOP: Specifies that the transaction and the associated program are not put into USTOP and STOPPED state, respectively.
PSTOP: Specifies that the transaction is put into a PSTOPPED state.
Restriction: If this option is specified and a transaction that resulted in an abend was defined as Fast-Path exclusive, the specified option will be ignored and the transaction status will be set to STOP. This behavior is consistent with the way IMS handles a PSTOP command issued against a Fast-Path exclusive transaction. If you do not want to stop the transaction and the associated program, the recommended value for the TRAN/PSB option is NOUSTOP.
PURGE: Specifies that the transaction is put through the PURGE process.
STOP: Specifies that the transaction is put into a STOPPED state.
START: Specifies that the transaction is put into a STARTED state.

Deleting a message origin abend record

The control statement format for deleting a message origin abend record is:

AL <lterm>  DELETE
   <tpipe>
   <luname>

Example:

AL  LTERM001  DELETE
AL  LTERM001/U/1000  DELETE