The AutoStatus Database provides a persistent repository for active task information extracted from the MUF Dynamic System Tables Database.
In addition to providing a repository for the task information, the AutoStatus function provides a simple way to iteratively collect the active task information for one or more MUFs on the same LPAR. The information can be collated by collection timestamp allowing you to see all MUF activity on a given LPAR in one place.
This information can be used for debugging problems that occurred in the past, such as a user calls in that processing was slow this morning around 8 a.m. but seems okay now. Can you tell what was happening this morning?
In addition, you can write your own post processors to review the AutoStatus snapshots, detect if there are any response issues, and, if detected, generate automated alerts. For example, a site using AutoStatus never noticed that at certain times CICS transactions would hang for a minute or two and then resume. Users noticed the problem, but never complained. Their AutoStatus alert system caught the fact that periodically batch jobs would run that locked data rows for a few minutes. Each time they ran, they held records needed by CICS transactions, which caused the CICS transactions to wait for exclusive control. Once the batch jobs were detected, a small program fix was done and the CICS delays disappeared.
The task status information can be used to look for many different conditions that could be affecting MUF performance.
The overhead to collect the information is minimal. The work to process the task activity statistics has a relatively small resource footprint. In addition, the management process can be offloaded to a non-production MUF for processing to remove any load from the production systems.
While most users have a variety of home grown tools to measure performance, the AutoStatus system provides a standard implementation that every z/OS Datacom site can use.
Business Value
AutoStatus provides a straightforward simple process to collect active task statistics from all MUFs on an LPAR and store them as a one point in time snapshot. This information can be used to do after the fact problem analysis and well as interactive alert processing.
Using this functionality can improve the DBAs control of a given system without increasing their workload.
Additional Considerations
For the AutoStatus function to work, you must have the Dynamic System Tables Database enabled.
The AutoStatus function is executed using the CA Datacom/DB DBUTLTY AUTOSTAT function. For more information about this function, see the CA Datacom/DB DBUTLTY Guide.
For detailed implementation, usage information, and recommended implementation scenarios, see the newly created CA Datacom/DB AutoScope User Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|