Editorial photograph of an IBM mainframe operations center with capacity planning charts on the wall
Article · IBM · Mainframe

Mainframe MSU and MIPS, reduced.

IBM mainframe licensing through MSU and MIPS metrics still drives some of the largest annual software lines in any enterprise IT budget. The buyer side levers are real, repeatable, and rarely fully exploited. This article is the 2026 reference for licensing reduction.

Read the Framework IBM Hub
18 to 35%MSU reduction range
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

IBM mainframe licensing on MSU and MIPS scales with the rolling four hour average peak workload. The single largest buyer side lever is the sub capacity pricing model, which prices each product family on the highest LPAR usage during a rolling four hour window, not on the total installed capacity.

Most enterprises leave eighteen to thirty five percent on the table by failing to operate ILMT discipline, by missing the workload shift opportunities, and by accepting the IBM ELA renewal without challenging the MSU baseline. This article fixes that.

Pair this article with the IBM knowledge hub, the IBM advisory practice, the IBM audit defense landing, the mainframe CIO advisory, the Mizuho case study, and the financial institution mainframe case study before the next renewal.

Key Takeaways

What a CIO needs to know in 90 seconds

  • MSU is the metric. Million Service Units per hour, rolling four hour average peak.
  • MIPS is the hardware view. Million Instructions Per Second, used for capacity sizing.
  • Sub capacity beats full capacity. Every enterprise that runs LPAR partitioning should use sub capacity.
  • ILMT is mandatory for sub capacity. IBM License Metric Tool must be deployed and reporting.
  • Workload shift is the lever. Move workloads out of the rolling four hour peak window.
  • ELA renewals reset the baseline. The MSU number at renewal anchors the next three to five years.
  • Independent benchmarks unlock leverage. The buyer side bench mark on IBM mainframe deals.

MSU and MIPS basics

IBM mainframe software licensing operates on two related but distinct units. MSU, the Million Service Units per hour, is the IBM software metric. MIPS, the Million Instructions Per Second, is the hardware capacity metric. The two move together but are not identical.

Three metric concepts to know

  • MSU rating. Each Z processor model carries an MSU rating that defines its software cost contribution.
  • R4HA. The Rolling Four Hour Average is the basis for sub capacity pricing.
  • WLC. Workload License Charges is the modern monthly billing model that uses R4HA.

Pricing model summary

ModelBasisBest fit
WLC, VWLCVariable monthly by R4HA peak per LPARMost enterprise z/OS estates
EWLCEntry level R4HASmaller installations
S/390 Usage PricingLegacy, full capacityRare
PSLCParallel Sysplex, full capacitySpecific clusters
Tailored Fit PricingAnnual commitment by baselinePredictable workload growth

Sub capacity pricing

Sub capacity pricing is the IBM model that allows enterprises to pay for the peak workload usage on each LPAR rather than the total machine capacity. The model can reduce the licensed MSU figure by thirty to sixty percent for an enterprise running multiple LPARs at different peak times.

Sub capacity eligibility rules

  1. ILMT deployed. The IBM License Metric Tool must be installed, configured, and reporting continuously.
  2. SCRT data. The Sub Capacity Reporting Tool feeds the monthly utilization data to IBM.
  3. SCRT submission. Monthly SCRT reports must be submitted within nine days of month end.
  4. Audit support. The customer must retain SCRT reports for two years for audit verification.

The ILMT trap

Sub capacity pricing eligibility depends on continuous ILMT deployment. A single ILMT outage longer than seven days can flip the customer to full capacity pricing for the affected month, with the back maintenance bill running into the seven figures for a mid size mainframe estate.

The buyer side discipline is to monitor ILMT health daily, log the uptime, and respond to any outage within hours, not days. The audit defense relies on the audit trail.

ILMT discipline

The IBM License Metric Tool is the linchpin of mainframe sub capacity pricing. Most audit findings against enterprise mainframe customers trace back to ILMT gaps, not to underlicensed software. The buyer side discipline is operational, not contractual.

Five ILMT discipline practices

  • Daily health check. Confirm ILMT agent reporting on every monitored LPAR.
  • Monthly SCRT submission. By the ninth day of the following month, no exceptions.
  • Quarterly reconciliation. ILMT inventory against the IBM Passport Advantage contract data.
  • Annual review. Independent third party audit of ILMT data quality.
  • Incident playbook. Written response for any ILMT outage longer than twenty four hours.

Reduction levers

The buyer side reduction levers for IBM mainframe MSU licensing run across two categories. Operational levers reduce the actual MSU consumption. Contractual levers reduce the price paid per MSU.

Reduction lever matrix

LeverCategoryTypical reductionEffort
Workload shift to off peakOperational5 to 15% MSUMedium
zIIP and zAAP offloadOperational10 to 25% MSUHigh
Decommission unused subsystemsOperational3 to 8% MSUMedium
Capping defined limitsOperational5 to 10% MSUMedium
Tailored Fit PricingContractual0 to 10% priceLow
ELA renewal negotiationContractual10 to 25% priceHigh
Multi product bundleContractual5 to 15% priceMedium

Lever prioritization

The right sequence starts with the operational levers because they compound. A workload shift that drops the R4HA peak by ten percent will reduce the MSU bill for every product priced on R4HA. The contractual levers then apply against a lower baseline, multiplying the saving.

ELA renewal moves

The IBM Enterprise License Agreement renewal is the largest single negotiation moment for any mainframe customer. The seven move sequence below is the buyer side play book Redress runs across IBM mainframe renewals.

