PH68909: CICS GETS DFHSO0002 (CODE X'02A0') CONDITIONS AFTER REACHING MAXSOCKETS LIMIT 25/11/11 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A slow down of outbound SSL workload was leading to a MAXSOCKETS
  limit reached condition (message DFHSO0126) in a CICS region.
  Subsequently, the following errors are logged:
  
  DFHSO0002 A severe error (code X'02A0') has occurred in module
  DFHSOCK.
  
  The trace showed a CHANGE_MODE error which was issued when an
  attempt is made to switch back onto the callers S8 TCB. This
  fails because the TCB is no longer available (because the
  association was lost as part of processing the closure of the
  reclaimed socket).
  
  Trace entry:
  *EXC* CHANGE_MODE_ERROR FUNCTION(CREATE) TRANSPORT(TCP)
  QUEUE_TIMEOUT(NO) TIMEOUT_VALUE(1) PROTOCOL(HTTP) SWITCH_TCB(NO)
  
  
  
  This is a variation of the issue addressed by APAR PH42541
  which presents itself when MAXSOCKETS is reached and there is an
  eligible socket in the pool to be closed and reclaimed for the
  current request.
  

Local fix

• Make sure that the MAXSOCKETS limit isn't reached.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users with UI78887, UI78888,        *
  *                 UI78889, UI80124, UI80125, UI90656, UI90657, *
  *                 UI90658, UI93696, UI93697, UI96412, UI96411, *
  *                 UI96262.                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Message DFHSO0002 can be seen as the    *
  *                      result of a CHANGE_MODE error when a    *
  *                      region is at MAXSOCKETS.                *
  ****************************************************************
  When a CICS region is at MAXSOCKETS and an attempt is made to
  reclaim a socket to be used for a secure inbound HTTP request,
  a change_mode error can be seen when the socket to be reclaimed
  has been used for secure/SSL work. This is because the task
  has lost association to its S8 TCB as CICS incorrectly assumes
  the S8 TCB is being used temporarily in order to close the
  secure socket being reclaimed.
  

Problem conclusion

• UI78887, UI78888, UI78889, UI80124, UI80125, UI90656, UI90657,
  UI90658, UI93696, UI93697, UI96412, UI96411, UI96262
  
  CICS now caters for the situation where a task already owns an
  S8 TCB, and the switch to an S8 in order to close a secure
  socket for re-use is not temporary.
  

Temporary fix

Comments

• ×**** PE26/03/16 FIX IN ERROR. SEE APAR PH70536  FOR DESCRIPTION
  

APAR Information

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

  PH64812

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

  UO05947 UO05948 UO05949 UO05950

Modules/Macros

• DFHLEPTS DFHMESOC DFHMESOE DFHMESOK DFHSOAD  DFHSOCK  DFHSODM
  DFHSODS  DFHSODUF DFHSOGH@ DFHSOHN  DFHSOIS  DFHSOL   DFHSOLI
  DFHSOLS  DFHSOLX  DFHSOLX6 DFHSOM01 DFHSOM02 DFHSOM03 DFHSONT
  DFHSOPL  DFHSOPLT DFHSORD  DFHSORL  DFHSORM  DFHSOS00 DFHSOS01
  DFHSOS02 DFHSOS03 DFHSOS04 DFHSOS05 DFHSOS06 DFHSOS07 DFHSOS08
  DFHSOS09 DFHSOS10 DFHSOS11 DFHSOS12 DFHSOS13 DFHSOS14 DFHSOS15
  DFHSOS16 DFHSOS17 DFHSOS18 DFHSOS19 DFHSOS20 DFHSOS21 DFHSOS22
  DFHSOS23 DFHSOSE  DFHSOSES DFHSOSK  DFHSOSM  DFHSOST  DFHSOTB
  DFHSOTI  DFHSOTRI DFHSOUE  DFHSOXM  DFHWBCL  DFHWBSC  DFHWBUR
  DFJ@H360
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R100 PSY UO05949

     UP25/11/29 P F511 {

• R10D PSY UO05950

     UP25/11/29 P F511 {

• R200 PSY UO05948

     UP25/11/27 P F511 {

• R300 PSY UO05947

     UP25/11/26 P F511 {

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.