The SMF 89 record type stores the CPU of each registered Sub-Capacity product over time. This is useful for finding out:
- which address spaces are registering which products on which systems
- product version
- product qualifiers (which relates to subsystem names for DB2 and MQ and components for IMS)
- CPU that is consumed by each product (used in specialized licensing programs like zCAP)
Tracking Software Version Upgrade Progress
One practical use of the SMF 89 data is to track the progress of a migration of a software version upgrade. As shown in the video, when a migration is underway from CICS version 5.3 To 5.5, the SMF 89 records give us insight into where the activity is occurring. In the video we see that most of the activity is happening on 5.5, but some activity is still happening on 5.3. This data also makes it easy to identify which the CICS regions are executing which versions.
Avoid MLC Charges on Unintended Usage
Another practical use of SMF 89 data is to help avoid being charged MLC costs for unintended data usage. Under MLC rules, any execution of a product on a particular system in a given hour causes all the MSUs for that system to be chargeable for that product. There can be instances when controls to limit execution of products to specified systems don’t work as intended.
We’ve seen TSO users executing the IMS BTS batch terminal simulator capability for unit testing result in IMS to be charged for MSUs on an unintended system. So usage data by product in the SMF 30 Address Space Records can be helpful in tracking down such unintended usage.
No-obligation MLC Reduction Assessment
Software costs consistently dominate the budget for mainframe installations of which processor cache efficiency can have a significant role in reducing. However, according to our recent survey, 88% of sites have not optimized their processor cache utilization. Get in touch with one of our experts to determine if your site has potential MLC savings.
Sub-Capacity Reporting Tool (SCRT) Filtering Capabilities & Benefits
The goal of analyzing Sub-Capacity Reporting Tool (SCRT) usage is to ultimately manage and reduce your MSU usage, and thus MLC costs.
Troubleshoot High CPU and zIIP Utilization in WebSphere Application Server
A common problem performance analysts encounter is high CPU utilization on a server or application without the ability to identify the root cause of the problem quickly and easily.
Monitor WebSphere Data Volumes
This video introduces the topic of transaction reporting based on the SMF 120 subtype 9 record, specifically in terms of data volume per request/response.
Supported Areas in IntelliMagic Vision for z/OS Systems
Monthly License Charges (MLC)
Tune your processor configuration to increase the MIPS you get out of your mainframe hardware.Learn More
Configure Coupling Facilities for optimal availability and proactively identify hidden health and performance risksLearn More
See Buffer Pool imbalances and proactively identify upcoming risks to your Db2 health and performanceLearn More
Save time looking for problems and profile CICS transaction data and see transaction response timeLearn More
Ensure sufficient capacity and consistent performance for IBM zEDC availability.Learn More
Monitor the health of your TCP/IP and analyze traffic from different perspectives.Learn More