PI92587: SNAPSHOT HISTORY DATA IS TRUNCATED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• SNAPSHOT history data is being collected and is visbile in the
  PE client up to a point in time. After that time no further
  SNAPSHOT history data is visible. The point in time generally
  coincides with the DB2 subsystem(s) being monitored experiencing
  a significant increase in activity.
  
  The DB2 subsystem is returning a reason code of 00E60802 which
  indicates that the return area provided by OMPE is not large
  enough for the amount of data being returned.
  
  Code will be changed to handle the 00E60802 reason code in a
  better fashion.
  

Local fix

• reduce the amount of data being collected for Sanpshot history
  In the RKD2PAR(OMPEdbid) members determine if all of the
  following are needed
  SHSTATISTICS=(Y,120)
  SHSQLCACHE=(Y,300)
  SHDATASETSTATISTICS=(Y,300)
  SHSYSTEMPARAMETERS=(Y,300)
  SHTHREAD=(Y,60)
  SHTHREADLOCK=Y
  SHTHREADSQL=Y
  SHDB2CONNECTAPPLICATION=(Y,60)
  SHDB2CONNECTSYSTEM=(Y,120)
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2 PM                *
  *                 users of component                           *
  *                        -  Performance Expert Client          *
  *                        -  PE Server subtask                  *
  *                                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Performance Expert Client does not  *
  *                      show snapshot history data in case      *
  *                      there is a large volume of active       *
  *                      threads and the parameter to collect    *
  *                      CPU parallelism data is set to 'NO'     *
  *                      (COLLECTCPUPARALLEL=N).                 *
  ****************************************************************
  * RECOMMENDATION: Apply the provided PTF.                      *
  ****************************************************************
  The problem surfaces when the following condition is true:
  The IFI reason code on a READS call that returns a warning
  (RC=4) is not equal to 00E60804 (for example 00E60802 or
  00E6080A) AND the OMPE Collector parameter COLLECTCPUPARALLEL=N.
  
  In this situation no data is written to the Snapshot History
  dataset and thus no data is displayed in the PE Client.
  
  Note that this situation is applicable not only for thread data,
  but can be observed also if the customer has turned on snapshot
  history collection for Dynamic Statement Cache data
  (SHSQLCACHE=(Y,x) in rHilev.RKD2PAR).
  

Problem conclusion

• The code logic has been corrected to accept all IFI reason codes
  that indicate data truncation to be processed correctly by the
  snapshot history data collector code.
  
  Furthermore, the product tracing has been enhanced with new
  tracing messages that are enabled when the trace level of the PE
  Server is set to TL=128.
  

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:

  UI54882 UI54883

Modules/Macros

•    DGOVHM00 DGOVMSTR FPEVDIM
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R530 PSY UI54882

     UP18/04/02 P F803

• R540 PSY UI54883

     UP18/04/02 P F803

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.