Transaction Problems

Transaction problems stop users from running their work - the transaction will not start, starts but misbehaves, or gets killed partway. The transaction definition and the task's behavior tell you where to look.

Transaction will not start

• APCT - the program named in the transaction definition cannot be found or is disabled. Check the PROGRAM definition and DFHRPL.
• Transaction disabled - the TRANSACTION resource was disabled by an operator or by CICS after errors. Re-enable it once the cause is fixed.
• AEI1 (TRANSIDERR) - the TRANSID is unknown. Check spelling and the TRANSACTION definition.
• Security (AEY7 NOTAUTH) - the user lacks authority for the transaction. Fix the RACF permission, not the program.

Transaction starts but gets killed

• AICA runaway - the task loops past its runaway limit. Purge it and fix the loop.
• AKC3 purged - an operator or deadlock detection killed it. Confirm the reason before rerunning.
• AKCT timeout - the task waited too long for terminal input. Adjust the timeout or redesign as pseudo-conversational.
• MAXTASKS or TRANCLASS limits - the task waits for a slot. Check for hung tasks consuming the class.

Checking and fixing a transaction

• Inspect the transaction's state with the operator command, and re-enable a disabled transaction with:-
  CEMT SET TRANSACTION(ORDR) ENABLED
  CEMT INQUIRE TASK
• CEMT INQUIRE TASK shows every active task - look for old tasks with high CPU or long elapsed times.
• After fixing the cause, test the transaction yourself before telling users it is working again.