Editorial photograph of a data center mainframe hall with rows of enterprise infrastructure
Article · IBM · Mainframe

IBM mainframe software licensing.

Mainframe software is the densest cost in many IBM estates. This buyer side advisory covers the MSU metric, sub capacity pricing, Tailored Fit Pricing, the Broadcom mainframe portfolio, and the renewal levers CIOs actually control.

Read the Framework IBM Hub
MSUThe core mainframe metric
30 to 60%Typical MLC of the bill
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Mainframe software is priced on capacity you can shape, so the MSU peak, the pricing model you sign, and the Broadcom renewal are the three levers that move the bill.

Key takeaways

  • MSU is the meter: most IBM mainframe software is priced on Million Service Units of capacity.
  • MLC tracks the peak: Monthly License Charges follow the rolling four hour average peak, not raw usage.
  • Sub capacity is the saver: reporting through SCRT prices software below the box capacity.
  • Tailored Fit Pricing changes the math: a consumption model that can help or hurt depending on profile.
  • Broadcom owns the CA stack: the former CA mainframe tools now renew on Broadcom terms.
  • The lever is the peak: capping and workload timing move MSU more than any discount ask.

How does the IBM mainframe MSU metric work?

Million Service Units measure processing capacity on IBM Z. Most IBM mainframe software is priced against the MSU rating of the capacity the software can use. The current IBM Z platform is documented on the IBM Z product pages.

The crucial point for buyers is that MSU is a capacity meter, not a usage counter. You pay for the capacity the workload peaks into, which is why peak control is the primary lever.

The rolling four hour average

Monthly charges follow the rolling four hour average peak across the measured period. A short spike can set the bill for the whole month, so workload timing matters more than total volume.

What drives the MSU bill

  • Peak capacity: the rolling four hour average high water mark.
  • Defined capacity: soft caps that limit the chargeable peak.
  • Workload placement: batch timing that avoids stacking onto the online peak.

What is the difference between MLC and sub capacity pricing?

Monthly License Charge software bills every month against the measured peak. Sub capacity pricing lets you license below the full box capacity by reporting actual usage through the Sub Capacity Reporting Tool, as set out in IBM z/OS licensing terms.

Without sub capacity reporting, the default is full capacity. On a large box that gap is the single biggest avoidable cost in the mainframe budget.

Mainframe pricing models compared

IBM mainframe pricing models

ModelBasisBuyer lever
MLC full capacityBox MSU ratingReduce box size
MLC sub capacityReported peak via SCRTCap the peak
Tailored Fit PricingAnnual consumption baselinePick the baseline year
One Time ChargePerpetual plus supportNegotiate at purchase

Why SCRT discipline pays

  • Report monthly: SCRT submissions must be timely and complete.
  • Cap deliberately: defined capacity limits the chargeable peak.
  • Reconcile: match reported peaks to entitlement before renewal.

Should a CIO move to IBM Tailored Fit Pricing?

Tailored Fit Pricing replaces the monthly peak model with an annual consumption baseline plus a growth allowance, described on the IBM Tailored Fit Pricing pages. It can simplify budgeting and remove the peak penalty.

It can also lock in cost if the baseline year was unusually high or if growth runs below the allowance. The decision turns entirely on your baseline year profile.

Tailored Fit Pricing decision points

  • Baseline year: model a low year and a high year before signing.
  • Growth allowance: compare the included growth to your real trajectory.
  • Exit terms: understand how you leave if consumption falls.

When it helps and when it hurts

It helps estates with steady growth and uncontrolled peaks. It hurts flat or shrinking estates that would do better capping a peak model. Run both scenarios before committing.

Where the common advice on mainframe licensing is wrong

The standard advice is to chase a bigger percentage discount at renewal and treat the MSU bill as fixed. We disagree. In the mainframe estates we advised, the discount ask moved the bill far less than capacity discipline did. Capping the rolling four hour average peak and timing batch workloads cut MLC by 15 to 30 percent before any discount conversation started. The buyer side move is to control the peak and model Tailored Fit Pricing against a real baseline first, then negotiate rate. Rate is the last lever, not the first, and treating it as the first leaves the largest savings untouched.

Editorial photograph of an engineer reviewing capacity and workload metrics on multiple terminal screens
On the mainframe, a short peak can set the whole month, so workload timing beats discount asks.
15 to 25
Mainframe estates advised 2024 to 2025
15 to 30%
MLC cut from peak control
20 to 40%
Broadcom renewal uplift asks seen

