Home / Licensing / Subscription and Support on the Mainframe: What Renewal Buys
① Explainer · Metric and concept
On IPLA products you bought the license once, but the annual Subscription and Support charge keeps it current. It buys updates, fixes, and support, and it compounds 3 to 5 percent a year. The quiet line that becomes the biggest number in the contract.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →Many mainframe products are licensed under the one time charge model, where you pay once for a perpetual license. That is the IPLA structure on IBM, and most other publishers have an equivalent. Subscription and Support (S&S) is the recurring annual charge attached to that perpetual license. It buys three things: entitlement to new versions and releases, access to fixes and corrective service, and technical support. In short, the one time charge buys the right to run the software, and S&S keeps that software current and supported.
This separation is the source of a common misread. The license is perpetual, so teams treat the product as fully paid for and the S&S line as a minor afterthought. But S&S is recurring, it compounds, and across a portfolio of products it is frequently the larger lifetime cost. It deserves the same scrutiny at renewal as any Monthly License Charge stream.
Directional only, indexing year one S&S to 100 to show the mechanic. Publishers commonly apply a 3 to 5 percent annual increase as a contractual right. Held over a typical ownership horizon, that minor looking percentage becomes a different number entirely.
| Year | Index at 3% uplift | Index at 5% uplift |
|---|---|---|
| Year 1 | 100 | 100 |
| Year 3 | 106 | 110 |
| Year 5 | 113 | 122 |
| Year 10 | 130 | 155 |
Illustrative index, compounding only, not pricing. Real uplifts vary by contract and publisher.
At 5 percent compounding, the year ten S&S charge is roughly half again the year one charge for the same software, doing the same job. Nothing was added. The number grew because the escalation was never challenged. Across dozens of products with staggered renewals, the aggregate drift is large and almost invisible line by line, which is exactly why it survives. Capping or negotiating the uplift is one of the highest return, lowest disruption moves available on a mainframe estate.
S&S cost concentrates in three quiet failure modes. Shelfware: products no longer in real use that keep drawing S&S because nobody reconciled entitlement against actual deployment. Uncapped uplift: the default annual escalation accepted year after year without negotiation, compounding as above. And the lapse trap on the other side: dropping S&S to save money, then needing to reinstate it later, which commonly triggers reinstatement fees and back charges that can exceed what was saved. The pattern across all three is that S&S is managed passively, on auto renew, while every other line gets attention.
Work three levers. Scope: reconcile what you actually run against what you pay S&S on, and drop or consolidate genuine shelfware deliberately, accounting for any reinstatement risk. Uplift: negotiate the annual escalation and seek multi year caps rather than accepting the default, since this is where compounding is defeated. Timing and alternatives: align the S&S renewal with version migrations and any larger negotiation so it is leverage rather than an isolated invoice, and weigh third party support for stable products near end of life where it is viable. For products approaching withdrawal, also read how version migration cost is handled.
S&S is the annual coverage attached to IPLA one time charge products. It buys three things: entitlement to new versions and releases, access to fixes and corrective service, and technical support. It is the recurring charge that keeps an otherwise perpetual license current and supported. Without it, the license persists but the software freezes at its current level with no path to fixes.
IBM commonly increases S&S charges annually, frequently in the range of 3 to 5 percent, as a contractual right. The increase compounds, so the line that looks minor in any single year becomes a material multiple over a typical mainframe ownership horizon. Other publishers apply similar annual uplift mechanics to their maintenance and support streams.
Technically no. IPLA products carry a perpetual license, so an organization can run without active S&S. In practice, dropping S&S means running frozen versions with no entitlement to fixes or new releases and no vendor support, which is operationally untenable for most production mainframe software. The real decision is rarely whether to renew, but on what terms and at what scope.
The levers are scope, term, and uplift. Reconcile what you still actually run against what you are paying S&S on, since lapsed products and shelfware quietly keep charging. Negotiate the annual uplift and multi year caps rather than accepting the default escalation. Time the renewal against version migrations and any larger negotiation, and weigh third party support where it is viable for stable products near end of life.
Related concepts: IPLA one time charge licensing, reinstatement fees, and third party support options. Where these products live: z/OS licensing. Put it to work: IBM cost optimization.