Monitor and Profile CICS Transactions and Regions with IntelliMagic Vision
IntelliMagic Vision enables performance analysts to manage and optimize their z/OS CICS transactions more effectively and efficiently, as well as proactively assess the health of their CICS regions.
Profile transactions, save time, and access raw CICS data.
Optimize and Analyze CICS Transactions and Performance
CICS SMF Transaction data is a rich source of performance insights, but its volume can make analysis challenging using traditional approaches that rely on static reports. Proactive assessment of key Statistics metrics across all regions is essential to identify potential risks to availability.
IntelliMagic Vision provides GUI-based, interactive reports with dynamic navigation and context-sensitive drilldowns to facilitate rapid and focused access to CICS data to tune, optimize, and profile your transactions.
With IntelliMagic Vision, you will be able to:
- Profile CICS transactions and analyze response times
- Save time with quick access to interactive reports by transaction/CICS region
- Proactively assess the health of CICS regions
- Get access to CICS raw data to filter, compare, and find problems
IntelliMagic Vision offers you the out-of-the-box visibility and seamless navigation to manage every component of your z Systems infrastructure under a single solution.
Proactively Assess Key CICS Region Metrics to Enhance Availability
The CICS statistics 110.2 records contain several metrics that lend themselves to being assessed as part of the overall health of a region. IntelliMagic Vision assesses key metrics across every CICS region against best practice values to identify potential risks to availability that may warrant additional investigation.
The assessments are initially rolled up into user-defined logical groupings of regions and presented in a red/yellow/green manner that can be quickly consumed. From here the user can drill into the assessments for all regions making up the selected group, or directly into the metrics.
View Transaction Workloads
One common starting point for analysis of CICS workloads is a “Top n” view of transactions by total CPU consumption or by transaction volume (shown here).
Drilldowns from here can quickly focus the analysis on response times or other aspects of the transactions of interest.
Transaction Response Times by Primary Categories
The CICS SMF 110.1 records capture about 100 timing components for transactions. By drilling down on any transaction, the response time distribution can be analyzed, initially divided into the standard high-level summary categories for CICS response times.
Detailed Components of Response Times
Dynamic navigation and context-sensitive drilldowns enable additional detailed analysis based on the current display. Since a primary response time component for the transaction above was “Total I/O Wait Time,” the subcomponents of Total I/O Wait Time can be examined (again with a single click).
In this example, Wait for Control at end of MRO and Wait for RLS File I/O were the primary contributors to the I/O Wait response time component.
Elapsed Time Profiles Across Transactions
The ability to compare profiles across transactions by those primary CICS response time categories can also provide helpful insights. This example shows CPU per CICS transaction across the selected transactions.
A global filter can also be specified to further focus the selected transactions.
Integrating CICS Transaction with Db2 Accounting Data
Capitalizing on the fact that Db2 Accounting data (SMF 101) captures the CICS transaction ID, IntelliMagic Vision seamlessly integrates key metrics from Db2 with the CICS SMF data. This set of charts integrates metrics from the CICS perspective on the top row (based on the transaction ID) and DB2 perspective on the bottom row (using the correlation name).
CICS Raw Data
Finally, all the remaining non-timing fields in the CICS 110.1 records (approximately 275 in number) are available for detailed analysis and are organized into the subgroups provided in the IBM documentation. Transaction-level metrics of potential interest include Db2 SQL calls per CICS transaction (pictured here), log stream writes, getmains by CICS storage area, and program loads.