PM56361: 8 BYTES OF PRIVATE STORAGE IS ORPHANED BY FREEMAIN OF PHB EACH TIME AN ALLIED ADDRESS SPACE ASID IS REUSED IN V10.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In DB2/z V10, 8 bytes of private storage is leaked each time
  the ALLIED address space is reused. This page fragmentation
  causes the address space to eventually run out of contiguous
  high private, resulting in RC00E20015 or similiar storage
  abend. SP229 SUBPOOL 229 KEY7 DB2STGLK/K
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 V10 HDBAA10 users.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Allied address spaces which are reused  *
  *                      repeatedly, such as WLM Stored          *
  *                      Procedures, WAS, or JES Initiators may  *
  *                      experience an out-of-storage abend such *
  *                      as RC00E20003, RC00E20015, or other     *
  *                      RC00E2nnnn storage bend.  Analysis      *
  *                      shows that there are many pages which   *
  *                      contain an 8 byte allocation, usually   *
  *                      at the very end of the page.  Page may  *
  *                      contain residual field names such as    *
  *                      FTBL, ASST, and PHBG.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The control block getmained at ALLIED start-up for the PHB to
  house the pool of PHBs, was changed from being double-word
  bounded to quad-word bounding on the getmain.  The ALLIED
  termination failed to round up the actual length of the control
  block, causing 8 bytes to be orphaned each time the address
  space was reused.  If this ASID remains active and reused for an
  extended period of time, this causes severe fragmentation of the
  private storage in the address space.
  

Problem conclusion

• The FREEMAIN during ALLIED termination has been changed so that
  the correct size of the control block is used.
  

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:

  UK75989

Modules/Macros

• DSNSFPL
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK75989

     UP12/02/28 P F202

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.