① Journal · Contract traps
Since Broadcom (CA) folded the former CA Technologies portfolio into its enterprise model, the renewal math changed before most buyers noticed. The recurring patterns below cost money at renewal and audit, and every one of them is more negotiable before signing than after.
The expensive clauses in a Broadcom CA agreement are rarely hidden. They sit in the portfolio structure, the capacity terms, and the renewal mechanics that nobody negotiates, which is the same thing as agreeing to them.
Broadcom (CA) sells the former CA Technologies mainframe estate as a portfolio: systems management, security (CA ACF2, CA Top Secret), automation, database utilities, and DevOps tooling (CA Endevor, CA InterTest), commonly licensed under a consumption oriented model branded Mainframe Consumption Licensing (MCL). Large enterprises typically run dozens of distinct CA products, and the renewal is priced on the whole set rather than the handful that carry real use. The traps below share a single trait: the cost lands at a renewal or an audit, years after signing, when the leverage to fix them has passed to the vendor. Read them as patterns commonly observed, not as claims about any single agreement, which always governs its own terms. For the consumption mechanics behind several of these, see Broadcom Mainframe Consumption Licensing explained.
| Trap | What it costs you | Neutralize it by |
|---|---|---|
| Portfolio bundle pricing | You pay across a bundle when one or two families carry the real use | Itemize per product use and keep a documented drop right |
| Capacity growth uplift | Renewal repriced on grown MIPS or MSU with no negotiated cap | Cap the capacity escalator and fix the rate for the term |
| MCL consumption baseline | A consumption commitment set on a peak period, paid all term | Scrub the baseline window before agreeing the floor |
| Co-term consolidation | Agreements pulled to one date to maximize the vendor's leverage | Stagger or co-term on your terms, not at the vendor's clock |
| Sub-capacity reporting gaps | A reporting lapse can default billing toward full capacity | Confirm the reporting obligation and a cure path in writing |
| Bundled entitlement creep | Products added in that you neither use nor can later remove | Pin entitlements to actual use and keep removal rights |
| Audit and true up terms | Findings priced at list with no dispute window or cure period | Pre agree rates, a cure period, and a good faith dispute window |
Broadcom CA portfolio structure, MCL mechanics, and the capacity and audit patterns described reflect practices commonly observed across CA mainframe renewals as of 2026. This is not legal advice; your specific agreement, consumption data, and counsel govern.
Two of these deserve the most attention. The portfolio bundle is where most overspend hides: the renewal is quoted on the full product set, while a large share of the bundle commonly sits idle. Rationalize the estate before the vendor quotes, so you negotiate from a true picture of use rather than the inherited list. The second is the capacity uplift, where renewal cost is decided by a single number, your grown MIPS or MSU, applied without a cap. Build the cap and the rate lock before capacity is the vendor's to price. For the full rationalization method see Broadcom CA portfolio rationalization before renewal, and for the negotiation itself, Broadcom CA license negotiation.
Broadcom CA renewal or audit notice under 18 months out? We mobilize within 48 hours to read the agreement before you sign or pay. Start with Broadcom CA license negotiation.
Every issue of the journal, plus renewal benchmarks we do not publish on the site. No vendor sharing, ever.
More from the journal: IBM contract traps to avoid, when a 60 percent uplift lands, and why renewal preparation starts at 18 months. Guides: negotiating Broadcom portfolio license agreements. Explainer: Broadcom Mainframe Consumption Licensing. Hub: Broadcom (CA) mainframe licensing.