PK41333: DB2 V7- AND V8-SPECIFIC EDM POOL STATISTICS ARE NOT DISPLAYED ON THE TEP

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• OA17149 results in changes to EDM Pool data processing because
  of chagnes to the EDM pool structure in DB2 V8.
  
  Please make corresponding code changes in the XE side to
  parallel the classic fixes for these issues
  ERROR DESCRIPTION:
  VARIOUS INCORROUT PROBLEMS WITH DB2 V8 EDM POOL DISPLAY
  
  1. Under V8 is that the EDM pool from V7 has been split into
     three sections, EDMDBDC, EDMPOOL & EDMSTMTC, each with a
     separate ZPARM controlling the maximum size.
  
     Pool Usage    Pages  Pct
     ----------- ------- ----
       In Use      36031  49%
         DBDs      35909  49%
         CTs          22   0%
         PTs         100   0%
       Available   37780  51%
         SKCTs        55   0%
         SKPTs     11765  16%
         SQL CACHE 25102  34%
       Free          858   1%
     Total Pages   73811 100%
  
     DBD in use is 35909 pages, or 140Mb. the DBD limit as defined
     by EDMDBDC is 149 Mb.  The percentage value is 49%.  The
     value should read 94% to be of any real use.  CTs, SCTs, PTs
     and SPTs are controlled by the EDMPOOL parameter and SQL
     CAHCE is controlled by the EDMSTMTC parameter in similar
     fashions.
  
     The % of DBD usage should be calculated using the DBD  pool,
     not the old EDM pool total
  
  2. EDM pool snapshot zoomed into DBDs lists off the DBDs in the
     EDM pool. The values for DBD length in this list does not
     match the values seen for DBD length when a DIS DB(xxx)
     command is issues.  Omeg DB2 varies in what is reported.
     Yesterday was 33Mb for one DBD (only 13Mb today) while a
     display DB command comes in at 8Mb.   Why is there this
     discrepancy?
  
  3. Failures due to EDM Pool full is 0, despite numerous resource
     unavailable messages e.g.
     TB2A DSNGEPUF RESOURCE UNAVAILABLE
     REASON 00C90089
     TYPE 00000602
     NAME EDM DBD SPACE
     Should these messages be driving this counter?
     Should for V8 should we have a counter for each section of
     the EDM
     pool?
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   Common Collector                         *
  *                 -   Tivoli Enterprise Monitoring Agent       *
  *                 -   ICAT                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: DB2 V7- and V8-specific EDM POOL        *
  *                      statistics are not displayed on         *
  *                      the TEP.                                *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF.                              *
  ****************************************************************
  Version-specific EDM Pool data is not properly displayed.
  

Problem conclusion

• Changed code to support new version-specific EDM Pool data.
  KEYWORDS :
  EDM Pool, TEP
  

Temporary fix

Comments

APAR Information

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

  OA18459

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

  UK26875

Modules/Macros

•    KD5AGENT KD5ATR   KD5CAT   KD5DOC   KD5PDICT
  KD5SRMFP KD5SRMFQ KD5SRMGP KD5SRMGQ KD5SRMHP KD5SRMHQ KD5SRMIP
  KD5SRMIQ KD5SUCFP KD5SUCFQ KD5SUCGP KD5SUCGQ KD5SUCHP KD5SUCHQ
  KD5SUCIP KD5SUCIQ KD5VOM   KD5310PP KO2APCAS KO2APCA2 KO2APINS
  KO2APIN2 KO2OEVCB
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R310 PSY UK26875

     UP07/07/12 P F707

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.