Introduction to Web Services insights available from CICS Transaction data that can facilitate collaboration between infrastructure and application teams.
More CICS Transactions Videos
- CICS Timing Metrics – Overview
- Transaction Response Time Analysis
- Timing Analysis by High-Level Components
- Response Time Analysis Scenario 1 Values Differing by System ID
- Integrating WLM Performance Index and CICS Transaction Analysis
- CICS Web Services Metrics
- Overview of Non-timing Transaction Metrics
All right. So in addition to all the timing buckets, the CICS transaction data captures almost 300 other metrics, and those metrics are organized by IBM into the subgroups that are listed here. And so today we’ll just have time to cover the categories that are listed in the first column. So let’s briefly introduce some of the metrics that are also available at the transaction level, other than timing metrics.
All right. So web service names, both operation and resource definitions are captured in the transaction data. And so here we see the volume of transactions that are using web services by transaction ID. And then for any particular transaction here, we can see the web service resource definitions being called by that transaction. Go ahead and look at this over time. So here we see various web service resource definitions being called by that particular transaction. Or we can begin analysis from the web service resource definitions, and then for any particular one, see which transaction is calling that service.
In this case, that’s a single transaction calling that service. So having access to the web service operation and resource definition names in the transaction data can help facilitate collaboration between infrastructure and application teams.
All right, so there are additional metrics, many web activity metrics that are also captured by transaction as previewed across the top of the screen. So here are total Web Requests and then they’re broken out by the type of the request, there’s the Browse requests, and the Read and Write Header requests. Other examples include Web Receive requests and Bytes Received. Another type of metric that’s captured here is the length of documents parsed using the XML system services parser. So, if we want to look at this by web service operation name, we can see that again. Just a reminder that all this data can be explored by web service name.
Speak to a Technical Expert Today
Whether you are conducting product research, need support on a project, are experiencing downtime, or want to learn more about how IntelliMagic can support your business, our experts are here to help.
You May Also Be Interested In:
Analysis of CPU By Plan: CICS Transaction (110.1) and Db2 Accounting (101) Part 2
Integrated visibility between Db2 Accounting and CICS Transaction data can correlate CICS transaction IDs driving high CPU in Db2 with the CICS profile of the transaction.
Elapsed Time Profiles by Correlation ID: CICS Transaction (110.1) and Db2 Accounting (101) Part 1
This video shows how viewing CICS Call Attach work by Correlation ID enables both CICS and Db2 teams to view elapsed time profiles within Db2 corresponding to each CICS transaction ID.
Troubleshooting WLM Missed Goals with CICS Transaction Data
Combined CICS and z/OS Systems visibility enables easy troubleshooting and root cause analysis of missed WLM goals resulting from CICS transaction data.