Db2
See Buffer Pool imbalances and proactively identify upcoming risks to your Db2 health and performance
This video introduces the topic of transaction response time reporting based on the SMF 120 subtype 9 record.
Each request that comes into WebSphere is considered a transaction and can be reported down to the level of URI (Uniform Resource Identifier) name. These URI’s give you the names of specific resources or applications requested, and each individual request is logged, including its response time and certain response time components. These individual records can be aggregated to the time intervals and infrastructure resources (cell/cluster/node/sever/transaction class) that make sense for you.
With a flexible combination of predefined reports, user defined reports, and drill downs, IntelliMagic Vision enables WebSphere response time reporting to help you:
Download this white paper to see how you can get instant access to key WebSphere metrics and a more detailed look at how to monitor the performance and resource usage of WebSphere transactions.
In this reprint from Cheryl Watson’s Tuning Letter, Todd Havekost provides detailed information and insights from his analysis of seven upgrades from both z14 and z15 CPCs to z16s.
This final blog in the mainframe cost reduction series will cover potential CPU reduction opportunities that produce benefits applicable to a specific address space or application.
No matter which z/OS subsystem you are primarily responsible for, this article will help you blur the boundaries between the SMF ‘silos’ for each product.
See Buffer Pool imbalances and proactively identify upcoming risks to your Db2 health and performance
Save time looking for problems and profile CICS transaction data and see transaction response time
Monitor the health of your TCP/IP and analyze traffic from different perspectives.