Rocket Mainstar: storage and Db2 tooling priced on the capacity it runs against.

Rocket Mainstar is a family of systems optimization and storage aware data management tools for z/OS, Db2, and IMS. The estate centers on Rocket Mainstar MXI, which gives operators instant access to z/OS configuration and resource information with historical reporting and trending, and the Database Backup and Recovery (DBR) solutions for Db2 and IMS, which deliver storage aware subsystem backup and recovery, alongside Volume Clone and Rename for cloning Db2 subsystems in minutes. Rocket acquired the MXI line in 2003 and Mainstar Software Corporation in 2016, then folded both under the Rocket Mainstar brand. This is operational and resilience tooling, the kind that is deeply embedded and rarely cut, which is exactly why its licensing deserves the same scrutiny as any sticky product.

Rocket Mainstar is typically licensed on capacity. The common unit is MSU, the IBM measure of processor capacity, so the entitlement is built on the MSU rating of the machines or LPARs where each Mainstar component is authorized, carried under a multi year agreement rather than a charge per backup or per query. Because Rocket assembled this estate through acquisition, metric definitions can vary across the individual products, so the exact metric and authorized capacity in your schedules are what govern. Rocket has also grown into a very large mainframe and infrastructure portfolio, having absorbed the Micro Focus mainframe assets and the ASG catalog, and increasingly negotiates across the whole estate rather than product by product.

Directional, pattern level. Confirm your own metric, components, and authorized capacity against the Rocket schedules before modeling a renewal.

The dominant driver is the MSU capacity of the environment each Mainstar component is authorized to run against. Because the price tracks that footprint rather than activity, a large or recently upgraded z/OS or Db2 estate can carry a higher entitlement than the actual backup, recovery, or monitoring workload would justify. The second driver is component scope: MXI, the DBR solutions, and Volume Clone and Rename are distinct products, so paying for components you do not use is a real and common cost. The third is the surrounding Rocket agreement structure and any uplift or escalator terms, which Rocket can apply across a bundled portfolio in ways that obscure what each Mainstar component actually costs.

Mainstar exposure sits in the capacity footprint and the component set. Common traps we see at pattern level:

The entitlement is built on capacity and component scope, and Rocket negotiates broad, so the levers work all three. The five that pay:

The functions Mainstar performs have credible alternatives: IBM and Broadcom (CA) storage and Db2 utilities cover overlapping monitoring, backup, and recovery ground, and a shop can evaluate a switch. But storage aware recovery and the operational visibility MXI provides are deeply rehearsed into runbooks, and the cost of disrupting recovery dwarfs most licensing savings, so a switching threat is real but heavy and should only be raised when genuinely prepared. For most estates the more reliable wins are aligning authorized capacity to the real footprint, trimming unused components, and pricing Mainstar inside the wider Rocket negotiation where the leverage actually sits.