PM94245: ISSB SESSIONS NOT FREED AFTER SOCKET CLOSE BY EXTERNAL ERROR

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You are running a stress workload to cross instance applications
  with RTIMOUT and MONITOR timeouts set to purge transactions that
  take excessive time to complete.  When one region is slowed, the
  processing is affected on the other regions, as multiple tasks
  are delayed and eventually purged.  ISSBs are not freed.
  .
  Upon encountering an error (possibly external to CICS) a SOCKET
  closes.  When 1 of the 4 sockets used by the IPCONN has been
  closed (not by an IPCONN release initiated by CICS), there is a
  mechanism to clean up the ISSBs associated with the ISSS
  which owns the socket.  This mechanism is not working and
  ISSBs are not returned to the free chain.
  KIXREVxxx
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: ISSB can not be freed after application *
  *                      task is purged during a socket wait.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A stress workload of DPL requests over an IPIC connection are
  sent from client region to server region. The application
  tasks which issues the DPL requests are defined with RTIMOUT
  and MONITOR timeouts set to purge transactions that take
  excessive time to complete.
  
  In client region, a DPL request is receiving the response data,
  and it is suspended on a socket wait. At the same time, the
  task which issues this DPL request is purged by the MONITOR
  mechanism. This causes the SO domain to treat it as a socket
  error and cancel the socket IO. Because of the canceled socket
  IO, the rest of the response data can not be received and the
  ISSB can not be freed.
  

Problem conclusion

• The IS domain has been changed to make sure the ISSB can
  be freed when trying to purge a task which is suspended on
  a socket wait.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

  PM87669

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

  UI12006

Modules/Macros

• DFHISRR  DFHISSR
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R800 PSY UI12006

     UP13/11/07 P F311

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.