① Journal · Rocket Software · UniVerse and UniData
Rocket UniVerse and UniData are licensed on users and instances, not mainframe MSU, so the entitled count and the support model move the bill more than the list rate. Here are the seven levers that actually shift a U2 renewal, and how each one works.
The list rate is the negotiation people expect. The entitled count and the support model are the ones that decide the bill.
Rocket UniVerse and UniData, the MultiValue databases in the Rocket U2 family, sit apart from the capacity priced mainframe products: they are not licensed on MSU. The metrics are user and instance based, commonly counts of concurrent or named users, sessions, and deployed instances or cores, authorized through Rocket's licensing mechanism. That means the charge follows the count you are entitled on and the support or subscription tier, not a capacity figure or a flat list. Buyers expect to argue the rate card, but the number on a UniVerse or UniData renewal moves on truing the entitled count to actual use and deciding the support model, before the renewal is set.
Around the count sit the structural levers: the reconciliation of deployed instances and user counts against entitlement, the choice between a perpetual license with maintenance and a subscription as Rocket steers parts of its portfolio that way, version currency where the perpetual license keeps the last entitled release, and the uplift cap. Each is decided on independently validated deployment data, because an entitled count that no longer matches the estate, in either direction, drives both overspend and exposure. Read this with our Rocket Software price increase piece and the Rocket Software publisher hub.
What we commonly observe · the lever and how it shifts the U2 number
| Lever | How it works | What it moves |
|---|---|---|
| True the entitled count | Match users, sessions, and instances to actual use | The metric the whole bill rests on |
| Reconcile deployment vs entitlement | Check the license records against what is deployed | Both shelfware and exposure at once |
| Decide the support model | Perpetual with maintenance, or subscription | The cost basis for the term |
| Weigh version currency | Perpetual license keeps the last entitled release | Whether maintenance is worth keeping |
| Consolidate instances and cores | Retire idle test and development deployments | The instance and core count under license |
| Cap the renewal uplift | A hard ceiling on the increase against a fixed reference | The size of the jump at signing |
| Validate the deployment data | Independent check of the authorized count and usage | The accuracy of the number everything rests on |
Levers are what we commonly observe working across buyer side engagements, not statements of Rocket policy, and the effect of each depends on your estate. Your deployment data, entitlements, and contract govern the real number.
UniVerse and UniData bill on users, sessions, and instances, so the entitled count is the number the whole renewal rests on. Reconcile the deployed instances and user counts against the entitlements using the license authorization records, because estates drift: idle test instances accumulate and user counts shift away from what the contract was sized for. Truing the count exposes overspend on shelfware and any exposure where deployment has crept past entitlement, and corrects both before the renewal is set.
The count you do not check is the count you overpay on.
Rocket has been steering parts of its portfolio from perpetual licenses with maintenance toward subscription, and the right answer turns on whether the database footprint is stable or growing and how long you intend to run it. A stable, long lived estate often favors keeping a perpetual entitlement with maintenance; a growing or transitional one may favor subscription. Model it on the entitled count and the term, against keeping what you already own, not on the vendor default.
Take the model your roadmap favors, not the one being sold.
Idle test and development instances quietly inflate the count under license, so retire what you no longer run and consolidate where you can before the renewal is calculated. Then cap the uplift against a fixed reference so the increase at signing cannot run away. Weigh version currency too: the perpetual license keeps the last entitled release, so maintenance is worth keeping only where you need fixes and new versions.
Shrink the count first, then cap what is left.
④ Where the U2 number is moved
The list rate is the argument you expect. The count, the model, the cap are the ones that count. True the count, choose the model, cap the uplift.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
The U2 databases are not licensed on mainframe MSU. They use user and instance based metrics, commonly counts of concurrent or named users, sessions, and deployed instances or cores. The bill follows the entitled count and the support or subscription tier, not a capacity figure. See Rocket Software price increase patterns.
It depends. Rocket has been steering parts of its portfolio from perpetual with maintenance toward subscription, and the answer turns on whether the footprint is stable or growing and how long you will run it. Model it on the entitled count and term, against keeping the perpetual entitlement. See Rocket COBOL estate renewals.
Reconcile deployed instances, user counts, and cores against the contract entitlements using the license authorization records Rocket issues. Estates drift, so the real deployment data exposes both shelfware and any exposure where deployment has crept past entitlement. See cost optimization.
True the entitled count, reconcile deployment against entitlement, decide the support model, weigh version currency, consolidate idle instances, and cap the uplift. Our license negotiation service sets the structure and our Rocket contract review checks the terms.
Related: Rocket Software publisher hub · Rocket Software price increase patterns · Rocket contract review · Rocket COBOL estate renewals · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →