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

AEID

EOF condition not handledCICS ABEND

The task ended because an EOF condition was raised and the program did not handle it, so CICS used abend AEID.

MOST LIKELY

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

FIRST CHECK

Find the command that raised EOF 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 EOF 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 EOF. EOF is a separate condition from ENDFILE, which ends a browse and gives AEIT instead, so AEID is not the browse abend. The dump and trace show the command.

Typical causes

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

How to fix it

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

Example

Illustrative only; names and values are invented.

DFHAC2236 11:02:44 APPL01 Transaction TRN2 abend AEID in program PROG02 term T003. Updates to local recoverable resources will be backed out.