① Journal · IBM
An IBM Subscription and Support line that rises a few points a year reads as housekeeping. It is not. An uncapped annual increase compounds into a structurally higher baseline that every future renewal builds on, and because no single year looks alarming, it is the increase buyers challenge least and pay longest.
The line item that never spikes is the one that costs the most.
IBM mainframe software bills on two recurring tracks. IPLA products carry a one time charge for the perpetual license and then an annual Subscription and Support charge that renews each year for support and version upgrades. The Monthly License Charge stack, the z/OS family and its programs, recurs every month and moves with rate changes and with installed or measured capacity. Both tracks share a feature buyers underweight: they go up on their own, year after year, whether or not anything in your estate changed.
The danger is not the size of any one increase. A Subscription and Support renewal that rises in the low single digits, or a Monthly License Charge that ticks up after a capacity bump, looks like the cost of doing business. It gets approved without a second look. But these increases compound. An uplift accepted once does not bill once; it raises the floor for the next year and the year after, and when an escalation clause sets the rate above inflation, the floor rises faster than the value you receive. That is the quiet compounder: small enough to wave through, structural enough to dominate a five year cost. Read this alongside our explainer on what subscription and support actually buys and the Monthly License Charge explained.
Worked · support line indexed to 100 at term start, compounding annually
| Annual uplift | Year 1 | Year 3 | Year 5 | Five year total vs flat 500 |
|---|---|---|---|---|
| 3 percent | 103.0 | 109.3 | 115.9 | 547 · plus 9 percent |
| 5 percent | 105.0 | 115.8 | 127.6 | 580 · plus 16 percent |
| 8 percent | 108.0 | 126.0 | 146.9 | 634 · plus 27 percent |
Worked illustration, not a quote. A flat estate paying five equal years would index to 500. At 8 percent compounding, the same estate pays the equivalent of 634, more than a quarter again, on a workload that never grew. The escalator, not usage, is doing the work.
Annual support renews on every entitled IPLA product, including ones bought for a project that ended and capacity added defensively years ago. You pay the escalator on tools you no longer run. Reconciling entitlement against actual use is the first place support cost falls without losing anything you depend on.
Support paid is not the same as support used.
An agreement with no ceiling on the annual increase lets the vendor set the rate each year. The single most valuable piece of language is a cap that ties the increase to a published index or a low fixed ceiling. Negotiated once, it protects every year of the term.
An uncapped rate is a rate the vendor controls.
Monthly License Charge follows the highest rolling four hour average. Capacity added for a peak that has passed keeps billing until it is tuned out. Sub-capacity discipline and zIIP offload hold the stack down so the monthly track does not compound on top of the support track.
Yesterday's peak is still on this month's bill.
Every year you accept the escalator, you raise the number the next agreement starts from. A baseline inflated by five years of unchallenged uplift and carried shelfware overpays for the term and the start of the one after it. Cleaning the baseline once benefits two terms.
A dirty baseline overpays twice.
④ The increase you wave through
A few points a year feels like nothing. Compounded across a term, it is the number. Cap the escalator, and the compounding stops working against you.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
Because the increase is built into the agreement, not driven by consumption. IPLA products carry an annual Subscription and Support charge that renews each year, and the Monthly License Charge stack escalates with rate changes and capacity. Many agreements also carry an escalation clause that lifts the renewal rate by a fixed percentage regardless of workload. An uplift on a flat estate is the clearest sign the cost is structural.
There is no single right number, but a defensible cap ties the annual increase to a published inflation index or a low single digit ceiling rather than an open ended vendor set rate. The point is to remove the uncapped escalator that compounds silently. A cap negotiated once protects every year of the term and lowers the baseline the next renewal builds on.
Often yes. Reconciling entitlement against actual use removes Subscription and Support paid on products and capacity you no longer run, sub-capacity discipline holds the Monthly License Charge stack down, and zIIP offload moves eligible work off general purpose engines. The work is identifying what you pay support on but do not use, then negotiating the baseline and the cap together. See our IBM license negotiation page.
No. The next renewal, or any point IBM wants something from you, resets the conversation. Reconcile entitlement, cap the increase, and clean the baseline, and the compounding that worked against you starts working for you. The cleaned baseline benefits every term after. Our IBM publisher hub maps the levers.
Related: Broadcom (CA) support escalation · the true cost of doing nothing · what subscription and support buys · IBM hub · IBM license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →