PH59523: DFHAC2236 TRANSACTION CSOL - ABEND ASOL IN PROGRAM DFHSOL

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• CSOL transaction abends with an ASOL in DFHSOL.
  The region in question regularly hits the
  configured MAXSOCKETS threshold.
  
  An auxtrace confirms that the abend happens because
  CSOL attempts to lock a SOCK_ALL token that no longer
  exists
  
  LM 0003 LMLM  ENTRY DELETE_LOCK                  196503E0
  LM 0004 LMLM  EXIT  DELETE_LOCK/OK
  LM 0004 LMLM  EXIT  DELETE_LOCK/OK
  LM 0003 LMLM  ENTRY DELETE_LOCK                  196503B0
  LM 0004 LMLM  EXIT  DELETE_LOCK/OK
  ...
  LM 0003 LMLM  ENTRY TEST_LOCK_OWNER              1962ED80
  LM 0004 LMLM  EXIT  TEST_LOCK_OWNER/OK
  SO 1007 SOMG  *EXC* AT_MAXSOCKETS         FAILED TO ADD A
                                            NEW SOCKET
  ...
  SO 0C03 SOLS  *EXC* RECOVERY_ENTERED      LISTEN,OK
  SO 0C02 SOLS   EXIT  LISTEN/DISASTER
  ...
  LM 0003 LMLM  ENTRY LOCK                  196503B0,EXCLUSIVE
  LM 0004 LMLM  EXIT  LOCK/EXCEPTION        LOCK_TOKEN_NOT_FOUND
  SO 0C03 SOLS  *EXC* RECOVERY_ENTERED      LISTEN,OK
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Message DFHAC2236 can be seen reporting *
  *                      an ASOL abend in DFHSOL. CICS trace     *
  *                      shows LOCK/EXCEPTION reason             *
  *                      LOCK_TOKEN_NOT_FOUND.                   *
  ****************************************************************
  Message DFHAC2236 reporting an ASOL abend in DFHSOL can be seen
  when an attempt is made to lock on a token that no longer
  exists. The CICS trace shows LOCK/EXCEPTION with reason
  LOCK_TOKEN_NOT_FOUND.
  
  This can occur when processing to close a socket interleaves
  with an asynchronous receive completing for this same socket.
  Processing to close the socket being held up (ie. waiting for a
  lock) can open a window in which allows an asynchronous receive
  to complete for this socket that is part way through closing.
  This places the socket on the asynchronous receive chain to be
  processed by CSOL.
  Close processing continues and closes the socket.
  CSOL then goes on to process the asynchronous receive for this
  socket that is on the asynchronous receive chain, this fails
  attempting to obtain a lock that has now been deleted.
  

Problem conclusion

• CICS has been changed to ensure that the asynchronous receive
  chain is checked for the socket being deleted/closed. If the
  socket is on the chain then it is removed.
  
  The CICS TS 6.1 IBM Documentation will be updated with the new
  SO 1008 trace entry.
  

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:

  UI96826

Modules/Macros

• DFHSOCK  DFHSOLS  DFHSOTRI
  

Fix information

• Fixed component name

  CICS TS Z/OS V6

• Fixed component ID

  5655YA100

Applicable component levels

• R400 PSY UI96826

     UP24/05/10 P F405

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.