Realtime data fields for which data is cumulative

OMEGAMON for Db2 PE reports cumulative values for some fields when Accounting trace class 1 is not active.

When Accounting trace class 1 is not active and the thread involved is reused, the value on OMEGAMON for Db2 PE displays is cumulative since thread creation. The following table contains the names of the fields that might contain cumulative data and the names of the panels on which they are displayed.

Table 1. Accounting trace class 1 - Cumulative data fields
Panel name Field names
Thread Buffer Pool Activity Getpage Requests
Getpages/Read I/O
Page Updates
List Prefetch Requests
Prefetch Pages Read
Immediate Writes
Failed Getpage Requests
Synchronous Read I/O
Sequential Prefetch Requests
Dynamic Prefetch Requests
Elapsed Time
ETIM
GETP
PREF
RIO
Summary of Db2 Activity PGUP
Exception Messages Aborts
Alters
Connects Type 1
Connects Type 2
Commits
Current SQL Counts Creates/Drops
Deletes
Describes
Fetches
Grants/Revokes
Incremental Binds
Inserts
Label/Comment Ons
Lock Tables
Open/Close Cursors
Prepares
Releases
Selects
Set Connections
Set Degrees
Set Host Variables
Set SQLIDs
Updates
Commit
Elapsed
Getpg
Update
Commit
Threads Summary Excluding Idle Threads Elapsed
Getpg
Update
 
CICS® Thread Summary  
 
 
 

When Accounting trace class 1 is active, the values in these fields will still be cumulative if all of the following conditions are met:

  • The thread involved was created as a reusable thread.
  • The thread is actually being reused.
  • Thread Signon was not driven for the new user of the thread.