My distributed DB2 V4.1 workload ran fine in compatibility mode but when I switched to goal mode, response time became very erratic. What happened?
Probably you did not add classification rules for your distributed DB2 transactions to your WLM service definition. Unclassified distributed DB2 transactions are assigned to the ‘SYSOTHER’ service class which has a discretionary goal. Using the WLM application, you need to add a set of classification rules under the ‘DDF’ subsystem type and assign the distributed transactions to service classes with appropriate response time or velocity goals.
Related Questions
- I am in goal mode and have been running fine with velocity goals for my CICS regions. Why should I switch to response time goals for CICS transactions?
- My distributed DB2 V4.1 workload ran fine in compatibility mode but when I switched to goal mode, response time became very erratic. What happened?
- How does Windows XP Mode align with Microsoft’s commitment to application compatibility?