① Journal · Broadcom (CA) · CA Gen · Renewal
CA Gen carries two costs: the mainframe runtime priced on MSU and the development toolset entitled separately. Lock-in is real, but the runtime baseline and the seat footprint are fully in play. The number moves when you reset both to what you actually run. Five levers move it.
CA Gen is runtime capacity plus development seats. Reset both and you move the price.
CA Gen, the Broadcom (CA) model driven application development toolset, has two licensing dimensions that a renewal has to address separately. The mainframe runtime, which executes the generated COBOL, C, and Assembler in CICS, IMS, batch, or TSO, is licensed on mainframe capacity measured in MSU (Million Service Units) or the older MIPS, validated by the License Management Program (LMP) and commonly placed under Broadcom Mainframe Consumption Licensing (MCL). The development side, the workstation toolset and the host encyclopedia, is entitled separately on seats and components. So a CA Gen renewal is two negotiations: the runtime capacity baseline and the development footprint you keep. The buyers who move the number reset both to what they actually run rather than carrying entitlement accumulated across years of projects.
The complication unique to CA Gen is lock-in. Because applications are generated from models and regenerating them requires the toolset, the switching cost is real and a credible alternative is a longer horizon lever than it is for a commodity product. That does not remove leverage, it changes which levers are immediate. The runtime baseline, the seat count, and the ISV SCRT validation are fully in play now; a modernization path is a strategic lever that works over time. Around them sit True Forward scrutiny and the modernization signal itself. Read this with our guide on preparing for a Broadcom CA renewal and the Broadcom (CA) publisher hub.
What moves the number on a Broadcom (CA) CA Gen renewal · the lever and its effect
| Lever | How it works | Effect on the number |
|---|---|---|
| Runtime MSU baseline | Reset the committed runtime MSU baseline to genuine steady state consumption | Lowers the level the runtime is priced against, the largest lever |
| ISV SCRT validation | Validate the peak MSU in the ISV SCRT report independently before accepting it | Keeps the runtime consumption figure honest |
| Encyclopedia and seats | Right-size the host encyclopedia and development seats to active developers | Removes inactive development entitlement from the renewal |
| True Forward scrutiny | Challenge growth billed forward that no longer reflects the workload | Prevents paying forward for capacity you do not keep |
| Modernization path | A documented modernization plan reframes the estate over a longer horizon | Signals the estate is not a captive annuity |
These are levers and patterns we commonly observe on Broadcom (CA) CA Gen renewals, not guaranteed outcomes. The effect of each depends on your contract, baseline, seat count, and modernization stance; validate your own SCRT data before relying on any figure.
The generated applications run on the mainframe, and the runtime is priced on MSU under MCL, so the runtime baseline is the recurring cost. Pull twelve months of runtime consumption, separate steady state from one time spikes, and propose a baseline trued back to the real workload rather than the historical level the vendor anchored on. This lever is immediate and fully in play regardless of lock-in. See our explainer on the MSU baseline and how to reset it.
The runtime baseline is the recurring number.
The toolset and host encyclopedia are entitled on seats and components, and development teams shrink over a product's life while the entitlement rarely follows. Count active developers, map the encyclopedia and workstation entitlement against them, and drop the seats and components no longer used. This is line item removal the vendor cannot dispute when the usage data is yours. See our explainer on contractual vs consumed entitlement.
License the developers you have, not the team you had.
Lock-in makes a near term switch unrealistic, but it does not make the estate a captive annuity. A documented modernization path, even an early stage one that exploits the COBOL the toolset already generates, signals that the relationship has a horizon and reframes a renewal the vendor would otherwise price as permanent. Treat it as a strategic lever that works over time, not a bluff. See our piece on third party mainframe support.
A horizon changes how a renewal is priced.
④ Where the CA Gen renewal is won
A CA Gen renewal is runtime capacity and development seats. Lock-in shapes it but does not remove leverage. Reset the runtime, right-size the seats, signal the horizon.
Typical renewal reduction
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
CA Gen has two dimensions. The mainframe runtime, which executes the generated COBOL, C, and Assembler in CICS, IMS, batch, or TSO, is licensed on capacity measured in MSU or MIPS, validated by LMP and commonly placed under Broadcom Mainframe Consumption Licensing. The development side, the workstation toolset and host encyclopedia, is entitled separately. A renewal turns on the runtime capacity baseline plus the development footprint you keep entitled.
The runtime capacity baseline, because the generated applications run on the mainframe and the runtime is priced on MSU under MCL. Resetting that committed baseline to genuine steady state is the largest lever, and validating the ISV SCRT peak independently keeps it honest. Beyond that, right sizing the encyclopedia and seats removes line items, scrutinizing True Forward prevents paying forward for growth you do not keep, and a documented modernization path reframes the renewal.
It shapes it rather than removing leverage. Because applications are generated from models and regenerating requires the toolset, switching is a longer horizon lever. But the runtime baseline, the seat count, and the ISV SCRT validation are immediate and fully in play regardless of lock-in. A modernization path works over a longer timeline, and even an early stage plan signals the estate is not a captive annuity. See CA 1 Tape Management renewal negotiation.
We validate the runtime ISV SCRT data independently, reset the committed MCL baseline to genuine steady state, right size the encyclopedia and development seats to active developers, and frame a modernization horizon before the vendor controls the clock. Our Broadcom (CA) hub maps the levers and our license negotiation service runs the renewal from the buyer side.
Related: Broadcom (CA) publisher hub · CA 1 Tape Management renewal · Datacom renewal negotiation · preparing for a Broadcom CA renewal · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →