Monthly License Charges (MLC)
Tune your processor configuration to increase the MIPS you get out of your mainframe hardware.
The SMF 89 record type stores the CPU of each registered Sub-Capacity product over time. This is useful for finding out:
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.
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.
This blog covers several CPU reduction areas, including, moving work outside the monthly peak R4HA interval, reducing zIIP overflow, reducing XCF volumes, and leveraging Db2 memory to reduce I/Os.
CPU optimization opportunities applicable across the infrastructure can often by implemented without the involvement of application teams and can benefit a significant portion (or all) of the work across the system.
This webinar discusses the many tiers of storage in IT systems and offers ideas about how to optimize access to those areas.
Tune your processor configuration to increase the MIPS you get out of your mainframe hardware.
Configure Coupling Facilities for optimal availability and proactively identify hidden health and performance risks
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
Ensure sufficient capacity and consistent performance for IBM zEDC availability.
Monitor the health of your TCP/IP and analyze traffic from different perspectives.
Automated health check for workload manager (WLM) goals, improving performance and protect availability.
Compute and chart FICON Effective Channel Data Rate and rates if the value is good or not