Db2 for z/OS System and Application Performance Monitoring
Db2 for z/OS System and Application Performance Monitoring Module
The Db2 for z/OS System and Application Performance Monitoring ZMARS module examines your capability to detect exception conditions and deviations from normal processing patterns early enough to be able to take proactive measures to avoid service disruption or outages. This capability is based on effective application and system level real-time monitoring and historical reporting.
The Triton study team will produce an easily consumable report with prioritised findings and recommendations that, if implemented, will enhance your ability to monitor and report on and detect performance and operational conditions that can impact availability and resilience.
Why It Matters
Performance, resourcing and operational problems, whether at the system or application level, can easily turn into availability problems. For example, a contention problem combined with high CPU usage can result in a system-wide slow down or even outage. Early detection of out-of-line conditions can help you take proactive action to prevent service availability being impacted.
Combining Real-time Monitoring with Historical Reporting
Effective use of real-time monitoring and historical performance reporting, whether from a performance database or directly from the SMF data, are both essential tools in being able to detect out-of-line conditions that can lead to service outages.
Understand What Is Normal
Historical performance reporting tools can enable you to understand your normal processing profile across the day, peak periods, end-of-month and so on. Without that, early detection of out-of-line conditions is much more difficult if not impossible.
Early Problem Detection
In some cases, it is possible to identify deviations from normal indicating potential problems that could become availability issues and need to be investigated. For example, increased CPU resource utilization for a transaction or group of transactions, or increased GETPAGE counts against an individual object.
Root Cause Determination
Real-time monitoring and effective historical reporting are vital tools in driving problems, typically performance related, to root cause. Historical reporting is likely to be the most effective tool.
Real-time Diagnostics
When you are firefighting, being familiar with a real-time monitor that provides up-to-date information about what is going on in your system is a vital part of your defence strategy for your business services as it helps you drive to root cause.
Database Backup and Recovery
Is your backup and recovery strategy tailored for optimised, safe local recovery in scenarios ranging from single object recovery to mass recovery after logical data corruption?
Database Housekeeping
How effective is your housekeeping strategy – REORG, REBIND, statistics collection – at ensuring stable, predictable performance and efficient use of machine resources?
Single Points of Failure
This key module focusses on identifying single points of failure, and your strategy to restore/continue services as quickly and transparently as possible in the event of failure.