Learn it on Mainframe Path. Do it with MainframeKit.Learn on Mainframe Path ▸
MainframeKit

AEI9

MAPFAIL condition not handledCICS ABEND

The task ended because a MAPFAIL condition was raised and the program had no RESP option or handler for it, so CICS issued abend AEI9.

MOST LIKELY

A command raised MAPFAIL and had no RESP option or NOHANDLE.

FIRST CHECK

Find the command that raised MAPFAIL from the dump or trace.

TRY IT ▸

Site search

What it means

AEIx abends come from the EXEC interface program (DFHEIP). Here CICS found an unhandled MAPFAIL condition: the command carried no RESP option and no HANDLE CONDITION covered it, so CICS ended the task and took a transaction dump.

The abend does not name the command that raised MAPFAIL. The dump and trace show it; see the MAPFAIL entry for the condition itself.

Typical causes

  • A command raised MAPFAIL and had no RESP option or NOHANDLE.
  • No HANDLE CONDITION for MAPFAIL was active when the command ran.

How to fix it

  1. Find the command that raised MAPFAIL from the dump or trace.
  2. Look at the EIB in the dump: function code (X'1B'), EIBRCODE (X'1D'), EIBRESP (X'4C') and EIBRESP2 (X'50') help show which command it was and why.
  3. Where you can, change the program so the MAPFAIL condition does not arise.
  4. Otherwise add RESP to the command and test the response, or set HANDLE CONDITION for MAPFAIL, and decide what the program does then.

Example

Illustrative only; names and values are invented.

DFHAC2236 10:40:05 APPL01 Transaction TRN1 abend AEI9 in program PROG01 term T001. Updates to local recoverable resources will be backed out.
EXEC CICS RECEIVE MAP('MAP1') MAPSET('MSET1') INTO(WS-MAP)   (no RESP) -> task ends with AEI9