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

AEIN

DUPREC condition not handledCICS ABEND

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

MOST LIKELY

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

FIRST CHECK

Find the command that raised DUPREC 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 DUPREC 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 DUPREC. See the DUPREC entry for what the condition means; the dump and trace show the command.

Typical causes

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

How to fix it

  1. Find the command that raised DUPREC 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 DUPREC condition does not arise.
  4. Otherwise add RESP to the command and test the response, or set HANDLE CONDITION for DUPREC, and decide what the program does then.

Example

Illustrative only; names and values are invented.

EXEC CICS WRITE FILE('CUSTFIL') FROM(WS-REC) RIDFLD(WS-KEY)   (no RESP; key already on file, illustrative) -> task ends with AEIN