IBM Z and LinuxONE - Group home

OMEGAMON Db2 Display Interval statistics on E3270 UI for recent Interval by Paul Kenney and Rokas Zemaitis

  

Problem overview

The OMEGAMON Db2 Enhanced 3270 User Interface the main workspace displays statistical values are totals since the start of Db2.  Since a DB2 subsystem usually runs for a long time, the Statistics may not be relevant to more recent problems. Situations and highlighting of fields can become almost meaningless because the values are too large.

Customer value 

With enhancement  APAR PH35707 / PTF UI76291) you will be able to display Db2 Statistics for a recent interval for example the last 24 hours. Now situations and thresholds can be based only on recent values like deadlocks that occurred today.

Interval reset situation

A situation must be defined on the Interval_reset table using the HOUR column to set the time when the Statistics should be reset.

The following example shows resetting the Statistics at 3 am every night.

This situation should be distributed to all Db2 subsystems that you want to see interval Statistic.

If you would not define a situation, Interval data collection would be started when you enter the KDPINTVD workspace the first time.

New Panels in Enhanced 3270 UI

From the All Active DB2 Subsystems Main Workspace Select D to display KDPINTVS – The Db2 Interval summary workspace.

The D Select can be used to show more detail for one specific Db2 subsystem on the KDPINTVD  Db2 Subsystem Interval Statistics detail Workspace.

Conclusion

Being able to Create Situations and Highlight on the DP_interval_statistics table will allow you to monitor your Db2 subsystems more accurately and pinpoint the times when problems occur.