OPS/MVS licensing: capacity priced, portfolio negotiated.

OPS/MVS, in full OPS/MVS Event Management and Automation, is Broadcom (CA) z/OS automation. It monitors system messages and events and responds to them automatically through rules, keeping resources in their intended state and reducing the manual console work that operations would otherwise carry. Its System State Manager maintains a model of how resources should look and corrects drift, while its Automated Operations Facility lets sites program responses to events. Like most automation, it is deployed widely and quietly across the estate, and that breadth is the key to both its value and its licensing exposure.

OPS/MVS is licensed on capacity. Historically that has meant a MIPS or MSU based charge tied to the machines or LPARs where the product runs. Broadcom has been moving its mainframe customers toward Mainframe Consumption Licensing (MCL), which prices on measured MSU consumption reported through SCRT across the production environment, the same report IBM requires. Whether your OPS/MVS entitlement is a legacy capacity license or sits inside a consumption agreement depends on your contract, and the two carry very different renewal dynamics, so the first step is always to confirm which basis you are actually on.

The first driver is the licensed capacity baseline, since a MIPS or MSU figure set years ago and never revisited after hardware upgrades can sit well above current need. The second is the MIPS to MSU conversion, because moving a legacy MIPS entitlement onto an MSU or consumption basis can quietly inflate the licensed position if the conversion runs on the vendor's assumptions. The third is portfolio context: Broadcom commonly renews its mainframe products together, and uplift pressure on the whole CA estate flows through to OPS/MVS, which means the product cost is rarely settled in isolation from the rest of the portfolio.

Because OPS/MVS runs broadly, its exposure is mostly about scope. Common traps we see at pattern level:

OPS/MVS responds to the same levers that move the whole Broadcom portfolio, applied with the product's breadth in mind. The five that pay:

z/OS automation is a competitive category, so OPS/MVS does have credible alternatives, including IBM Z System Automation and BMC automation tooling. Displacement is genuine leverage but not a quick saving: automation policy and rules are custom, deeply embedded in operations, and risky to rebuild, so a switch is a project that must be costed against the migration effort and operational risk it carries. The more common move is consolidation, removing duplicate automation where two products cover the same ground, and using a credible displacement option as leverage in the Broadcom renewal rather than executing it under deadline.