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?
I have run into a number of customer who have Optim Performance Manager (OPM) and who were unaware of a feature introduced in OPM 22.214.171.124 in August 2012 that provides an important value-add to people working with DB2 workload management.
DB2 customers approach the task of identifying incoming work in different ways and I thought I would share some of what I have learned as a way of opening our minds to be able to view old problems from new, different perspectives. It never hurts to think new thoughts, keeps one young! ;)
I am finding it difficult to distinguish between the different connections because they either use the same authorization ID or come in through a middleware server like WebSphere or MicroStrategy. Is there any way that I can push more outside information into DB2?
This is a follow-on entry to a previous one discussing how workload management and DB2 pureScale get along... it contains a first draft of a proposal for a workload management paradigm aimed at homogeneous workloads (e.g. OLTP)