A fix is available
APAR status
Closed as program error.
Error description
The problem only occurs when running with Transaction Isolation and pooled DB2 threads. The CICS trace shows several SQL FETCH requests followed by a SYNCPOINT which results in a ROLLBACK. Several other ROLLBACKs occur until eventually the program terminates and we get the exception trace and abend because the DB2 thread is not assicated with the TCB. Change team update ; In the problem case, DFHERM is called on an L8 TCB, then the first true causes it to swap to QR. It loops round to drive the second true (DFHD2EX1) which should be called on an L8, but before changing mode back to L8 it tests the mode the DFHERM was called on and incorrectly decides that no CHANGE_MODE is required. Hence it calls DFHD2EX1 whilst running on QR and the call to DB2 to terminate the thread fails with 00F30018 because it's on the wrong TCB.
Local fix
Turn OFF Transaction Isolation
Problem summary
**************************************************************** * USERS AFFECTED: All * **************************************************************** * PROBLEM DESCRIPTION: Abend AD3F when using DB2. * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem occurs when DFHERM is called on an open TCB for end-of-task but then drives multiple TRUEs, one of which runs on QR. The final TRUE should run on an open TCB but is incorrectly called on QR. DFHERM is testing the wrong field when determining whether to switch back to an open TCB so it wrongly believes that it is already on an open TCB and fails to switch. This results the reported abendAD3F when using DB2 because DFHD2EX1 ( the CICS-DB2 Task Related User Exit) attempts to terminate the thread on the wrong TCB. Additional keywords: DSNCSQL 00F30018
Problem conclusion
DFHERM has been changed to replace the test of DFHERM's initial mode with a test of the current TCB when determining whether to change mode before calling a TRUE.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM93913
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / Pervasive
Submitted date
2013-07-26
Closed date
2013-11-05
Last modified date
2015-03-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI12273
Modules/Macros
DFHERM
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R800 PSY UI12273
UP13/11/15 P F311
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
05 March 2015