MainframeKit

AEI1

TRANSIDERR condition not handledCICS ABEND

A START (or similar command) raised TRANSIDERR because the transaction ID is unknown or cannot be routed, and the program did not handle it.

MOST LIKELY

The transaction ID is misspelt or the field holding it has the wrong value.

FIRST CHECK

Note the transaction ID the program passed and check it with CEMT I TRANSACTION(xxxx).

TRY IT ▸

MainframeKit assistant

What it means

The command named a transaction that CICS could not find or could not send to the right region. The program did not check RESP, so CICS ended the task with AEI1.

For START, TRANSIDERR means the transaction is not defined to this region, or a dynamic transaction's REMOTESYSTEM does not match where routing sent it.

Typical causes

  • The transaction ID is misspelt or the field holding it has the wrong value.
  • The transaction is installed in another region but not in the one running the START.
  • A remote transaction is defined DYNAMIC(YES) with a REMOTESYSTEM that conflicts with the routing decision.
  • A region upgrade changed how a dynamic remote START is handled; IBM has fixed such cases by APAR.

How to fix it

  1. Note the transaction ID the program passed and check it with CEMT I TRANSACTION(xxxx).
  2. Install the transaction definition in this region if it is missing.
  3. For remote transactions, check REMOTESYSTEM, DYNAMIC and the routing program with the CICS systems team.
  4. If it started after an upgrade, search IBM support for APARs on START and TRANSIDERR for your release.
  5. Add RESP to the START so the program can report a missing transaction.