I have a question about the total_extended_latch_wait_time monitor element. We recently saw high values of total_extended_latch_wait_time and we'd like to understand how to interpret this.
Statistics event monitors are an extremely useful way to get periodic monitoring of basic metrics on your system. They're just well-disguised behind a somewhat misleading name.
For those of you who use or like db2top, the new dsmtop tool is worth trying out!
I am trying to ensure that the work in my WLM configuration is going to the right place but my workload is always pointing to the same service class even though I know that I have a work action set to point the incoming statement to a different class. What am I missing?
We are collecting statistics every two minutes but looking at the CoordActLifetime histogram data collected in one of these 2 minute windows, we observed that in the upper bins, there are activities with lifetimes of 1715085 milliseconds (@28 minutes). How is this possible?