S/MF
StackMF Knowledge Base • z/OS
ABENDS & Diagnostics 10 min read 2026-09-27

Resolving CICS AEYH ABEND: CICS-DB2 Attachment Facility Disconnects and Thread Pool Starvation

A
Reviewed by Anshu
Chief Technology Architect & Mainframe Systems SME
Verified Production Runbook
Google AI Overview & Featured Snippet Quick Answer

Quick Diagnostic Summary: What Causes Resolving CICS AEYH ABEND: CICS-DB2 Attachment Facility Disconnects and Thread Pool Starvation?

CICS ABEND AEYH occurs when an application issues an EXEC SQL statement but the CICS-DB2 attachment facility is inactive or when all pool threads are exhausted. Learn how to diagnose DB2CONN and DB2ENTRY resources and tune thread limits.

1 Incident Symptoms: What Triggers Resolving CICS AEYH ABEND: CICS-DB2 Attachment Facility Disconnects and Thread Pool Starvation?

Every CICS transaction attempting to access DB2 tables crashes simultaneously:

text
DFHAC2206 09:12:04 CICS01 TRANSACTION TXIN ABENDED AEYH IN PROGRAM CUSTINQ.
          THE CICS DB2 ATTACHMENT FACILITY IS NOT CONNECTED.

Online customer portals return HTTP 500 errors across all digital banking channels.

2 Technical Root Cause & Architecture Mechanics

The CICS-to-DB2 interface is managed by the CICS DB2 Attachment Facility:

1. DB2 Subsystem Disconnected: DB2 was recycled or crashed, or the attachment was disconnected via DSNC DISCONNECT.

2. Thread Starvation: The transaction's DB2ENTRY reached its THREADLIMIT, and THREADWAIT=NO was specified, forcing an immediate AEYH rejection.

3. Plan Authorization Failure: The CICS user lacks EXECUTE authority on the DB2 application plan.

3 Step-by-Step Diagnostic & Code Resolution

# 1. Inquire and Start the CICS-DB2 Connection

From the CICS master terminal:

text
CEMT INQUIRE DB2CONN

If STATUS: DISCONNECTED, issue:

text
CEMT SET DB2CONN CONNECTED

Or via the DB2 operator interface:

text
DSNC STRT DB2P

# 2. Configure DB2ENTRY Thread Overflow

In the CICS System Definition (CSD), configure thread pool overflow so transactions wait or overflow to general pool threads rather than abending:

text
CEDA DEFINE DB2ENTRY(TXINENT) GROUP(BANKGRP)
     TRANSID(TXIN)
     PLAN(PLNBANK1)
     THREADLIMIT(25)
     THREADWAIT(YES)
  • THREADWAIT(YES): If all 25 threads are active, incoming requests queue smoothly instead of crashing with AEYH.

# 3. Handle AEYH in Application Code

Add error handling around SQL calls:

cobol
EXEC SQL
           SELECT CUST_NAME INTO :WS-CUST-NAME
           FROM CUSTOMER WHERE CUST_ID = :WS-CUST-ID
       END-EXEC.

       IF SQLCODE = -922 OR SQLCODE = -924
           MOVE 'DB2 Subsystem Offline - Try Again Later'
             TO WS-USER-MESSAGE
           EXEC CICS RETURN END-EXEC
       END-IF.

Diagnostic Reference Matrix

Attribute Specification
Target Subsystem IBM z/OS 2.4 - 3.1 • ABENDS & Diagnostics
Error Signature CICS, DB2, ABEND AEYH
Resolution SLA < 15 Minutes via Verified StackMF Runbook
Technical Reviewer Anshu, Chief Technology Architect • StackMF Architecture Pod

Architectural Prevention & Performance Tuning Checklist

? Frequently Asked Questions

What is the root cause of Resolving CICS AEYH ABEND: CICS-DB2 Attachment Facility Disconnects and Thread Pool Starvation? ↓
The CICS-to-DB2 interface is managed by the CICS DB2 Attachment Facility:.
How do you resolve Resolving CICS AEYH ABEND: CICS-DB2 Attachment Facility Disconnects and Thread Pool Starvation in production? ↓
CICS ABEND AEYH occurs when an application issues an EXEC SQL statement but the CICS-DB2 attachment facility is inactive or when all pool threads are exhausted. Learn how to diagnose DB2CONN and DB2ENTRY resources and tune thread limits.
How can teams prevent Resolving CICS AEYH ABEND: CICS-DB2 Attachment Facility Disconnects and Thread Pool Starvation in enterprise pipelines? ↓
Configure automatic reconnection in `DB2CONN` (`STANDBYMODE=RECONNECT`).

Recommended Technical Runbooks

Authoritative Reference Documentation

Official IBM manuals, Redbooks, and vendor technical advisories:

Related Topics: CICSDB2ABEND AEYHAttachment FacilityThreadsDB2CONN
Diagnostic Runbook Notice & Nominative Fair Use Disclaimer

This diagnostic runbook is published by StackMF Technologies LLP for educational and architectural reference only. All code snippets, JCL, and procedures are provided "AS IS" without warranty of any kind. Always test changes thoroughly in non-production sysplex environments prior to production rollout.

IBM, z/OS, CICS, Db2, IMS, RACF, and IDz are registered trademarks of International Business Machines Corporation. Broadcom, CA-7, and Endevor are trademarks of Broadcom Inc. All other trademarks belong to their respective owners and are referenced under the Nominative Fair Use Doctrine (US Lanham Act 15 U.S.C. ยง 1125 / Section 30 of the Indian Trade Marks Act, 1999) solely for technology compatibility and diagnostic identification. StackMF Technologies LLP is an independent consulting entity not affiliated with or endorsed by these vendors. View Full Legal & IP Policy →

Enterprise Advisory

Struggling with Critical Mainframe Incidents or Vendor Renewal Pressure?

StackMF deploys certified Senior Mainframe Engineers fluent in both z/OS legacy internals (COBOL, DB2, CICS, VSAM, CA-7, Endevor) and modern cloud stacks (React, Kafka, AWS, Git). Onboard dedicated pods in 48 hours or cut Broadcom licensing by 60%.