PM62786: SUBPOOL 231 KEY 7 STORAGE GROWTH IN ECSA FOR ORPHANED ENTRIES OF SADL/CTIB AFTER UTILITY JOB EXECUTIONS.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Slow growth in ECSA for DB2 subsystem. Utility jobs that have
  terminated will leave orphaned 'OG' entries in OWNCOMM report
  for SADL/CTIB control blocks. Dump will show small number of
  entries for SADL (100-150) but more for CTIBs more than 2000.
  The CTIBs are also larger than SADL entires in size.
  No abends in DB2, just accumulated entries for utility job
  executions in OG since IPL.
  
  SUBPOOL NAME: SADL for SSAM  AMGSSIDP
  PHB for this pool shows several entries like this:
  .
  1442C5B0: 00000078 0070006C E2C1C4D3 000A8000 000A0000
  ...%SADL........  N/A       DSN3AUCN +2655    UK67202
   1442C638: 00000078 0070006C E2C1C4D3 000A8000 000A0000
  ...%SADL........  N/A       DSN3AUCN +2655    UK67202
  
  Additional keywords:
    ECSA STORAGE LEAK
    SUBPOOL 231 0231 SUBPOOL231 SUBPOOL0231 SP231 SP0231
    KEY 7 KEY7 storage
    SADL SSAM CTIB
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
  *                 utility users of LOAD with TRUSTED CONTEXT   *
  ****************************************************************
  * PROBLEM DESCRIPTION: LOAD with TRUSTED CONTEXT results in    *
  *                      storage growth of subpool 231 in the    *
  *                      DBM1 address space                      *
  ****************************************************************
  * RECOMMENDATION: Apply corrective PTF when available          *
  ****************************************************************
  LOAD with TRUSTED CONTEXT results in subpool 231 storage growth
  in the DBM1 address space.  This is due to LOAD subtasks
  overlaying the address of one of their control blocks with the
  address of a control block from the LOAD main task.  This caused
  the storage of the original control block to not be freed when
  the subtask went through deallocation which, in turn, resulted
  in the DBM1 address space running low on storage.
  

Problem conclusion

• LOAD code has been modified to save the pointer for the subtask
  control block before overlaying it with the pointer from the
  main task control block.
  
  Subsystem Services code has been changed to make sure pointers
  are set up correctly so the utility subtask control blocks can
  be deallocated correctly.
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  UK79871 UK79872

Modules/Macros

• DSNUGSIT DSN3EOT0 DSN3ID30
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK79871

     UP12/07/12 P F207

• R910 PSY UK79872

     UP12/07/12 P F207

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.