① Journal · Hardware and cost
IBM shipped the z17 in June 2025, and the upgrades are now moving through enterprise estates. Buyers tend to treat a hardware refresh as a tin swap the infrastructure team runs. It is a licensing event. New MSU ratings, a faster processor that invites capacity creep, and renewals that the project can be used to reopen all ride on the z17 move. Here is what it means for the software bill, and the levers to pull.
The hardware team runs the upgrade. The software bill rides along with it.
IBM announced the z17 in April 2025 and made it available from June 18, 2025, built on the new Telum II processor with a large generational jump in general purpose performance. A year on, the refresh is reaching the estates that plan their capital on the platform's cadence. For most organizations the upgrade is scoped as an infrastructure project: order the machine, migrate the workloads, retire the old frame. The software that runs on it is treated as a constant that simply moves across.
That framing leaves money on the table. On the mainframe the software charge is tied to capacity, and a new generation changes the capacity picture in ways that are easy to miss. The MSU rating tables are updated for the new models, so the same workload can be rated differently on z17 than on the machine it replaces. A faster processor tempts consolidation and headroom that lift the rolling four hour average. And a hardware project is one of the rare moments when both IBM and the tools vendors are motivated, which makes it leverage. Read this alongside our securing price holds across hardware refreshes guide and our cost optimization service.
Four cost surfaces a hardware refresh changes · each one is a negotiation surface too
| Cost surface | What the z17 move changes | Why it matters to the bill |
|---|---|---|
| MSU ratings | New model capacity ratings apply to the z17 generation | Sub-capacity charges follow the rating, so the same work can bill differently |
| R4HA peak | Consolidation onto fewer, faster engines reshapes the peak window | A higher rolling four hour average raises monthly license charges directly |
| Tailored Fit baseline | A baseline set or reset around the upgrade locks in the new consumption | An inflated transition baseline is overpaid for the life of the term |
| Tools and ISV contracts | Capacity based tool licenses revalue against the new machine | Broadcom, BMC, and Compuware costs can move with the capacity they price on |
Effects vary by workload mix, configuration, and the terms in force at the time of your move. Confirm the current z17 generation pricing mechanisms with the vendor at the point of upgrade rather than assuming a prior cycle's behavior carries over.
A faster machine should not mean a bigger bill. Unless you let it.
When IBM ships a new generation, it commonly publishes pricing mechanisms that recognize the newer technology, so that a customer moving to the latest machine is not penalized purely for the raw capacity increase the new processor delivers. The intent is that a like for like workload should not cost more simply because it now runs on a faster engine. That benefit, however, is not automatic in the way buyers assume. It has to be confirmed for the z17 generation at the time of your move, modeled against your own workload rather than the headline, and captured in the agreement rather than left for the vendor to apply or not.
The failure pattern is predictable. The infrastructure team completes a clean upgrade, the software simply carries across at the old terms, and nobody models whether the new ratings and the transition mechanism were actually applied to the renewal that follows. Months later the consumption profile has quietly climbed, the Tailored Fit baseline was set from a transition period that included migration overhead, and the saving the technology was supposed to deliver never reached the invoice. The discipline is to treat the upgrade as a licensing project with its own workstream. Our MIPS to MSU conversion explainer covers the rating mechanics underneath this.
Do not assume the headline performance number is your number. Map your actual peak workloads onto the z17 rating tables and see how each licensed product is affected before you sign anything tied to the new machine.
Your estate, not the brochure, sets the cost.
Confirm the current z17 generation pricing mechanism and make sure the agreement captures it. A benefit the vendor could apply but is not contractually bound to apply is a benefit you may never see.
If it is not in the contract, it is not yours.
Never let a Tailored Fit or renewal baseline be set during the migration period, when overhead and dual running inflate consumption. Reduce the peak first, then anchor the new agreement to the cleaned profile.
A baseline set mid migration is overpaid for years.
A hardware refresh motivates IBM and the tools vendors at the same time. Align the software review with the upgrade to secure price holds across the refresh and reset metrics that no longer fit the estate.
Two motivated vendors is leverage you do not get twice.
A faster machine tempts consolidation and defensive headroom that lift the R4HA. Decide capacity deliberately, hold the peak where deferrable work allows, and do not let the upgrade quietly raise the number your software bills on.
New capacity is a choice, not a default.
⑤ The discipline that pays
A refresh is scoped as hardware. The cost that moves is software. Put a licensing workstream on the upgrade.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
Yes, in both directions. A refresh is a licensing event. New MSU rating tables mean the same workload can bill differently, while a faster processor invites capacity additions that lift the R4HA. Whether the move lowers or raises the bill depends on how the transition is managed, not on the hardware alone.
IBM commonly publishes mechanisms that recognize newer technology so customers are not penalized for the raw capacity jump. Confirm the current terms for the z17 generation at your move, model your own workload against the new ratings, and make sure the benefit is captured in the agreement, not left on the table.
A refresh is one of the few moments both IBM and the tools vendors are motivated, which makes it leverage. Aligning the software review with the z17 move secures price holds across the refresh, resets metrics that no longer fit, and stops the capacity jump inflating sub-capacity charges and baselines.
When the upgrade is run as hardware only, the baseline gets set during migration overhead and the transition mechanism is never confirmed in writing. The saving the technology should deliver never reaches the invoice. See our cost optimization service.
Related: securing price holds across hardware refreshes · capacity on demand · the MIPS to MSU conversion question · renewal advisory
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →