Broadcom Software (CA) Mainframe Licensing: CIO Playbook for 2025–2027

The Broadcom CA Mainframe Software Landscape: Understanding What You Own and What It Costs

Broadcom's CA Technologies mainframe software portfolio — acquired in 2018 — is one of the most comprehensive and deeply embedded vendor relationships in enterprise IT. The product set spans mainframe systems management (CA Mainframe Software Manager), DevOps and SCM tooling (CA Endevor, CA InterTest), performance and capacity management (CA Detector, CA SPA), database utilities, security (CA ACF2, CA Top Secret, CA RACF), and operations intelligence — with many large enterprises running 20–40 distinct CA products across their mainframe estate. For a complete overview of what this entails at the commercial level, our Broadcom Knowledge Hub provides the full context of how Broadcom manages this portfolio strategically.

The commercial model for Broadcom CA mainframe software is capacity-based: most products are licensed based on the number of MSUs (Million Service Units) — the standard IBM measurement of processor capacity on z/OS mainframe environments — or MIPS (Millions of Instructions Per Second), an older equivalent measure. MSU capacity drives two distinct cost dynamics. First, if your organisation's mainframe workloads grow and MSU consumption increases above the licensed baseline, Broadcom bills for the excess — typically through annual true-up mechanisms with penalty pricing for overruns. Second, even if consumption remains flat, Broadcom's standard renewal approach includes annual escalator clauses of 5–7%, meaning the cost per licensed MSU increases at every renewal regardless of workload changes. Over a three-year contract term, a 6% annual escalator compounds to an 19% cumulative cost increase on a flat consumption baseline.

The product concentration in most large-enterprise CA mainframe relationships creates significant negotiating complexity. Organisations running 20 or more distinct CA products face a portfolio where some products are deeply operationally embedded (decommissioning would require significant project effort), some are partially used (features licensed but not exploited), and some are legacy products maintained for operational stability rather than active value delivery. Broadcom's renewal teams are sophisticated in their understanding of this product dependency hierarchy — and price accordingly, with highest prices on the most deeply embedded products and more flexibility on peripheral tools. Conducting an honest assessment of your product dependency depth before renewal negotiations is the foundational step for any effective Broadcom mainframe advisory engagement.

MIPS/MSU Pricing: How the Model Works and Where the Commercial Traps Are

Understanding the mechanics of MIPS/MSU-based pricing is essential for any CIO or IT procurement leader managing a Broadcom CA mainframe relationship. The fundamental structure works as follows: each CA product is priced at a rate per MSU of the licensed capacity tier. Most large enterprises run on multi-year agreements where the licensed MSU level is fixed at the contract's start, with annual escalator increases applied to the per-MSU price. True-up mechanisms allow Broadcom to bill for consumption above the licensed tier on an annual or quarterly basis, at rates that are typically higher than the base tier pricing — creating a structural incentive for enterprises to over-license as a buffer against unplanned workload growth.

The specific traps in MSU-based pricing include the ratchet mechanism: in many CA mainframe agreements, MSU consumption that exceeds the licensed tier triggers a permanent step-up in the licensed level — meaning that a temporary workload spike during a peak period (end-of-year batch processing, for example) can permanently elevate the licensing baseline with no ability to step back down when the workload returns to normal. The Four-Hour Rolling Average (4HRA) — IBM's methodology for measuring peak MSU consumption — can be triggered by brief computational peaks that do not represent sustained operational capacity. Enterprises with variable batch workloads or seasonal processing peaks must actively manage their 4HRA exposure to avoid triggering inadvertent licensing step-ups.

Broadcom's Mainframe Consumption Licensing (MCL) programme, introduced as an alternative pricing model, addresses some of these traps by providing an all-you-can-eat subscription across the Broadcom mainframe portfolio at a fixed annual fee, with consumption below the baseline rolling over to the next true-up period. MCL is compelling for enterprises with growing mainframe workloads or unpredictable consumption patterns where the ratchet mechanism in traditional capacity agreements creates unacceptable budget risk. However, MCL pricing is typically set at a premium to traditional capacity pricing — Broadcom prices the certainty and consumption flexibility at a material cost above what a well-negotiated traditional agreement would deliver for enterprises with stable workloads. The right model for each organisation depends on workload trajectory, budget predictability requirements, and the negotiated price point for each option.

Contract Structure: Anatomy of a CA Mainframe Agreement

Most large-enterprise CA mainframe contracts are structured as multi-year agreements — commonly three to five years — with annual price increases, defined product schedules, and true-up provisions. The product schedule is one of the most commercially sensitive elements: it defines exactly which CA products are included, at what MSU tier, and at what per-MSU price for each year of the contract. Enterprises that do not maintain a current, validated understanding of their product schedule often discover discrepancies at renewal — products at higher-than-necessary MSU tiers, products that have been technically end-of-life'd by Broadcom but remain on the schedule at full price, and maintenance inclusions for products the organisation no longer operates.

Annual escalator provisions deserve particular CIO attention. A contract signed today at a 7% annual escalator represents a compounded 40% cost increase by the end of a five-year term, for an estate where the operational value delivered by the software has not changed. Negotiating a CPI-linked or fixed-ceiling escalator (typically achievable at 3–5% in competitive renewal situations) is one of the highest-value interventions available in any CA mainframe renewal. The challenge is that Broadcom's standard renewal process anchors to the contracted escalator, and reducing it requires specific negotiation focus and typically the leverage of a competitive alternative — whether a BMC Technologies competitive assessment, a mainframe modernisation programme that would reduce the licensed CA footprint, or engagement with Broadcom's ELA/PLA programme that provides different commercial structures. Download our white papers library for additional frameworks covering enterprise software contract negotiation.

Negotiation Strategy: Building Your Position for CA Mainframe Renewal

Effective CA mainframe renewal negotiation requires preparation across three dimensions: consumption analysis, product rationalisation, and competitive positioning. On consumption analysis, the starting point is a validated MSU consumption history — typically 24–36 months of 4HRA data — that establishes the actual peak, average, and trend consumption for the entire estate. This data frequently reveals that the licensed MSU tier is higher than actual peak consumption, either because the tier was set conservatively at the previous renewal or because workloads have declined since the last contract period. Bringing a documented analysis of actual versus licensed consumption to the negotiation table gives procurement teams the factual foundation for a tier reduction request — one of the most impactful single negotiation lever available, as reducing the licensed MSU tier directly reduces the annual cost base before any per-unit pricing discussion begins.

Product rationalisation addresses the common problem of CA estates that have grown through licence accumulation rather than strategic acquisition — products added for specific projects that are now complete, products replaced by more modern alternatives (including Broadcom's own newer offerings), and products where the operational team no longer has the expertise to maximise utilisation. A formal product rationalisation exercise typically identifies 10–20% of licensed products that can be removed from the renewal schedule without operational impact, directly reducing contract value. Broadcom will resist removing products from the schedule — each removed product reduces their revenue — but with documented evidence of non-usage and a credible alternative migration plan, rationalisation of genuinely unused products is achievable in most renewal negotiations.

Competitive positioning for CA mainframe renewals is structurally different from VMware negotiations because the mainframe software market is more concentrated — BMC Technologies is the primary alternative for most CA product categories, with IBM's own mainframe software portfolio as a secondary alternative for specific security and operations tools. A formal BMC competitive assessment, conducted with BMC's direct account team, provides the pricing reference data and technical comparison information that gives Broadcom's commercial team the commercial incentive to deliver their best terms. Most organisations that engage Broadcom without a documented BMC evaluation receive standard programme pricing; those with a current BMC proposal in hand consistently achieve 15–25% better outcomes on per-MSU pricing. To understand how our Broadcom mainframe advisory team supports CA renewal negotiations, book a confidential call with our specialist team.

The Portfolio Licensing Agreement (PLA) Option: When Does It Make Sense for Mainframe?

Broadcom's Portfolio Licensing Agreement — combining CA mainframe, VMware, and Symantec products under a single enterprise agreement — is actively promoted to organisations with material spend across multiple Broadcom product families. For enterprises where CA mainframe software represents a significant spend alongside VMware virtualisation infrastructure, the PLA offers a potential path to consolidated commercial terms with portfolio-level discounts that exceed what is achievable through individual product family negotiations.

The economics of a PLA for mainframe-heavy organisations depend critically on two factors: the balance of spend between CA mainframe and other Broadcom product families, and the organisation's planned VMware posture over the PLA contract term. PLAs are structured around a committed annual spend floor across the combined portfolio — if the organisation's VMware footprint is reducing (migrating to Nutanix or Azure VMware Solution), the PLA commitment that includes a VMware revenue floor may lock in spend that the organisation's deployment model no longer requires. Conversely, for organisations with stable VMware deployments and growing mainframe workloads, a PLA structured around the combined spend can deliver genuine discount leverage on the CA component that individual CA negotiation cannot match.

The due diligence required before signing a PLA includes: a complete mapping of current and projected spend across all Broadcom product families; modelling of the PLA terms against individual product renewal pricing to identify the genuine net saving; review of PLA scope reduction provisions to ensure the organisation retains the ability to reduce VMware commitment as workloads evolve; and assessment of the annual escalator provisions across the combined PLA — a 6% annual escalator on a $10M combined PLA creates a $600,000 annual cost increase that must be evaluated against the discount achieved at signing. Our team supports PLA evaluation engagements for organisations with complex Broadcom footprints, providing the independent analysis that a Broadcom account team is structurally unable to deliver.

Mainframe Modernisation and Its Licensing Implications

For organisations pursuing mainframe modernisation programmes — whether migrating specific applications to distributed infrastructure, implementing API layers to reduce mainframe MIPS consumption, or evaluating full workload migration — the CA licensing implications of the modernisation roadmap must be understood before design decisions are made. Mainframe applications that generate significant MSU consumption when run natively may produce different capacity profiles when fronted by API layers or when specific processing steps are offloaded to distributed compute. Understanding the MSU impact of each architectural change before implementation allows the organisation to model the licensing cost reduction achievable through the modernisation programme, which in turn provides the financial business case that justifies the investment.

CA product dependencies also create modernisation constraints that procurement teams need to understand. Applications that rely on CA Endevor for source code management, CA Datacom for database operations, or CA IDMS for network database functions cannot simply be migrated without addressing these product dependencies — either by migrating to alternative tools (adding project complexity) or by maintaining CA licences for the residual mainframe functions that cannot be immediately migrated. The commercial dialogue with Broadcom during a modernisation programme should explicitly address the planned reduction in CA product footprint over the contract horizon, ensuring that the renewal agreement includes scope reduction rights tied to documented migration milestones rather than locking the organisation into capacity tiers that reflect a departing workload profile. For the complete playbook on managing CA mainframe licensing through a modernisation programme, the resources in our Broadcom Knowledge Hub provide the detailed framework.