MainframeKit

ASRB

Operating system abendCICS ABEND

The task ended because a z/OS operating system abend occurred while it was running, and CICS recovered the region by ending only that task.

MOST LIKELY

The program or a routine it called issued or triggered a z/OS system abend.

FIRST CHECK

Read the CICS messages logged with the abend to get the original system abend code and program.

TRY IT ▸

MainframeKit assistant

What it means

An operating system abend (not a program check) happened under the task. CICS's system recovery program took control and ended the task with ASRB so the rest of the region could carry on.

Like ASRA, the real reason is the underlying system abend code. Look for it in the messages and dump CICS produces around the failure.

Typical causes

  • The program or a routine it called issued or triggered a z/OS system abend.
  • A non-CICS service called from the program failed with a system abend.
  • A problem inside CICS code itself (CICS takes a dump before your HANDLE ABEND exit runs in that case).

How to fix it

  1. Read the CICS messages logged with the abend to get the original system abend code and program.
  2. Look up that system abend code to learn the real cause.
  3. Use the transaction dump, if one was taken, to see where the task was.
  4. If the failure points into CICS code rather than your own, collect the dump and contact IBM support.

Example

Illustrative only; names and values are invented.

DFHAC2236 10:20:44 APPL01 Transaction TRN1 abend ASRB in program PROG01 term T001. Updates to local recoverable resources will be backed out.