PI58948: PE SERVER SNAPSHOT HISTORY DOES NOT START COLLECTING DATA

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When a PE Server subtask is configured with function Snapshot
  History activated, collection of snapshot history data may not
  be started after the monitoring PE Server subtask completes the
  start up phase. Depending on the start up and dispatch sequence
  a timer may not get started. In this case snapshot data are not
  retrieved from the monitored DB2 subsystem or a monitored DB2
  Connect Agent and no more data are stored into the snapshot
  history dataset.
  When snapshot history or DB2 Connect data are requested from
  PE Server for display in a user interface, outdated performance
  data are displayed.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component                           *
  *                 - PE Server subtask                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Several problems are observed.          *
  *                      1. PE Server function Snapshot History  *
  *                      does not start collecting data.         *
  *                      2. PE Server issues message FPEV0060E   *
  *                      during termination.                     *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF.                              *
  ****************************************************************
  PROBLEM SUMMARY:
  1. When a PE Server subtask is configured with function Snapshot
  History activated, the collection of snapshot history data may
  not be started after the monitoring PE Server subtask completes
  the start up phase. Depending on the start up and dispatch
  sequence a timer may not get started. In this case snapshot
  data are not retrieved from the monitored DB2 subsystem or a
  monitored DB2 Connect Agent and no more data are stored into
  the snapshot history dataset. When snapshot history or DB2
  Connect data are requested from PE Server for display in a
  user interface, outdated performance data are displayed.
  
  2. When PE Server is monitoring a DB2 subsystem with function
  Autoexception activated and the corresponding Autoexception
  Exit is also activated, the termination of the monitoring PE
  Server subtask is delayed because the stop request is not sent
  to the task driving the exit. Message FPEV0060E is issued.
  
  PROBLEM CONCLUSION:
  The code has been corrected accordingly
  1. to start snapshot history collection independent of the
  start up and dispatch sequence and
  2. to propagate the stop request to the subtask driving the
  Autoexception Exit.
  
  KEYWORDS:
  SNAPSHOT HISTORY HANGS DB2 CONNECT AUTOEXCEPTION
  FPEV0060E
  

Problem conclusion

• The code has been corrected accordingly
  1. to start snapshot history collection independent of the
  start up and dispatch sequence and
  2. to propagate the stop request to the subtask driving the
  Autoexception Exit.
  

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:

  UI36554 UI36555 UI36556

Modules/Macros

• DGOVHM00 DGOVMSTR DGOVUM02
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R511 PSY UI36554

     UP16/03/30 P F603

• R520 PSY UI36555

     UP16/03/30 P F603

• R530 PSY UI36556

     UP16/03/30 P F603

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.