Rocket Enterprise Suite: licensed by seats and cores, not the MSU.

Rocket Enterprise Suite is the modernization toolchain Rocket acquired from Micro Focus, built to maintain, test, and rehost COBOL and PL/I applications with a modern development experience. Enterprise Developer is the IDE for editing and debugging the code in Eclipse or Visual Studio. Enterprise Server is the runtime that executes those applications off the mainframe on Linux, Windows, Unix, containers, or cloud. Enterprise Analyzer and the test tooling round out the analysis and quality layer. Together they are how an organization either keeps mainframe code under modern development or moves it onto distributed infrastructure.

This is distributed software licensing, not mainframe capacity licensing. Enterprise Developer is typically licensed per authorized user, so the cost driver is the number of developers entitled to the IDE. Enterprise Server is typically licensed by server capacity, measured in cores or vCPU on the machines where the runtime executes. Analyzer and test components carry their own named user or capacity bases. Rocket inherited a mix of perpetual and subscription entitlements from Micro Focus and is steering the portfolio toward subscription, so the renewal increasingly turns on subscribed seats and subscribed cores rather than a one time purchase.

Because seats and cores drive the bill, the contract terms around counting and the perpetual to subscription move matter most. See what audit clauses allow.

The first driver is the authorized user count for Enterprise Developer, which tends to be sized for a peak project team and rarely trued down once a modernization push slows. The second is the deployed core or vCPU count for Enterprise Server, which grows as runtimes spread across production, test, and disaster recovery, and can balloon in container and cloud deployments where scaling out multiplies effective cores. The third is the subscription transition, since moving from perpetual licenses with maintenance to subscription changes the cost shape and is the moment to true seats and cores down to real need rather than carry inflated counts forward.

Distributed modernization tooling has its own exposure pattern, all about counting seats and cores. Common traps we see at pattern level:

The levers all work on the seat count, the core count, and the contract basis. The five that pay:

Application modernization tooling is a contested market, and the Enterprise Suite is itself often part of a move away from mainframe license costs. IBM and several specialist modernization vendors offer competing COBOL development, rehosting, and refactoring paths, so a credible alternative exists for both the development and the runtime layers. The switching cost is in retraining developers, reworking build and deployment pipelines, and revalidating the rehosted applications, so a full replacement is a managed program rather than a quick swap. The practical play is to price a credible alternative, use it to discipline the Rocket renewal, and weigh an actual move against the rework across your application estate. For the wider Natural and COBOL decision, see Natural vs COBOL modernization.