PH30124: DB2 DDF THREAD ABEND 0C4-00000011 DSNLILLM.DSNLQACT+0EE8

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Abend 0C4-00000011 from DSNLILLM.DSNLQACT+0EE8 when TCPIP
  drop commands where used for a DDF thread that was stuck in an
  IOCTL call in TCPIP.
  
  In the reported V11 case, the DISC-NC thread was using SSL with
  handshake timeout of zero causing the thread to be unresponsive
  in TCPIP. Db2 cancel threads commands would not clear the
  thread from Db2, therefore the documented TCPIP
  drop commands were used to free the thread.
  
  LOGREC may show a previous abend 0C4-038 from DSNLQACT+0948.
  
  
  The DB2 subsystem may abnormally terminate with reason code
  00E50702 following the abend 0C4 from DSNLQACT+0EE8.
  
  
  Additional keywords and symptoms:
  *********************************
  DB2DDF DDF ABEND0C4 0C4 S00C4
  DSNLQACT OFFSET0948 OFFSET0EE8
  DB2TCPIP DB2TERM ABTERM
  

Local fix

• no local workaround or fix
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Distributed Data Facility (DDF) users.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Abend 0C4-00000011 DSNLQACT+0EE8 may                         *
  * occur at a Db2 for z/OS server. This                         *
  * abend may further cause the                                  *
  * Db2 for z/OS to abnormally terminate                         *
  * with reason 00E50702.                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  Abend 0C4-00000011 DSNLQACT+0EE8 may occur at a Db2 for z/OS
  server. In this case, a Db2 pool thread's internal control
  block being referenced, the storage was unavailable because it
  was allocated from a previous instance of DDF. As a result, the
  reported abend 0C4 occured which then ultimately led to Db2
  abnormally terminating with reason 00E50702.
  

Problem conclusion

• Db2 for z/OS has been changed to detect and avoid using
  storage of internal control blocks that was allocated from a
  previous instance of DDF during Db2/DDF pool thread activation
  processing.
  

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:

  UI73700 UI73701

Modules/Macros

• DSNLQACT
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RB10 PSY UI73700

     UP21/02/09 P F102 ¢

• RC10 PSY UI73701

     UP21/02/09 P F102 ¢

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.