IC51815: TSM SERVER MEMORY LEAK IN PKMON.C FOR CONDITION VARIABLE ALLOCATIONS

APAR status

• Closed as program error.

Error description

• There is a small TSM Server memory leak that occurs when
  condition variables are allocated for storage service sessions.
  Storage service sessions are started for any operation that
  needs to access data in a storage pool for either read or write
  purposes. This would include both random access and sequential
  storage pool access.
  .
  NOTE: The memory leak is very small so in most cases it will
  take a very long time for it to become noticeable, or to even
  cause problems such as exhausting the available memory on a
  given server. The effects of the leak will vary depending on
  workload and memory limitations for a given TSM Server.
  .
  Platforms affected: All TSM 5.3 and 5.4 Servers
  .
  Customer/L2 Diagnostics:
  If TSM Server memory utilization continually increases over
  time and remains constant even during times when the TSM
  Server is quiet, issue the following
  command (this command is not valid for Windows):
  .
  show alloc
  .
  If the pkmon.c allocations account for close to half of the
  total memory being consumed by the TSM Server, this APAR most
  likely applies:
  .
  pkmon.c line   461:
  .
  I.E. This is an example of excessive memory allocations for
  pkmon.c:
  pkmon.c line   461:      941 entries for    1806720000 bytes
  .
  Initial Impact: Medium
  .
  Additional Keywords:  ANR9999D enomem pkalloc leak leaking swap
                        paging page condvar errno out of memory
                      exhausted
  .
  

Local fix

• Recycle the TSM Server when memory usage gets close to the
  limit imposed by the system.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM Tivoli Storage Manager V5.3 *
  *                                                              *
  *                 and V5.4.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: See Error Description.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available.  This     *
  *                 problem is currently projected to be fixed   *
  *                 in levels 5.3.5 and 5.4.1. Note that this is *
  *                                                              *
  *                  subject to change at the discretion of IBM. *
  ****************************************************************
  TSM server does not free some allocated memory.
  

Problem conclusion

• TSM server is modified to eliminate the problem.
  

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:

  PK40665

Modules/Macros

• SSSESS
  

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R53A PSY

     UP

• R53H PSY

     UP

• R53L PSY

     UP

• R53S PSY

     UP

• R53W PSY

     UP

• R53Z PSY

     UP

• R54A PSY

     UP

• R54H PSY

     UP

• R54L PSY

     UP

• R54S PSY

     UP

• R54W PSY

     UP

• R54Z PSY

     UP