Question & Answer
Question
Why does CICS Transaction Server for z/OS (CICS TS) stop responding after I cancel a CICS transaction that uses the WebSphere Optimized Local Adapter (WOLA) adapter? This transaction makes DB2 requests. The transaction stays hanging on the WOLA true BBOATRUE and blocks the QR TCB. No further transactions are dispatched.
CICS shows abend 378 reason 14. A cancel of the CICS address space did not work so CICS had to be forced down.
I also found the following message in the syslog: +IDI0002I Module,BBOATRUE,,CSECT BBOATRUE, offset X'D76': CICS abend AKEH
Answer
In this case, OMEGAMON was used to kill the CICS task and this led to an abend 04E. If the DB2 CANCEL THREAD command had been used the problem would not have occurred. See Purging CICS DB2 transactions in the CICS TS documentation tfor more details about ensuring that DB2 requests are not cancelled during "must complete" activity.
Here's what I saw in the system dump:
---+----1----+----2----+----3----+----4----+----5----+----6----+----7--
CICS Task Detail
Command ===>
SYSTEM=XXXCICS CODE=KERNDUMP ID=0/0000 SY2 2015/04/13 11:51:24
Tran Initial Facility
KE_NUM Status Number Tran ID Program Id In Error Userid
0076 ***Running** 11943 SEF0 S17790 6BE683A0 USRCICS
TACB details current abend code AD3K.
Attach Date/Time. .: 2015/04/13 09:15:18 Current program . .: BBOATRUE
It looks like task 11943 sent a request to DB2. This request suffered an abend 04E, internal DB2 error and became stuck. The operator recognized that something was wrong with this task, and purged it. CICS detected that the purge occurred in a critical two phase commit state (abort request to DB2, issued during the second phase of syncpoint, failed). This was the route cause of the abend 04E.
Product Synonym
CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
04 March 2016
UID
dwa1256196