Seven moves at ELA renewal

  1. Baseline the MSU consumption. Two year SCRT data, peak by product, peak by LPAR.
  2. Run the operational lever audit. Workload shift opportunities, zIIP offload candidates.
  3. Score the bundle. Which products carry weight at renewal, which are paid but unused.
  4. Pull the buyer side benchmark. Independent MSU rate benchmarks by product family.
  5. Open the alternative. Distributed migration scenarios for selected workloads.
  6. Cap the price uplift. Zero to three percent annual cap, fixed in the renewal contract.
  7. Time the close. IBM quarter end leverage, March, June, September, December.

The mainframe renewal closed at thirty one percent below the IBM opening proposal after a twelve month ILMT discipline reset and a workload shift program. The MSU consumption dropped fourteen percent on the operational side. The contractual lever added another seventeen percent on the price side.

What to do next

The seven step checklist below is the buyer side starting position for any IBM mainframe MSU reduction engagement.

  1. Pull twenty four months of SCRT. Peak by product, peak by LPAR, R4HA distributions.
  2. Audit ILMT health. Daily reporting, monthly submission, quarterly reconciliation.
  3. Map the workload windows. When does the R4HA peak occur, what drives it.
  4. Inventory the product bundle. CICS, DB2, MQ, IMS, z/OS, ISVs, paid but unused.
  5. Pull the buyer side benchmark. Redress benchmark or comparable independent source.
  6. Build the operational lever plan. Workload shift, zIIP offload, capping, decommission.
  7. Open the ELA renewal sequence. Twelve to eighteen months ahead of the renewal date.

Frequently asked questions

Is sub capacity pricing available to every IBM mainframe customer?

Sub capacity pricing requires ILMT deployment, SCRT data submission, and an eligible IBM contract. Most modern z/OS estates qualify. Customers on legacy parallel sysplex full capacity pricing or on older S/390 usage pricing terms need to migrate to a WLC variant to access sub capacity. The migration is a contract event and typically aligned to an ELA renewal.

What is the difference between MSU and MIPS?

MIPS is a hardware capacity metric, Million Instructions Per Second, used for sizing. MSU is a software cost metric, Million Service Units per hour, used for IBM licensing. The two move in the same direction but the conversion ratio differs across IBM processor models. The license cost is driven by MSU, not by MIPS.

How long does an ELA renewal take?

A mainframe ELA renewal typically runs twelve to eighteen months from kick off to signed contract. The first six months cover the baseline, operational lever planning, and benchmark. The middle six months cover the IBM conversation, bundle scoring, and alternative scenario. The final three to six months close the contract.

Does workload migration off the mainframe really work as a lever?

Selective workload migration works when the target is credible and the workload is suitable. Batch jobs, analytics workloads, and modern Java applications can migrate to distributed or cloud targets at a cost that creates a credible alternative. Core transaction processing typically remains on the mainframe. The lever is the alternative, not the migration.

What is Tailored Fit Pricing?

Tailored Fit Pricing is the IBM annual commitment model. It prices mainframe software on a forward MSU baseline rather than the rolling R4HA peak. The customer commits to a yearly MSU figure and pays a fixed monthly rate. The model simplifies budgeting but can lock in a higher baseline than VWLC. Model both side by side before committing.

How does Redress engage on IBM mainframe licensing?

Redress runs IBM mainframe engagements as part of the wider IBM practice, with Piaras McDonnell leading the practice as a former IBM commercial executive. The work covers the SCRT baseline, the ILMT discipline reset, the operational lever plan, the alternative scenario, and the ELA renewal sequence. Always buyer side, never IBM paid.

How Redress engages on IBM

Redress runs IBM engagements as part of the wider Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. IBM practice lead Piaras McDonnell anchors the engagements.

Read the related benchmarking framework, about us, management team, locations, and contact pages.

Score your IBM mainframe MSU posture against the buyer side benchmark in under five minutes.
Open the Audit Readiness Check →
White Paper · IBM

Download the IBM Audit Defense Guide.

A buyer side reference on the IBM audit notice sequence, the ILMT discipline, the SCRT submission discipline, the MSU reduction levers, and the ELA renewal negotiation framework.

Independent. Buyer side. Written for CFOs, CIOs, and procurement leaders carrying IBM mainframe relationships. No IBM influence. No sales kickback.

IBM Audit Defense Guide

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

Open the Paper →
18 to 35%
MSU reduction
7
Reduction levers
3
Audit gates
500+
Enterprise clients
100%
Buyer side

The mainframe renewal closed at thirty one percent below the IBM opening proposal after a twelve month ILMT discipline reset and a workload shift program. The MSU consumption dropped fourteen percent on the operational side. The contractual lever added another seventeen percent on the price side.

Group CIO
European financial institution
More Reading

More from this practice.

IBM Hub →
IBM Mainframe CIO Advisory
IBM · Article
IBM Mainframe CIO Advisory
The CIO grade reference.
16 min read
Mizuho 71M Saving
IBM · Case Study
Mizuho 71M Saving
The Mizuho mainframe case.
20 min read
Financial Institution Case
IBM · Case Study
Financial Institution Case
Mainframe optimization.
16 min read
IBM Audit Defense
IBM · White Paper
IBM Audit Defense
The audit defense framework.
20 min read
IBM Advisory Services
IBM · Service
IBM Advisory Services
The IBM practice.
10 min read
Editorial photograph of enterprise contract negotiation strategy

Mainframe MSU overspend is a fixable problem.

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

IBM intelligence, monthly.

Mainframe MSU patterns, ILMT discipline wins, ELA renewal lessons, sub capacity signals, and the wider IBM commercial leverage signals across every program we run.