How do BMC and Broadcom mainframe portfolios compare on licensing?

Both are broad mainframe software portfolios priced largely on MSU capacity, and both offer a consumption model: BMC zConsumption Licensing (zCL) and Broadcom Mainframe Consumption Licensing (MCL), each with a year end true up. BMC's strength sits in operations and automation with the AMI family, MainView monitoring, Control-M scheduling, and the Compuware DevX tooling. Broadcom (CA) holds a deep portfolio across scheduling such as CA 7, databases such as Datacom and IDMS, security, and development tools such as Endevor. The licensing mechanics are similar; the real difference is which portfolio your estate is built on and which vendor's bundle you are negotiating inside.

Should I consolidate to one of them?

Consolidation can earn a bundle discount and simplify the relationship, but it also concentrates leverage in one vendor's hands, which is exactly what the vendor wants. The opposite, keeping both, preserves a credible switch threat in every category where the two compete, because BMC and Broadcom each actively pursue displacement of the other. The right answer depends on your estate: where one vendor already dominates your stack, a disciplined consolidation with hard caps can pay; where the split is even, retaining both as mutual leverage usually protects you better. Decide on the math and the leverage, not the consolidation pitch.

Do BMC and Broadcom compete directly?

In several categories, yes, and aggressively. Monitoring is the clearest example, BMC MainView against Broadcom SYSVIEW, and both vendors run displacement programs to take estate from the other. Scheduling, automation, and parts of the data and DevOps tooling also overlap. That direct competition is the buyer's main asset: a genuinely prepared evaluation of the rival product is a credible walk away that disciplines the incumbent's renewal, and the displacement terms each vendor will offer to win share can be substantial when the other is a real threat.

What actually decides BMC versus Broadcom cost?

Three things. First, where your estate is already invested, since switching embedded tools carries migration cost that usually outweighs licensing savings alone. Second, the consumption model and bundle structure, zCL versus MCL and how products are grouped into a portfolio deal, where the real negotiation happens. Third, your leverage: the credible alternative each vendor represents to the other, and your ability to right size the licensed MSU on either side. Feature parity in the overlapping categories is close enough that licensing structure and leverage, not function, drive the number.

BMC vs Broadcom: Mainframe Tools Compared

BMC vs Broadcom: the portfolio decision, not the feature sheet.

BMC and Broadcom (CA) both run broad mainframe software portfolios priced largely on MSU, each with a consumption model: BMC zCL and Broadcom MCL. BMC leans to operations and automation, Broadcom to a deep estate of scheduling, databases, and development tools. They compete directly in several categories and chase displacement of each other. That rivalry is your main asset, because a credible alternative on either side disciplines the incumbent renewal.

Pick the portfolio your estate is already built on, and use the other as standing leverage. Neither BMC nor Broadcom wins on features across the board; each is strong where your stack happens to be invested, and switching embedded tools rarely pays on licensing savings alone. The real prize is the rivalry: because the two actively displace each other, a prepared evaluation of the competing product is a credible walk away on every overlapping category. The disciplined move is to consolidate only where the math and hard caps justify it, and otherwise keep both vendors honest against each other.

BMC vs Broadcom, the licensing levers compared
Dimension	BMC	Broadcom (CA)
Portfolio strength	Operations, automation, monitoring, DevX	Scheduling, databases, security, development
Flagship tools	AMI Ops, MainView, Control-M, Compuware DevX	CA 7, Datacom, IDMS, Endevor, SYSVIEW
Primary metric	MSU capacity	MSU capacity
Consumption model	BMC zConsumption Licensing (zCL)	Broadcom Mainframe Consumption Licensing (MCL)
Bundle context	Wide AMI portfolio deals	Broadcom portfolio or MCL agreements
Displacement posture	Targets Broadcom monitoring and scheduling estates	Targets BMC monitoring and scheduling estates

BMC vs Broadcom, the licensing levers compared

Dimension

BMC

Broadcom (CA)

Portfolio strength

Operations, automation, monitoring, DevX

Scheduling, databases, security, development

Flagship tools

AMI Ops, MainView, Control-M, Compuware DevX

CA 7, Datacom, IDMS, Endevor, SYSVIEW

Primary metric

MSU capacity

Consumption model

BMC zConsumption Licensing (zCL)

Broadcom Mainframe Consumption Licensing (MCL)

Bundle context

Wide AMI portfolio deals

Broadcom portfolio or MCL agreements

Displacement posture

Targets Broadcom monitoring and scheduling estates

Targets BMC monitoring and scheduling estates

For most estates this is a renewal and consolidation decision, not a clean sheet procurement. Use it this way:

Lean BMC, or consolidate toward it, if

Your operations and automation stack already runs on AMI, MainView, or Control-M
You value a single operations and DevOps tooling relationship and can secure hard caps for it
Broadcom is a credible displacement threat you can use to price the BMC bundle

Lean Broadcom, or consolidate toward it, if

Your estate is built on CA scheduling, Datacom or IDMS, Endevor, or CA security
The breadth of the CA portfolio lets you negotiate one MCL agreement with real volume
BMC is a credible displacement threat you can use to price the Broadcom deal

Either way, the foundational lever is the same for any capacity priced portfolio: right size the licensed MSU, choose the consumption model on the arithmetic, and never let a consolidation remove your credible alternative without a cap that pays for the lost leverage.

How do they compare on licensing?Both price largely on MSU with a consumption model, zCL for BMC and MCL for Broadcom. The difference is portfolio depth and which bundle you negotiate inside.

Should I consolidate?Only where one vendor dominates your stack and you can secure hard caps. An even split is usually better kept as mutual leverage.

Do they compete directly?Yes, in monitoring, scheduling, and automation, with active displacement programs. That rivalry is your main negotiating asset.

What decides the cost?Estate investment, the consumption model and bundle, and your leverage. Feature parity is close enough that licensing and leverage drive the number.

Close on features. The deal is won on portfolio fit and leverage.

Explainers: Broadcom Mainframe Consumption Licensing (MCL) explained and what audit clauses allow. Related comparisons: MainView vs SYSVIEW and single vendor vs best of breed. Hubs and commercial: the BMC buyer side guide, the Broadcom (CA) buyer side guide, and Broadcom (CA) contract review.

BMC vs Broadcom: the portfolio decision, not the feature sheet.

The verdict

Head to head

Who should pick which

Frequently asked

Two portfolios, one credible threat each. We turn the rivalry into your discount.