CA. Mainframe contracts, modern auditors.

CA Technologies products — mainframe estate tools, AIOps, API Management, Endevor, Top Secret, and the legacy distributed agent portfolio — now sit inside Broadcom. CA audits are the highest-value and the slowest-moving of the Broadcom audit categories. We assess, defend, and negotiate the CA estate.

How CA licensing still works.

CA mainframe products are licensed by MIPS or MSU on the LPAR they run against, with sub-capacity rules under specific contract terms, and per-product mainframe ELA agreements that bundle dozens of tools into a single capacity number. Distributed CA products — including AIOps, Spectrum, eHealth, and the API Management portfolio — are licensed by user, by device, by transaction, or by node depending on the product line and the vintage of the entitlement.

Most CA customers have not re-papered their CA entitlement since the Broadcom acquisition. The contract on file is often a decade old, with sub-capacity rules that may or may not have been preserved through assignment.

What auditors look at for CA.

For mainframe CA, the audit pulls SMF records, IPL history, LPAR configuration, and the product activation records that show which CA tools were used during the audit window. For distributed CA, the audit pulls the product console exports, the agent deployment list, and the configuration database.

Mainframe CA disputes often centre on whether sub-capacity rules apply to a given LPAR, and whether peak MSU should be measured by rolling 4-hour average or by raw peak. Distributed CA disputes centre on installed-but-unused agents and on the metric definition.

Three CA audit traps.

Sub-capacity not preserved through assignment

Sub-capacity entitlement in the original CA contract may not have carried through the Broadcom assignment cleanly. Auditors may attempt to revert to full LPAR capacity if the documentation chain is incomplete.

Bundled tools used without active entitlement

Mainframe ELAs bundle dozens of products. After a renewal or partial termination, tools that were once in the bundle but are no longer active may continue to be invoked by automation. Audit treats this as full-product usage.

Distributed agent sprawl

CA distributed agents installed across server estates years ago are often still present on hosts long since repurposed. The audit reconstruction counts them as active deployments unless the customer can prove removal.

Defences we use in CA engagements.

CA audits are document-heavy. The defences below have all been used to reduce a real claim.

Mainframe sub-capacity preservation under assignment

Rolling 4-hour average versus raw peak MSU methodology

LPAR sysplex aggregation and isolation

Disaster recovery and standby LPAR exemption

Top Secret, ACF2, RACF inter-operability and entitlement

Endevor and software change management scope

Mainframe ELA bundle re-allocation

Mainframe versus distributed product boundary

AIOps DX OI metric reconciliation

Spectrum and eHealth deployed-agent versus monitored-device counts

API Management gateway throughput tier challenges

PPM and Clarity user definition disputes

Service Virtualization environment treatment

Test, development, and DR carve-out claims

Affiliate, subsidiary, and divested-entity scope

True-up window and notice-period challenges

Where CA savings tend to land

In documented CA mainframe engagements the largest single reduction usually comes from re-establishing sub-capacity entitlement through the assignment chain. The second largest comes from re-allocating bundled-ELA capacity to the products the customer is actually using and away from those they have not run for years. For distributed CA, the largest single reduction usually comes from removing decommissioned-host agent counts from the audit reconstruction.

CA licensing questions.

Did our sub-capacity rights carry through the Broadcom acquisition?

Sub-capacity rights flow from the original CA contract and its amendments. The Broadcom assignment in principle preserves them, but the documentation chain is the test. We frequently re-establish sub-capacity rights that the auditor initially refused to honour.

How is mainframe peak measured?

It depends on the contract. Some contracts use the rolling 4-hour average (R4HA), others use raw peak MSU. The choice materially changes the claim. The methodology used by the auditor must match what the contract actually says.

Are CA distributed and CA mainframe audited together?

Often yes, under a single audit clause. Buyers can sometimes scope the two apart at the protective-response stage, particularly when the contractual basis differs. Narrowing scope is a high-value early defence.

Can we drop CA products at renewal?

Yes, with notice and with a clean inventory of which tools are no longer needed. Dropped tools must be removed from the environment cleanly to avoid post-renewal audit exposure on the dropped products.

How is AIOps DX licensed?

DX OI is licensed by Monitored Element. The definition of a Monitored Element is technical and contract-specific. Audits frequently apply a broader definition than the contract entitles.

CA. Mainframe contracts, modern auditors.

How CA licensing still works.

What auditors look at for CA.

Three CA audit traps.

Defences we use in CA engagements.

Where CA savings tend to land

CA licensing questions.

CA audit on the desk?
Don't reply alone.

CA. Mainframe contracts, modern auditors.

How CA licensing still works.

What auditors look at for CA.

Three CA audit traps.

Defences we use in CA engagements.

Where CA savings tend to land

CA licensing questions.

CA audit on the desk?Don't reply alone.

CA audit on the desk?
Don't reply alone.