Viewing DB2 Object Performance Data in the Investigator › View DB2 Object Performance Data in the Time Series Facility › CA Chorus for DB2 Database Management TSF Examples

CA Chorus for DB2 Database Management TSF Examples

Example: Long Program Execution

The operations manager wants to know why a program seems to be taking longer to execute each time it is run. The manager first noticed the increase in execution time a few days ago and has now noticed that the issue is getting progressively worse.

Database administrators are regularly asked about past events that may be affecting current system performance (programs running faster or slower, permissions that are changed, and so on).

CA Chorus captures performance data from CA products at intervals set within Time Series Facility (TSF) parameters. Therefore, all of the DB2 executions have been captured, which can help you analyze a problem.

You can identify when this program was executed and can investigate the cause of the longer elapsed time. To do so, launch the Investigator and select the program that you want to investigate from the history or from the active display. Select the TSF. From TSF, specify a date range to view performance data in chart form. Use the chart to identify when the change in the package execution time began. After you identify when execution time degraded, look for prior events that could have triggered the issue.

Example: Post Upgrade Behavior

The operations manager wants to know if a DB2 process is taking less time to execute after a recent upgrade. The upgrade was completed a few days ago, and the manager wants to confirm that the upgrade has improved performance.

CA Chorus captures performance data from CA mainframe products at intervals that are set within TSF parameters. Database Administrators can use the TSF to create two charts to identify performance improvement. The first chart shows the current performance. The second chart shows the performance from the same day and time a week before the upgrade.

Example: Graph Application Performance Data

The need to graph and compare DB2 application performance data is high on the database administrator priority list. Today, you can use CA Detector to collect and aggregate data for reporting purposes. After the data is loaded into DB2 tables, use utilities, such as UNLOAD, to transfer the data into comma-delimited files. You can then FTP the file to your PC and load it into a software program to perform graphing. The process can be time-consuming and error prone.

With CA Chorus for DB2 Database Management, these steps are automated through TSF, which stores data that is collected and provided by CA products, such as CA Detector. TSF provides a single point for collection, storage, management, and organization of the product data. When you request a Time Series chart from the Investigator, TSF provides the data content for the chart and the ability to select different metrics to graph over time and to compare with different points.

To graph application performance data in CA Chorus for DB2 Database Management, complete the following steps:

1. Enable TSF to collect and manage DB2 application performance data within the enterprise. The TSF started task collects and manages the data regardless of the LPAR location.
2. Set up a CA OPS/MVS EMA task to run a started task to transport the data to the TSF. Complete this step for each CA Detector collection that you want.
3. The centralized Time Series Facility started task manages all performance data from all DB2 subsystems. The data retention and aggregation (up to five tiers) is defined during post-installation configuration. Each tier is defined with an expiration time in days, months, years, and a resolution for aggregation of one hour, two hours, and so on. The data is automatically moved to the next tier based on the tier expiration time and eventually purged based on the last tier expiration.

All CA Detector data from all subsystems across all LPARs are now available to you to manage and graph in the TSF.