① Journal · Rocket Software · BlueZone · Renewal
Rocket BlueZone is licensed per seat, not on MSU, so the renewal turns on the seat count, the named versus concurrent model, and whether you keep perpetual entitlement or are moved to subscription. The number moves when you true the seats down and treat the conversion as a choice. Five levers move it.
BlueZone is priced per seat, not on capacity. True the seats down and you move the price.
Rocket BlueZone, the terminal emulation product Rocket Software has consolidated alongside RUMBA, HostExplorer, EXTRA!, Reflection, and Passport under its Rocket Secure Host Access line, is licensed per seat rather than on mainframe MSU (Million Service Units). Seats are entitled as named users or concurrent users, and the line is moving from perpetual licenses with annual maintenance toward subscription. That puts a BlueZone renewal in a different category from the capacity priced products on the rest of the estate. The number follows the seat count, the licensing model, and the perpetual versus subscription question, and the buyers who move it arrive with the seat count trued to active users rather than carrying entitlement that has not been reconciled in years.
The pattern we commonly observe across acquired emulation portfolios is seat entitlement that has drifted far above active users, a named user model where concurrent would cost less, and a subscription conversion presented as the default at renewal. The largest lever is the seat count itself, supported by the named versus concurrent choice. Around them sit perpetual retention, the consolidation question, and a credible alternative emulator path. Read this with our piece on Rocket Software audit activity and the Rocket Software publisher hub.
What moves the number on a Rocket BlueZone terminal emulation renewal · the lever and its effect
| Lever | How it works | Effect on the number |
|---|---|---|
| Seat true down | Reconcile entitled seats against active users and drop the inactive ones | Lowers the seat count the renewal is priced on, the largest lever |
| Named vs concurrent | Switch to concurrent licensing where access is shift based or intermittent | Cuts the billed count below the headcount |
| Perpetual retention | Keep perpetual entitlement plus maintenance rather than convert to subscription | Preserves a lower run rate on a stable seat base |
| Consolidation terms | Negotiate the move to Rocket Secure Host Access rather than accept it imposed | Holds price and rights through the portfolio consolidation |
| Alternative emulator path | A credible competing or web based emulator sits behind the renewal | Caps the renewal against a real switch |
These are levers and patterns we commonly observe on Rocket terminal emulation renewals, not guaranteed outcomes. The effect of each depends on your contract, seat model, and access patterns; reconcile your own usage data before relying on any figure.
BlueZone is licensed per seat, and seat entitlement on an acquired emulation portfolio drifts far above active users as roles change and access moves to other channels. Reconcile entitled seats against who actually connects, using the licensing daemon usage data where available, and drop the inactive entitlement before the renewal prices it. This is the largest and least disputable lever when the usage data is yours. See our explainer on contractual vs consumed entitlement.
License the users who connect, not the headcount.
Named user licensing entitles each individual; concurrent licensing entitles simultaneous sessions. Where mainframe access is shift based, intermittent, or shared across a pool, concurrent can cut the billed count well below the named headcount. Map how your users actually connect, then choose the model that fits rather than carrying the model the contract was originally written under. The right model is a structural saving, not a one time discount. See our piece on Rocket Software audit activity.
Concurrent beats named when access is intermittent.
Rocket is moving terminal emulation from perpetual plus maintenance toward subscription, usually presented as the default at renewal. Model both over the planning horizon: a stable, long lived seat base often costs less on retained perpetual plus maintenance, while a shrinking base may favor subscription flexibility. Negotiate the consolidation onto Rocket Secure Host Access rather than accept it imposed, and keep a credible alternative emulator path on the table. See our piece on pricing after a vendor is acquired.
The conversion is negotiable, not inevitable.
④ Where the BlueZone renewal is won
A BlueZone renewal follows seats, not capacity. The number moves when you true the count. Reconcile the seats, fit the model, choose the conversion.
Typical renewal reduction
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
BlueZone, consolidated alongside RUMBA, HostExplorer, EXTRA!, Reflection, and Passport under Rocket Secure Host Access, is licensed per seat rather than on mainframe MSU. Seats are entitled as named or concurrent users, and the line is moving from perpetual plus annual maintenance toward subscription. A renewal turns on the seat count, the named versus concurrent model, and whether you hold perpetual entitlement or are being moved to subscription, not on the rolling four hour average.
The seat count, because BlueZone is licensed per seat and entitlement rarely tracks down as access patterns change. Truing the seat count to active users is the largest lever, and switching from named to concurrent can cut the count further where access is shift based. Beyond that, retaining perpetual entitlement rather than converting to subscription preserves a lower run rate, consolidation can be negotiated rather than imposed, and a credible alternative emulator path caps the renewal.
Not automatically. Rocket, like many vendors absorbing acquired portfolios, is moving terminal emulation from perpetual plus maintenance toward subscription, usually presented as the default. Whether it serves you depends on the math: a stable, long lived seat base often costs less on retained perpetual plus maintenance, while a shrinking base may favor subscription flexibility. Model both over the planning horizon and treat the conversion as a negotiable choice. See AMI Data for IMS renewal negotiation.
We reconcile entitled seats against active users from the usage data, test named versus concurrent against your access patterns, model perpetual retention against the subscription conversion, and build the credible alternative before the vendor controls the clock. Our Rocket Software cost optimization service right sizes the seat base and our license negotiation service runs the renewal from the buyer side.
Related: Rocket Software publisher hub · Rocket Software audit activity · pricing after a vendor is acquired · Rocket cost optimization · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →