PH67640: THERE IS NO MESSAGE WRITTEN TO CONSOLE WHEN A MID-TRANSACTION ASSOCIATE FAILS WITH DB2 REASON X'00F31100'.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• It is possible that during the course of a transaction that does
  SQL calls, CICS will call Db2 to momentarily Dissociate the
  transaction's TCB from its Db2 thread, and then later call Db2
  to re- Associate the transaction's TCB to its Db2 thread.   This
  happens when a transaction has programs running on different
  TCBs all making SQL calls.   For instance, the transaction could
  have a java program running on a T8 TCB doing JDBC calls.   And
  it could also have an OPENAPI program running on an L8 TCB.  And
  it could also have a Quasirent program running on the QR TCB.
  Dissociate / Associate allows a transaction's  different TCBs to
  use the same Db2 thread.
  
  If a mid-transaction Associate fails, the transaction is no
  longer able to work with that thread.  This is a problem.  We
  have seen a mid-transaction Associate fail with Db2 reason code
  x'00F31100'.  We are working to understand and fix the cause of
  this.  The Associate failure results in the transaction abending
  with abendAD3L.  But there is no CICS message written to console
  to externalize this error.
  
  This APAR is to change CICS to issue a message to the console in
  this situation.  This message will make it easier to get a dump
  of CICS and Db2 at time of this error.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: A CICS Db2 transaction receives a Db2   *
  *                      feedback code of '00F31100'x on an      *
  *                      ASSOCIATE call. The thread left active  *
  *                      in Db2.                                 *
  ****************************************************************
  A CICS Db2 transaction has used an open ( L8 ) TCB, then has
  briefly switched back to the QR TCB. This transaction is now
  switching back to the open TCB and is issuing an ASSOCIATE, to
  tie the CICS CSUB to a Db2 thread. The ASSOCIATE call is getting
  a '00F31100'x feedback code from Db2 which results in CICS
  issuing an abend AD3L, but nothing appears on the SYSLOG to warn
  the operators or any automation that the Db2 thread could be
  left hanging holding onto Db2 resources.
  

Problem conclusion

• DFHD2EX1 has been changed so that when a feedback of '00F31100'x
  is returned from Db2 on an ASSOCIATE call, then before it issues
  the abend AD3L, it will issue a severe error with a new error
  code (x'31A9') and take a system dump.
  

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:

  UO05188 UO05189 UO05190

Modules/Macros

• DFHD2CC  DFHD2CM1 DFHD2CO  DFHD2D2  DFHD2EX1 DFHD2EX2 DFHD2EX3
  DFHD2IN1 DFHD2RL  DFHD2RP  DFHD2ST  DFHD2STP DFHD2STR DFHD2TM
  DFHD2TR1 DFHD2TRI DFHMEAPE
  

Fix information

• Fixed component name

  CICS TS Z/OS V6

• Fixed component ID

  5655YA100

Applicable component levels

• R400 PSY UO05190

     UP25/10/03 P F510

• R500 PSY UO05189

     UP25/10/03 P F510

• R600 PSY UO05188

     UP25/10/03 P F510

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.