This article describes the new enhancements in Version 20.0 of
CA Detector® for DB2 for z/OS.
The following list provides a high-level summary of the new features and enhancements that have been delivered to date in Version 20.0 for
CA Detector® for DB2 for z/OS(CA Detector):
To ensure availability of all features and fixes, we recommend that you install all available maintenance. To download and receive maintenance automatically, use CA SMP/E Receive Order. To view a list of available solutions and fixes, select the link for PTFs since GA on the CA Database Management Solutions for DB2 for z/OS Maintenance Grid (login required).
DBM 20 IR 8 is the last incremental update for Version 20.0. New features and fixes are no longer bundled in incremental PTFs. Instead, we have transitioned to a continuous delivery release model that provides individual PTFs for new product features and product fixes. For more information, see Transition to Continuous Delivery.
Filter CA Detector Collection Data by Connection Type (LU01002)
When you run
CA Detector® for DB2 for z/OScollections, you can now filter the collected data by connection type. A new field, Connection Type, has been added to the Add Include/Exclude Entry panel. This panel is accessible through your CA Detector collection profile. The ability to filter by connection type gives you more granular control over the collection of your Db2 application statistics, which helps you optimize the use of system resources.
For more information, see Limit Collection Activity.
Improved Performance for Batch Unloads (LU00565)
CA Detector® for DB2 for z/OSnow provides better performance when the PDTBATCH job is used with NORMALIZE=Y to unload collection data from the data store. Customers may experience significant improvement, depending on their site environments. Having a fast and reliable method for unloading normalized collection data helps ensure that your collection data is safely archived before it is overwritten in the data store.
Increased Number of Intervals for Data Stores (SO16173, SO16174)
You can now specify more intervals when creating a
CA Detector® for DB2 for z/OSdata store. Previously, you were limited to 999 intervals. This limit has been increased to 9,999. The ability to create a data store with more intervals lets you save smaller slices of data for more granular troubleshooting.
CA Mainframe Operational Intelligence Integration Enhancements
You can now customize the selection of Db2 plan and package metrics that you want to send from CA Detector to collect, view, and analyze in CA Mainframe Operational Intelligence. This enhancement allows you to exclude specific metrics from analysis in CA Mainframe Operational Intelligence. All metrics are included by default.
The default settings that indicate when to extract metrics based on the number of SQL calls for a plan or package have changed. If the following parameters are omitted when you extract CA Detector data, the default value is now zero:
The following new functionality helps reduce collection overhead:
- Statistics collection has been streamlined:
- CA Detector now collects only the statistics that it reports on. (Previously, some unused statistics were also collected.)
- Data movement during collection has been minimized when USECOLLTASKS(Y) is used.
- SQL activity data collection has been streamlined when COMPAT(N) is used. A more efficient collection mechanism has been implemented that reduces INDB2_CPU usage.
DB2 12 Support
IBM DB2 12 for z/OS function levels V12R1M100, V12R1M500, and V12R1M
nnnare now supported.
Version 20.0 of
CA Detector® for DB2 for z/OSsupports the IBM DB2 12 Continuous Delivery Model, which introduces new features in the maintenance stream for faster adoption.
Customers who are moving to DB2 12 should upgrade to Version 20.0 of
CA Detector® for DB2 for z/OSto take advantage of new DB2 12 features. In Version 19.0, only DB2 12 function levels V12R1M100 and V12R1M500 are supported.
Mainframe Team Center – Database Management for Db2 for z/OS
Mainframe Team Center – Database Management for Db2 for z/OS is a graphical user interface that lets you view and explore DB2 application performance data from
CA Detector® for DB2 for z/OSin a web browser.
This feature is configured to run on the CCS Apache Tomcat server and uses the Database Management Data Service (DBM Data Service) to read the collected data from CA Detector through Xnet and Xmanager services.
For more information about installing, configuring, and using the Mainframe Team Center user interface and the DBM Data Service, see the CA Database Management Solutions for DB2 for z/OS documentation.
With Mainframe Team Center – Database Management for Db2 for z/OS, you can easily identify poorly performing SQL statements in your environment. Database administrators at any experience level can monitor their mission-essential mainframe applications in a non-3270 environment.
You can also perform the following tasks:
- View current and historical DB2 application performance data from one or more data stores by DB2 subsystem ID or data sharing group.
- Explore SQL summarized by the following categories:
- Static or dynamic SQL statement
- Key by user ID, correlation ID, connection type, location, end user ID, transaction ID, or workstation ID
- Analyze SQL statement performance metrics in your preferred view. For example, view all packages for a particular DB2 SSID, then narrow the view to see SQL statements that are associated with a selected package.
- Reduce or eliminate right-to-left scrolling by rearranging the table columns.
- View dynamic SQL statement text.
Database Management Data Service
The Database Management Data Service (DBM Data Service) hosts a RESTful API that enables access to Db2 data and metrics that are collected by the
CA Database Management Solutions for DB2 for z/OS. The DBM Data Service allows applications such as Mainframe Team Center – Db2 Performance Analysis access to SQL activity and metrics that are collected by CA Detector. Also, mainframe and non-mainframe applications can use the API hosted by the service to access collected data.
For more information about installing, configuring, and using the Mainframe Team Center user interface and the DBM Data Service, see the CA Database Management Solutions for DB2 documentation.
CA Mainframe Operational Intelligence Solution
CA Mainframe Operational Intelligence lets your mainframe management team visualize and explore current and historical performance data, from across your mainframe, from one location. CA Mainframe Operational Intelligence also uses machine learning to predict future performance. Data-science algorithms provide the team with embedded and predictive analytics. CA Mainframe Operational Intelligence models your data and provides multiple tools to analyze it in your Web browser. CA Mainframe Operational Intelligence tools include alerts, dashboards, metrics, and reports.
With the historical, current, and predicted data, the team can:
- Predict incidents.
- Remediate faster.
- Improve collaboration among the mainframe management team.
- Optimize performance continuously.
CA Mainframe Operational Intelligence combines multi-domain data, machine learning, predictive analytics, and a domain-agnostic web application to help your site maintain optimal mainframe performance.
To learn more about the challenge that CA Mainframe Operational Intelligence addresses, see this video:
For detailed information about this solution, see the CA Mainframe Operational Intelligence documentation.
CA Detector® for DB2 for z/OSMetrics for
CA Mainframe Operational Intelligence
CA Mainframe Operational Intelligence Release 2.0.01 includes totals and averages for the following metrics from CA Detector Version 20.0:
Average metrics are displayed in CA Mainframe Operational Intelligence with the suffix AVG. For example, DB2_CPU_AVG represents the average amount of time that is spent executing within Db2. Average numbers are calculated by dividing the value of the total metric by the SQL_COUNT.
DB2_CPU represents the total amount of CPU time spent executing within Db2.
Redesigned SQL Collection Process
CA Detector® for DB2 for z/OSperformed SQL statement resource collection as part of SQL statement execution. Overhead that was associated with SQL statement capture, calculation, recording, and exception collection was added to the cost of the SQL statement.
With the new Collection Tasks process, calculation, recording, and exception collection are no longer performed as part of the SQL statement. Those functions are now performed by Xmanager collection tasks. Also, the Xmanager collection tasks can run on a zIIP processor. The Collection Tasks process provides more reliable processing, reduced CPU costs, and less overhead on SQL statements.
The Collection Tasks process has the following requirements:
- CA Common Services for z/OS Version 15.0 or above. For information about CA Database Management Solutions for DB2 for z/OS software requirements, see Software Requirements.
- Assign a higher dispatching priority to Xmanager than that of DB2 DBM1, DIST or WLM address spaces, any allied address space such as CICS, IMS, or WebSphere, or any address space that is executing SQL. For more information about dispatching priority, see Assign Dispatching Priority or a WLM Service Class.
The Collection Tasks process is enabled through the following new parameters in
- USECOLLTASKSEnables or disables the new collection process. By default, the new collection process is disabled.
- COLLTASKSCNTControls the number of collection tasks. By default, the collection process determines this number.
- USEZIIPEnables utilization of zIIP processors. By default, zIIP processor utilization is enabled.
- MAXQSpecifies how many elements the collection task queue can hold before data loss occurs. Valid values are 5000-120000.
Auto Delete Threshold for Collection Intervals
If a data set in a data store becomes full,
CA Detector® for DB2 for z/OScan now delete multiple collection intervals from the data set to make space for the newest interval. Previously, CA Detector stopped writing data to the data store. This new functionality lets CA Detector continue to write collection data to the data store even when the data store has become full.
This new functionality is enabled by adding the following parameter to the PDT parmlib member in
- INTERVAL_%_TO_DELETE (nnn)Specifies the maximum percentage of collection intervals to delete. For example, if you specify 50 percent and the data store contains 60 intervals, CA Detector can delete up to 30 of the oldest intervals to make space for the newest interval.Default:0Limits:0–100
Automatic Collection Restart after Abends
If a collection stops due to an abend, Xmanager can now restart the collection automatically when the collection meets certain criteria. This new functionality eliminates the need to monitor the collections manually and helps prevent gaps in collection data. Previously when an abend occurred during collection, the collection had to be restarted manually.
This new functionality is automatically enabled and does not require you to select any options.