PH60834: TRANSACTION HANGS AND CAN NOT BE PURGED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• After the following sequence of events, a transaction is left
  hung and it can not be purged:
  
  1) A java application program  uses JCICS to invoke a Cobol
  program.
  
  2) The cobol program does SQL calls
  3) The cobol program gets any type of transaction abend
  
  4) The cobol program does not Handle the transaction abend.
  This causes the transaction abend to percolate back to the java
  program.
  
  Following that sequence, the L8 TCB on which the calls to Db2
  were made is incorrectly left Associated with the Db2 thread.
  Also, in the java environment on the T8 TCB, as DFHTFP is being
  invoked as part of processing the abend, there is an attempt to
  Dissociate the T8 TCB from the thread.  This fails with an
  abend04E as the T8 TCB has never been involved with calling Db2.
  
  
  After this, the transaction is suspended and can't be purged.
  The abend04E is externalized with a message like this:
  
  CEE3250C The system or user abend S04E R=NULL   was issued.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Java transaction may be left hung and   *
  *                      unable to be purged.                    *
  ****************************************************************
  A transaction can hang when a Java program which will be running
  on a T8 TCB links to another program (such as COBOL) running on
  a different TCB and that program does a Db2 call.
  CICS switches to an L8 TCB and ASSOCIATES a Db2 thread.
  This program takes an abend which is not handled and the abend
  is percolated back up the stack and CICS switches back to the T8
  TCB.
  CICS now tries to DISSOCIATE the Db2 thread but this fails with
  a 04E and x'00F31104' because Db2 knows nothing about the T8
  TCB.
  The transaction is then suspended and cannot be purged.
  

Problem conclusion

• CICS has been changed to DISSOCIATE a Db2 thread from the active
  task before returning to an application's T8 TCB.
  

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:

  UI97937 UI97938

Modules/Macros

• DFHEPC   DFHMEPAE
  

Fix information

• Fixed component name

  CICS TS Z/OS V6

• Fixed component ID

  5655YA100

Applicable component levels

• R400 PSY UI97938

     UP24/08/09 P F408 ¢

• R500 PSY UI97937

     UP24/08/08 P F408 ¢

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.