MainframeKit

AEIM

NOTFND condition not handledCICS ABEND

A CICS command raised the NOTFND condition and the program did not handle it, so CICS ended the task with AEIM.

MOST LIKELY

A command looked for something that does not exist and the program did not check the response.

FIRST CHECK

Find which command failed (the program offset, CEDF, or a trace).

TRY IT ▸

MainframeKit assistant

What it means

AEIM belongs to the AEIx group: abends that CICS raises when a command condition comes back and the program has no RESP option or handler for it. For AEIM the condition is NOTFND.

The fix is almost always in the program: test the response and decide what to do when the item is missing.

Typical causes

  • A command looked for something that does not exist and the program did not check the response.
  • No RESP option on the command and no HANDLE CONDITION for NOTFND.
  • Wrong key or name passed to the command.
  • Bad setup data, such as an unknown code page on a WEB RECEIVE (an IBM-documented case).

How to fix it

  1. Find which command failed (the program offset, CEDF, or a trace).
  2. Add RESP to the command and test for DFHRESP(NOTFND).
  3. Check the key or name the program built before the call.
  4. Correct any wrong definitions or setup values the command depends on.

Example

Illustrative only; names and values are invented.

DFHAC2236 12:00:01 APPL01 Transaction TRN1 abend AEIM in program PROG01 term T001. Updates to local recoverable resources will be backed out.