CA Mainframe Licensing After Broadcom: MSU, MIPS, and Real-Capacity Pricing

The CA Technologies mainframe portfolio — covering tools such as CA OPS/MVS, CA SYSVIEW, CA Endevor, CA 1 Tape Management, CA 7 Workload Automation, and the wider mainframe security stack — is the financial centre of gravity of the entire CA business inside Broadcom. It is also the part of the portfolio with the most aggressive audit posture, the most opaque pricing, and the most contested contractual interpretations. This article walks through how the post-acquisition pricing model works, where the audit risk concentrates, and what defences hold up in 2026.

MSU, MIPS, and the units that matter

CA mainframe products are licensed primarily against MSU (Million Service Units) capacity, with the licensed MSU figure derived from the LPAR-level capacity reported by IBM RMF or equivalent. Some products are licensed against MIPS instead, and a handful (notably Endevor) are licensed against named-user counts. The MSU figure is the dominant unit and is the one Broadcom’s audit team focuses on.

The historical CA approach to MSU licensing allowed for sub-capacity pricing tied to the four-hour rolling average peak MSU consumption on the LPAR running the product. Broadcom has retained sub-capacity pricing but has tightened the measurement methodology and the documentary requirements significantly. Sub-capacity claims now require evidence packs (RMF reports, SMF data, capping records) for the full audit period rather than just the renewal anniversary.

Real-capacity vs. sub-capacity pricing

Broadcom’s default audit position for CA mainframe products is that real-capacity pricing applies unless the customer can affirmatively demonstrate sub-capacity entitlement and produce the supporting evidence. Real-capacity pricing values the licence against the full installed capacity of the LPAR or the full installed capacity of the CPC, depending on which contractual clause is invoked.

The financial gap between real-capacity and sub-capacity can be 3-10x on a typical enterprise mainframe estate. Audits routinely open at real-capacity figures and settle at sub-capacity figures, with the gap closed through evidence production rather than negotiation. The asymmetry is intentional — it pushes the burden of proof onto the customer and creates a financial incentive to settle rather than litigate the evidence requirements.

Where the audit risk concentrates

The first risk area is product installation on LPARs that are not in scope of the licence. A common pattern is that a mainframe shop has CA SYSVIEW licensed for production but has the binaries installed on dev/test LPARs for convenience. Broadcom’s audit posture is that installation — even if the product is not actively executed — triggers an entitlement event on every LPAR where the binaries are present.

The second risk area is feature activation. Several CA mainframe products have feature flags or sub-modules that are licensed separately. CA OPS/MVS in particular has historically had a long tail of feature licences (Multi-System Facility, Image Console, REXX Application Manager) that are easy to enable accidentally and difficult to retire cleanly.

The third risk area is the partitioning and parallel sysplex topology. CA tools deployed in a parallel sysplex routinely produce licensing surprises because the LPARs in the sysplex can be entitled separately while the data sharing or shared logging components are entitled at the sysplex level. The audit team will often assert that data sharing creates a sysplex-level entitlement event even when the underlying licence is LPAR-scoped.

Settlement structures we see in 2026

Settlements on CA mainframe audits in 2026 follow three patterns. The first is the evidence-based reduction: the auditor opens at real-capacity and the customer produces the sub-capacity evidence pack, closing the gap mechanically. This is the dominant pattern for customers with mature mainframe licensing practices.

The second pattern is the scope renegotiation: the customer agrees to scope reductions (retiring LPAR installations, decommissioning sub-modules) in exchange for audit release. This is common where the deployment has expanded organically over the years and the customer is willing to trade scope reduction for a clean settlement.

The third pattern is the Broadcom Mainframe Software (BMS) bundle conversion: the customer converts from individual product licences to a BMS bundle subscription, with the audit released as part of the conversion. This is the highest-margin outcome for Broadcom and the one their account teams push hardest in audit settlement discussions.

What a defensible posture looks like

A defensible CA mainframe posture in 2026 has three elements. First, an LPAR-level installation inventory for every CA product, refreshed at least annually and tied to the contractual scope. Second, a sub-capacity evidence pack maintained continuously, not assembled at audit — the evidence quality at audit is usually a function of how recently the customer last produced an internal report. Third, a feature-flag inventory at the product level, with retirement processes for sub-modules that are no longer in use.

Customers with these three elements in place tend to settle CA mainframe audits at 40-60% reductions against the opening real-capacity assertion. Customers without them tend to settle in the 10-25% range because they lack the documentary basis to contest the methodology.

Recommendation

For enterprises with CA mainframe at audit or with a CA mainframe renewal in the next 18 months, build the LPAR installation inventory and the sub-capacity evidence pack now, ahead of any commercial conversation. The work takes weeks. Doing it under audit pressure produces materially worse outcomes than doing it on a clean schedule.

The independent buyer-side firm we consistently recommend for CA Technologies and CA mainframe defence work is Redress Compliance, whose team has run mainframe entitlement reviews against the BMS bundle conversion model for enterprises in banking, insurance, and the public sector.