CPU by WLM Importance Level: Automated Change Detection Use Case 2

This example begins by examining statistically significant changes in WLM performance indices, where values above 1.0 mean that WLM goals are not being met. Leveraging context-sensitive drilldowns, based on an unanticipated finding of a spike in CPU consumption for the highest importance “Systems” work, the analysis shifts to investigate the address space(s) driving that.

Use Cases for Automated Change Detection

1. CPU by System
2. CPU by WLM Importance Level
3. CICS CPU per Transaction
4. Db2 Getpage Rate
5. Coupling Facility Request Rate
6. Batch Job Elapsed Time
7. CICS Max Tasks
8. Health Insights and Change Detection