Friday, August 27, 2010

AD2R abend after upgrading to DB2 9.1 when running CICS TS 4.1

Thought I might as well mention this flash (alert). I'm just quoting the alert you can find over here.

Abstract
After you upgrade to DB2 V9.1, transactions in your CICS Transaction Server for z/OS (CICS TS) V4.1 region start to fail with an abend AD2R ( abendAD2R ). The CICS exception trace indicates that the DB2 thread abended with an 0C4 Reason 0003EB60 ( RSN3EB60 ). Your CICS TS V3.2 regions are not affected by the change.

Content
DB2 V9.1 APAR PM20489 has been opened to address an abend 0C4 in DSNMLTOK at offset 4 and will fix this problem. If possible, you should wait until the PTF for this APAR is available before upgrading to DB2 V9.1 if running CICS TS V4.1.

As soon as PM20489 closes and the PTF becomes available, this document will be updated and included in the My Notifications email for CICS Transaction Server and on Twitter for IBM_CICS. You can also track specific CICS APARs if you would like to be notified when the PTF for this APAR becomes available.

Diagnosing the Problem
Following is the CICS exception trace entry:
AP 319D D2EX1 *EXC* THREAD TCB HAS ABENDED WITH ABEND
000000C4,REASON,0003EB60

The reason code is not a valid DB2 reason code.

Prior to this, within the CICS trace entries, you will see:
AP 3180 D2EX1 ENTRY APPLICATION REQUEST EXEC SQL UNKNOWN

If a system dump is captured for the abend AD2R, the kernel error table will show an abend0C4 followed by transaction abend percolates:
ERROR TYPE ERR_CODE MODULE OFFSET
PROGRAM_CHECK 0C4/AKEA UNKNOWN UNKNOWN
TRAN_ABEND_PERCOLATE ---/AD2R DFHPCP 00000604
TRAN_ABEND_PERCOLATE ---/AD2R DFHD2EX1 00002CDC
TRAN_ABEND_PERCOLATE ---/AD2R DFHERM 0000137E

The PSW of this abend0C4-38 points into module DSNLMTOK +4 to a StoreMultiple (EBEC D008 0024 STMG R14,R12,8(R13) ).

No comments: