PI49958: STORAGE LEAK IN MULTI-THREADED ENVIRONMENT WHEN QSAM OR VSAM FILE IS CLOSED.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• COBOL leaves a small piece of storage allocation when a QSAM or
  VSAM file is closed. When a COBOL program is invoked many times
  in a multithreaded environment (POSIX(ON)) and the COBOL
  program uses the THREAD option, the leak could lead to out of
  storage conditions (as in ABEND878).
  
    The areas not being freed were x'38' in length and just
  contained a pointer to an FCB. For example:
  
  64C2D3D2 00000038 00020101 00000000 | MBLK............ |
  00000000 00000000 00000000 643C802C | ................ |
  643C7020 643C9020 341B74BC C5D5C460 | ............END- |
  D4C2D3D2 00000000 00000000 00000000 | MBLK............ |
  
  The pointer 341B74BC in the sample above would take you to an
  area with the eyecatcher "FCB".
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Enterprise COBOL V5.x users compiling and    *
  *                 running programs that are compiled with the  *
  *                 THREAD compiler option and run under a       *
  *                 multi-threaded POSIX(ON) environment, and    *
  *                 that contain QSAM or VSAM files OPENed and   *
  *                 then CLOSEed repeatedly.                     *
  *                                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: There is a small memory leak in the     *
  *                      CLOSE processing of the file.           *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply provided service.                      *
  ****************************************************************
  During OPEN of QSAM/VSAM file, a control block is created to
  associate the OPENed file with the current thread. If the thread
  is cancelled, that information is used to correctly close all
  files associated with that thread.  During CLOSE processing, the
  control block that associate the file CLOSEing and the thread
  should be removed.  The issue is that removal was not done
  correctly.
  
  FIXCAT keyword:  COB0501T/K   COB0502T/K
  

Problem conclusion

• The logic of the CLOSE file processing to handle THREAD in
  POSIX(ON) is fixed to correctly remove that control block used
  to associate the file with the thread. Thus removing the memory
  leak.
  

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:

  106PC1Ÿ

Modules/Macros

• IGZXLPKA
  

Fix information

• Fixed component name

  LE ENT COBOL LI

• Fixed component ID

  568819812

Applicable component levels

• R7A0 PSY UI32124

     UP15/10/23 P F510

• R780 PSY UI32125

     UP15/10/23 P F510

• R790 PSY UI32126

     UP15/10/23 P F510

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.