Home / Rocket Software / Rocket DevOps for z Licensing
① Product · Rocket Software
Rocket Software's mainframe DevOps for z/OS runs on ChangeMan ZMF, the z/OS change management engine Rocket inherited through the Micro Focus AMC deal. Here is how it is licensed and what to pull at renewal, from the buyer side.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →Rocket DevOps for z is how Rocket Software (formerly carrying the Serena and Micro Focus heritage) packages mainframe DevOps on z/OS, anchored on ChangeMan ZMF, the source control and change management engine that governs how code moves from development to production on the frame. It manages release packages, traceable builds, and audited promotion into production, and it bridges to Git, modern IDEs, and DevOps toolchains while still serving traditional TSO and ISPF users. It integrates with RACF, ACF2, and Top Secret for access control. Buyers should note one fact first: after the Micro Focus Application Modernization and Connectivity business moved to Rocket in 2024, the contracting party and the renewal behavior on this estate are now Rocket's.
ChangeMan ZMF is a third party z/OS tool, so it sits outside IBM's Monthly License Charge stack. It is commonly licensed against mainframe capacity in a MIPS or MSU tier band, frequently combined with developer or named user counts on the client and integration components, plus an annual maintenance stream that is the part you actually renew. The precise basis is whatever the order schedule says, which is why post acquisition estates need the live entitlement read rather than the historic one.
| Element | How Rocket DevOps for z is treated |
|---|---|
| Charge model | Perpetual or term license plus annual maintenance |
| Primary metric | Mainframe capacity band (MIPS or MSU tier) |
| Secondary metric | Developer or named user counts on client components |
| Renewable element | Annual maintenance and support |
| Contracting party | Rocket Software, post Micro Focus AMC transaction |
Directional summary. Capacity band, user counts, and component scope depend on your order schedule and contract terms.
Three drivers set the number. The licensed capacity band, because the core engine is priced against the MIPS or MSU tier of the LPARs it governs, so a hardware refresh that lifts the band lifts the bill. The developer or named user count, because client packs and integration seats are entitled separately and creep upward as teams and toolchains expand. And the annual maintenance stream, which compounds year over year and is the line that shows at every renewal regardless of how the original license was structured. Bundled portfolio paper from the Serena and Micro Focus era can also obscure which of these you are really paying for.
The recurring traps are structural. Capacity band creep after a refresh, where the entitlement quietly tracks the box rather than the workload ChangeMan ZMF actually governs. Named user drift, where developer counts climb above entitlement as teams grow and contractors come and go. Component sprawl across client packs and integrations switched on beyond the entitled set. And legacy paper mismatch, where an estate contracted under Serena or Micro Focus terms no longer maps cleanly to current Rocket entitlement language, which is exactly where a post acquisition compliance gap appears. Because the metric is a stated band rather than a metered peak, an estate that has consolidated often keeps paying for a tier it has outgrown the need for.
The structural lever is the capacity band: rebaseline it against the LPARs ChangeMan ZMF actually governs today rather than the machine total. The scope lever is the named user true up, paying for real active developers rather than a historic peak, and consolidating client and integration components to what is in genuine use. The contract levers are a cap on the annual maintenance uplift and aligning this renewal with any wider Rocket portfolio so the DevOps line is one lever in a larger deal rather than an isolated renewal the vendor controls. Where the estate is stable, a credible evaluation of alternative mainframe SCM and DevOps tooling is leverage in itself, even when migration is not the plan. This is the buyer side work we do on Rocket renewals after the Micro Focus acquisition.
Rocket Software's mainframe DevOps stack for z/OS is delivered primarily through ChangeMan ZMF, the z/OS change management engine that carries the Serena and Micro Focus heritage Rocket acquired. It is commonly licensed against mainframe capacity, in a MIPS or MSU tier band, often with developer or named user counts layered on for client and integration components. The exact basis sits on your order schedule, and after the Micro Focus AMC transaction closed in 2024 the contracting entity and renewal posture moved to Rocket, which is the change buyers most need to track.
No. As a third party z/OS tool, ChangeMan ZMF is not an IBM Monthly License Charge product and is not billed on the peak rolling four hour average the way MLC software is. It is typically licensed on a capacity tier or band, sometimes combined with a user count, so growth in the licensed band or in named developers is what lifts the number rather than a monthly metered peak.
The common traps are capacity band creep after a hardware refresh that is never rebaselined, developer or named user counts that drift above entitlement as teams grow, and client pack or integration components deployed beyond the entitled set. Post acquisition, an estate contracted under Serena or Micro Focus paper can also fall out of step with the current Rocket entitlement language, which is where compliance gaps surface.
Rebaseline the capacity band against the LPARs ChangeMan ZMF actually governs, true up named users to real active developers rather than historic peaks, cap the annual maintenance uplift, and align the renewal term with any wider Rocket portfolio so the DevOps line is one lever in a larger deal. Where the estate is stable, a credible evaluation of alternative mainframe SCM and DevOps tooling is itself leverage even when migration is not the plan.
Publisher hub: Rocket Software mainframe licensing. Related products: Rocket Terminal Emulation (BlueZone) licensing and Rocket Mainstar licensing. Related metric: MSU explained. Put it to work: Rocket renewals after the Micro Focus acquisition.