Troubleshooting
Problem
You have a DB2 transaction failing in your CICS Transaction for z/OS (CICS TS) region with an abend AD2U ( abendAD2U ). You are trying to find the reason code in the CICS transaction dump so you can determine why the create thread failed.
Cause
An abend AD2U means an attempt to create a DB2 thread by the TCB servicing the DB2 request failed. Note that the AD2U does not always mean the transaction abnormally terminated with an AD2U, but that an AD2U dump was taken. This depends on the setting of THREADERROR in the DB2CONN definition .
Resolving The Problem
Examine the AD2U dump to determine what SQLCODE and reason code you are receiving. You can locate the reason code by entering a find on the term SQLCA in the transaction dump. You should find it in the eyecatcher area of a piece of task storage. For example, you might see 00F30034 within the SQLCA area.
Reason code 00F30034 is an Authorization failure. If THREADERROR(N906D) is specified, an error code is passed back to the application. SQLCODE -922 indicates an Authorization Failure. Subsequent requests from the application would receive an SQLCODE -906.
Following is a more detailed explanation of 00F30034 taken from the DB2 Messages and Codes manual:
Explanation
The authorization ID associated with this connection is not authorized to use the specified plan name or the specified plan name does not exist.
System action
The request to allocate a plan to the authorization ID is denied.
User response
Verify that the correct plan name was specified. If this plan exists, then request execution authority to the plan from either the owner of the plan or from another person given authority to grant execution authority to the plan.
Reason code 00F30034 is an Authorization failure. If THREADERROR(N906D) is specified, an error code is passed back to the application. SQLCODE -922 indicates an Authorization Failure. Subsequent requests from the application would receive an SQLCODE -906.
Following is a more detailed explanation of 00F30034 taken from the DB2 Messages and Codes manual:
Explanation
The authorization ID associated with this connection is not authorized to use the specified plan name or the specified plan name does not exist.
System action
The request to allocate a plan to the authorization ID is denied.
User response
Verify that the correct plan name was specified. If this plan exists, then request execution authority to the plan from either the owner of the plan or from another person given authority to grant execution authority to the plan.
[{"Type":"MASTER","Line of Business":{"code":"LOB70","label":"Z TPS"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"ARM Category":[{"code":"a8m0z00000007dVAAQ","label":"Data services and Data tables-\u003EDB2"}],"ARM Case Number":"","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"5.4.0;5.5.0;5.6.0;6.1.0;6.2.0;6.3.0"}]
Product Synonym
CICS/TS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
05 January 2026
UID
swg21025760