Source: Redress Compliance advisory engagement file, 2024 to 2025.

We capped defined capacity and moved two batch windows off the online peak. The rolling four hour average dropped, and the monthly license charge fell before we ever opened the discount conversation.
Head of Mainframe · European insurer

How do you handle Broadcom mainframe software renewals?

The former CA Technologies mainframe tools now renew under Broadcom, whose mainframe portfolio sits on the Broadcom mainframe pages. Renewal asks have been steeper since the acquisition.

The buyer side counterweight is credible optionality. Third party support and selective retirement of low value tools reset the conversation. The wider Broadcom playbook rewards customers who arrive with alternatives.

Broadcom renewal levers

  • Tool rationalization: retire overlapping or unused mainframe tools.
  • Third party support: price the alternative to anchor the renewal.
  • Term shaping: trade term length for rate certainty.

Third party support as leverage

Even when you intend to stay, a costed third party support option changes the negotiation. It converts an open ended uplift ask into a bounded commercial decision.

What to do next

  1. Pull twelve months of SCRT reports and find the real rolling four hour average peaks.
  2. Set or tighten defined capacity caps on the highest cost products.
  3. Reschedule batch windows that stack onto the online peak.
  4. Model Tailored Fit Pricing against both a low and a high baseline year.
  5. Inventory the Broadcom CA tools and flag overlap and shelfware.
  6. Price a third party support option before the next Broadcom renewal.

Frequently asked questions

What is an MSU on the mainframe?

An MSU is a Million Service Unit, IBM's measure of mainframe processing capacity. Most IBM mainframe software is priced against the MSU rating of the capacity it can use. It is a capacity meter rather than a usage counter, which is why peak control drives the bill.

How is the monthly license charge calculated?

Monthly License Charge software bills against the rolling four hour average peak across the measured period. A short spike can set the charge for the entire month. Capping defined capacity and timing workloads off the peak are the main levers to reduce it.

Does sub capacity pricing always save money?

Almost always on a large box, because the default without it is full capacity licensing. Sub capacity prices software against the reported peak through SCRT. The saving requires timely, complete monthly reporting and deliberate capping to hold the peak down.

Is Tailored Fit Pricing cheaper than MLC?

It depends entirely on your baseline year and growth profile. Tailored Fit Pricing helps estates with steady growth and uncontrolled peaks. It can cost more on flat or shrinking estates that would do better capping a traditional peak model. Model both before signing.

What changed when Broadcom acquired CA?

The former CA mainframe tools now renew on Broadcom commercial terms, and renewal uplift asks have been steeper. The counterweight is credible optionality, including third party support and retiring low value tools, which resets the negotiation.

Can we use third party support on the mainframe?

Yes, for many products, and it is a strong negotiation lever even when you plan to stay. A costed third party support option converts an open ended uplift ask into a bounded commercial decision and anchors the renewal.

How quickly can mainframe cost be reduced?

Peak control measures often land inside one or two billing cycles because they act on the rolling four hour average directly. Structural savings from pricing model changes and tool rationalization usually follow at the next renewal.

Where do most mainframe overspends hide?

In an uncontrolled peak, in pricing models signed without scenario analysis, and in overlapping tools nobody retired. The largest avoidable cost is usually capacity that was never capped, not a discount that was never won.

Score your IBM mainframe estate for peak control and renewal readiness in under five minutes.
Run the Software Spend Health Check →
White Paper · IBM

Download the IBM Audit Defense Guide.

A buyer side framework for ILMT compliance, the PVU baseline, and the VPC transition. Includes the ILMT health check template, the entitlement reconciliation worksheet, and the conversion map used across hundreds of IBM engagements.

Independent. Buyer side. Built for CIOs and procurement leads carrying IBM software estates or facing an IBM audit. No vendor influence. No sales kickback.

IBM Audit Defense Guide

Open the white paper in your browser. Corporate email only.

Open the Paper →
Editorial photograph of enterprise contract negotiation strategy

Your mainframe bill is shaped by the peak, not the discount.

We have served 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.

IBM intelligence, monthly.

MSU peak control tactics, Tailored Fit Pricing movement, Broadcom mainframe renewal data, third party support signals, and the wider IBM commercial leverage patterns across every engagement.