Banks run core systems on IBM Z, where monthly license charges follow peak capacity. The four hour rolling average decides the bill. Capacity discipline is the lever that controls cost.
IBM mainframe software bills on monthly license charges driven by peak capacity, where the four hour rolling average sets the number.
Key takeaways
Monthly license charges meter mainframe software by capacity in MSU, billed each month against your peak usage. IBM's z/OS product page anchors the software stack that MLC prices, where the bill follows the busiest sustained window rather than average load.
MLC is a capacity charge. You are billed for the peak your workloads reach, not for steady state, which makes the timing of demand the cost driver.
An MSU, or millions of service units, is the capacity unit IBM uses to size mainframe consumption. More MSU at peak means a higher monthly charge.
Core software such as z/OS, Db2, CICS, IMS, and MQ commonly bill on MLC, so the peak applies across the regulated banking stack.
The four hour rolling average, often shortened to 4HRA, decides the bill because IBM bills the highest sustained four hour window in the month. IBM's software licensing overview describes sub capacity reporting, where a brief spike matters less than a sustained peak.
Mainframe pricing models compared
| Model | Basis | Best fit |
|---|---|---|
| MLC sub capacity | Peak 4HRA in MSU | Stable, capped workloads |
| Tailored Fit Pricing | Annual consumption | Growing or variable load |
| Container Pricing | Isolated workload | New apps and modernization |
| Soft capping | Defined MSU limit | Cost discipline on peak |
| IPLA one time charge | Owned license | Tools and utilities |
Because the average smooths short spikes, capacity management aimed at the four hour window is the most direct lever on the monthly number.
Banks cut the bill by managing the metered peak through soft capping and workload scheduling, never by cutting capacity the regulator expects you to hold. Discipline on timing protects both cost and resilience.
Soft capping sets a defined MSU limit so partitions cannot drive the peak above a planned level, which controls the metered charge.
Protect resilience by capping only what is safe to cap and by keeping headroom for failover. Cost control must never undercut regulatory obligations.
A bank should model Tailored Fit Pricing whenever its load is growing or variable, because the consumption model can beat peak based MLC for unpredictable demand. IBM Passport Advantage agreements govern how the commitment is structured.
Tailored Fit Pricing trades the monthly peak for an annual consumption commitment. It rewards predictable growth but needs an accurate baseline.
Container Pricing helps when you add new workloads, because it can isolate them from the general MLC peak and price them on their own terms.
Keep reporting audit ready by maintaining accurate sub capacity data and reconciling it every month, because the regulated environment demands defensible numbers.
Sub capacity reports, capping policies, and the monthly peak history matter most. They are the evidence that supports both your bill and an audit.
The standard advice from many account teams is that the way to cut a mainframe bill is to negotiate a deeper discount on your monthly license charges. We disagree. In most banking estates we reviewed, the monthly peak was set by a single batch window that ran for only a few hours, and disciplined soft capping cut metered MSU by 8 to 18 percent with no service impact. The buyer side move is to manage the four hour rolling average through capping and scheduling first, then model Tailored Fit Pricing against the real profile. Capacity discipline lowers the number the discount is applied to, which compounds in your favor every single month.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
“On the mainframe you are billed for a four hour peak, not for the month. Manage the window and the bill follows.Morten AndersenCo Founder, Redress Compliance
White Paper · IBM
IBM Z Mainframe Licensing Negotiation
How to cut IBM Z mainframe cost: Tailored Fit Pricing, MLC and IPLA mechanics, MSU optimization, and the sub capacity levers that hold at renewal. Read it free.
Monthly license charges meter mainframe software by capacity in MSU and bill each month against your peak usage rather than your average load.
An MSU, or millions of service units, is the capacity unit IBM uses to size mainframe consumption. More MSU at peak raises the monthly charge.
IBM bills the highest sustained four hour window in the month, so capacity management aimed at that window is the most direct lever on the bill.
Soft capping sets a defined MSU limit so partitions cannot push the peak above a planned level, which controls the metered monthly charge.
Model it whenever load is growing or variable. The consumption model can beat peak based MLC, but it needs an accurate annual baseline before you commit.
Container Pricing helps when you add new workloads, because it can isolate them from the general MLC peak and price them on their own terms.
Manage the metered peak through soft capping and scheduling, and cap only what is safe, keeping headroom for failover and regulatory resilience.
Sub capacity reports, capping policies, and the monthly peak history are the evidence that supports both your bill and an audit in a regulated bank.
A buyer side view of how monthly license charges meter mainframe software, where the four hour rolling average bites, and how banks cut the bill.
See IBM advisory →Buyer side only. No vendor commissions. We sit on your side of the table.
