PH21486: CONA GET AEXY ABEND DURING CICS-DB2 DISCONNECT 20/02/28 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This problem is being caused because at some point in the past
  the CONA task was used to purge a task, and that task just
  happened to be in DB2 at the time. To satisfy the SET TASK
  PURGE request, CONA had to issued a DSNC CANCEL THREAD command.
  This caused the CONA task to acquire some lifetime affiliation
  to the DB2CONN. This meant that when the FORCE command was
  issued against the DB2CONNN, COIE had to purge the CONA task
  before it could succeed.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users with PI98569, PH03569, PH15982     *
  *                 or PH18162 applied.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: The CONA suffers an AEXY abend as part  *
  *                      of CICS DB2 disconnect processing       *
  ****************************************************************
  CICS will not disconnect from DB2 because the CONA transaction
  is still connected to Db2 after a purge / forcepurge has been
  issued against a user task from CPSM.  This results in the CONA
  transaction being purged.
  Kwds: CONL
  

Problem conclusion

• UI57402 UI57403 UI57406 UI57407 UI59006 UI59007 UI59008 UI59009
  UI65858 UI65965 UI66003 UI66023
  
  Code has been added to ensure that the CONA transaction no
  longer has a connection to Db2 after the purge / forcepurge has
  completed.
  
  
  The CICS Transaction Server Version 5 Release 2,  Version 5
  Release 3, Version 5 Release 4 and Version 5 Release 5, CICS
  Messages manual will be updated as follows.
  
  In Chapter 2. DFHAPnnnn messages - a new message will be added
  immediately after the description of message DFHAP0604. This new
  message description will read as below.
  
  DFHAP0605  date time applid Db2 Cancel Thread issued for thread
             threadtoken  whilst processing purge or forcepurge
             of transaction number trannum transaction id tranid.
  
  
  Explanation:  CICS has issued a cancel thread request to
  Db2 because it has detected that the transaction it is about
  to purge or forcepurge has a thread active in Db2.
  
  System Action:  CICS continues with the purge or forcepurge
  of the transaction.
  
  User Response:  None.
  
  Destination:  Console
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI68415 UI68416 UI68417 UI68418

Modules/Macros

• DFHD2D2  DFHD2D2T DFHD2EX1 DFHD2TRI DFHEIQSK DFHERM   DFHMEAPC
  DFHMEAPE DFHMEAPK DFHTCA
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R000 PSY UI68416

     UP20/03/19 P F003 {

• R100 PSY UI68417

     UP20/03/18 P F003 {

• R200 PSY UI68418

     UP20/03/17 P F003 {

• R900 PSY UI68415

     UP20/03/19 P F003 {

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.