PK53394: DFHAP0002 SEVERE ERROR (CODE X'3255') HAS OCCURRED IN DFHD2D2. NO LOT ERROR CODE AFTER DISSOCIATE SQL CALL ERROR X'00F30018'

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When the task goes through end-of-task processing, DFHD2D2 does
  a DISSOCIATE to DB2 on this thread.  This DISSOCIATE fails with
  00F30018 because the thread has been cancelled, but there is no
  error checking in issue_DB2_dissociate. It just clears the
  csb_tcb_address and assumes that DB2 has updated
  CSB_DISSOCIATE_TOKEN with a token.
  The next task that gets it and goes into DFHD2D2 and promptly
  gets the d2d2_invalid_tcb error because the lack of a token in
  csb_dissociate_token makes D2D2 think the task is associated
  After the DFHAP0002 dump, D2D2 returns back with a response of
  d2d2_invalid and reason d2d2_invalid_tcb.  But no LOT error code
  is set-up and no SQLCA error code is set-up.  DFHD2EX1 doesn't
  check d2d2_response, and seeing no LOT error code just returns
  back to the application as if the SQL call worked.  That is why
  there is no transaction abend or anything. No message nor any
  indication is returned back to notify there is a problem.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All.                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: A severe error (code X'3255') has       *
  *                      occurred in DFHD2D2.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A severe error (code X'3255') occurred in DFHD2D2 when an
  attempt is made to associate a CSUB that failed to dissociate
  when released earlier by another task.
  An exception trace entry is created, AP3255 INVALID_TCB.
  The CSUB trace shows that the earlier dissociate failed with
  00F30018.
  The syslog indicates that just before a DB2 thread had been
  cancelled and this would be the cause of the dissociate failing.
  Additional keywords
  3255 F318 d2d2_invalid_tcb DFHAP0002 msgDFHAP0002 AP0002
  issue_DB2_dissociate CSB_DISSOCIATE_TOKEN
  CANCEL THREAD
  

Problem conclusion

• DFHD2D2 has been amended. If a CSUB fails to dissociate
  then it will be freemained rather than being reused.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

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

  PK58580 UK33899 UK33900

Modules/Macros

•    DESD2D2  DFHD2D2
  

Fix information

• Fixed component name

  CICSTS V3 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R400 PSY UK33899

     UP08/02/23 P F802

• R500 PSY UK33900

     UP08/02/23 P F802

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.