PI08869: ECSA STORAGE SHORTAGE DUE TO CONTENTION ON THE IPMAIN LOCK

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A spike in ECSA storage due to contention on the IPMAIN lock.
  The unit of work holding the IPMAIN lock SHARED had been
  terminated with an ABEND04F.  The lock was not released
  during recovery processing.  Contention for the lock occurs
  when an IPMAIN lock EXCLUSIVE request is outstanding.
  

Local fix

• .
  KEYWORDS:  Subpool241 sp241 key6 key 6 K6 DUCB DUSA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of the IBM Communications Server for z/OS Version  *
  * 2 Release 1 IP                                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * ECSA sp241 storage growth of DUCBs caused by lock            *
  * contention.  The lock contention is a result of recovery     *
  * being interrupted before locks can be released.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply PTF                                                    *
  ****************************************************************
  ECSA sp241 storage growth of DUCBs caused by lock contention.
  The lock contention is a result of recovery being interrupted
  before locks can be released.
  
  An application thread (TCB or SRB mode) issues a socket call
  that obtains a TCPIP lock.  The application thread experiences
  an abend of some form which caused TCPIP's recovery routine to
  get control.  The recovery routine turns off the inuse indicator
  for the associated DUCB.  Before the recovery routine could call
  the lock release routine the address space was MEMTERMed.  The
  recovery routine was interrupted and no further processing of
  the DUCB was done due to the inuse flag being off.
  

Problem conclusion

• The recovery routines (EZBPFVNR and EZBITDRC) have been amended
  to set an indicator that locks have not been released when the
  inuse indicator is turned off.  The resource manager (EZBITREM)
  has been amended to process DUCBs that have the new indicator
  that locks have not been released.
  

Temporary fix

Comments

APAR Information

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

  PI08334

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

  UI15984

Modules/Macros

• EZBITREM EZBPFVNR EZBITDRC
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R210 PSY UI15984

     UP14/04/25 P F404

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.