MainframeKit

AEIP

INVREQ condition not handledCICS ABEND

A CICS command raised INVREQ (invalid request) and the program did not handle it, so CICS ended the task with AEIP.

MOST LIKELY

A command used with options that do not fit together or are not allowed in this context.

FIRST CHECK

Find which command failed and capture its RESP2 value (CEDF or a trace).

TRY IT ▸

MainframeKit assistant

What it means

AEIP is the abend you get when the INVREQ condition comes back and the program has no RESP option or handler for it.

INVREQ is broad. The RESP2 value of the failing command says exactly what was wrong, so look it up on that command's IBM page.

Typical causes

  • A command used with options that do not fit together or are not allowed in this context.
  • A browse command (for example READNEXT) issued when no valid browse is active for the task.
  • A command that is not allowed in the current environment, such as some commands in a DPL server program.
  • No RESP option on the command and no HANDLE CONDITION for INVREQ.

How to fix it

  1. Find which command failed and capture its RESP2 value (CEDF or a trace).
  2. Look up that RESP2 value on the IBM page for the command.
  3. Fix the options or the order of commands in the program.
  4. Add RESP to the command and test for DFHRESP(INVREQ) where it can happen.

Example

Illustrative only; names and values are invented.

DFHAC2236 12:05:33 APPL01 Transaction TRN1 abend AEIP in program PROG01 term T001. Updates to local recoverable resources will be backed out.