How are BMC Control-M and Broadcom CA 7 licensed?

Both are workload automation schedulers whose mainframe footprint is licensed on capacity. Broadcom (CA) CA 7, now CA 7 Workload Automation, is a mainframe centric scheduler licensed on MSU or MIPS capacity of the LPARs it runs on, and it can sit under Broadcom Mainframe Consumption Licensing (MCL). BMC Control-M is a broader, cross platform orchestration product, and on z/OS its mainframe component is also priced on capacity, while its distributed and cloud reach is commonly measured by managed jobs or tasks. So on the mainframe the headline metric is similar, capacity, and the meaningful differences sit in scope, the consumption framework, and how each is bundled.

Is it worth switching between Control-M and CA 7 to save money?

A scheduler is one of the stickiest products on the mainframe, because the entire batch schedule, its dependencies, calendars, triggers, and the operations runbooks around it are built into the tool, so a migration is a major program rather than a swap. BMC actively pursues displacement of Broadcom schedulers and publicizes large numbers of completed CA to BMC migrations, which means a genuine Control-M proposal can be a credible alternative to discipline a CA 7 renewal, and the reverse holds where Control-M is incumbent. But the saving on the migration alone rarely justifies the operational risk; the alternative is usually most valuable as negotiation leverage on the incumbent.

What actually decides Control-M versus CA 7 cost?

Three things decide it more than feature differences. First, the licensed mainframe capacity, the MSU or MIPS of the LPARs the scheduler runs on, which is the primary lever on either side. Second, the scope and bundle: Control-M's distributed and cloud reach measured in managed jobs against CA 7's mainframe focus, and how each sits inside a wider BMC or Broadcom portfolio deal. Third, your incumbency and a credible alternative, since both vendors run active displacement campaigns. Feature parity for core mainframe scheduling is close enough that licensing, scope, and leverage drive the number, not function.

Control-M vs CA 7: Scheduling Licensing

Control-M vs CA 7: the licensing, not the feature sheet.

BMC Control-M and Broadcom (CA) CA 7 are both capable batch schedulers, and on the mainframe both are priced on capacity. Core scheduling parity is close. What actually moves the number is the consumption model, the scope and bundle each sits in, and the leverage your incumbency plus a credible alternative give you, since both vendors chase displacement of the other.

Keep your incumbent scheduler and use the other as leverage. A scheduler holds the entire batch schedule, its dependencies, calendars, and the operations runbooks around it, so a migration is a major program rather than a swap, and the saving on the move alone rarely clears the operational risk. The genuine value of the comparison is that BMC and Broadcom each run active displacement campaigns, with BMC publicizing large numbers of completed CA to BMC migrations, so a prepared proposal from the other side is a credible walk away that disciplines the incumbent's renewal. The prize is usually a better deal on what you already run.

Control-M vs CA 7, the licensing levers compared
Dimension	BMC Control-M	Broadcom (CA) CA 7
Vendor	BMC	Broadcom (CA)
Modern branding	Control-M, with BMC Helix Control-M as the SaaS line	CA 7 Workload Automation
Scope	Cross platform: mainframe, distributed, cloud orchestration	Mainframe centric batch scheduling
Mainframe metric	MSU or MIPS capacity of authorized LPARs	MSU or MIPS capacity of authorized LPARs
Distributed metric	Commonly managed jobs or tasks per day	Mainframe focused; less distributed footprint
Consumption option	BMC consumption oriented model	Broadcom Mainframe Consumption Licensing (MCL)
Displacement posture	Actively targets Broadcom scheduling estates	Defends installed base under Broadcom portfolio terms

Control-M vs CA 7, the licensing levers compared

Dimension

BMC Control-M

Broadcom (CA) CA 7

Vendor

BMC

Broadcom (CA)

Modern branding

Control-M, with BMC Helix Control-M as the SaaS line

CA 7 Workload Automation

Scope

Cross platform: mainframe, distributed, cloud orchestration

Mainframe centric batch scheduling

Mainframe metric

MSU or MIPS capacity of authorized LPARs

Distributed metric

Commonly managed jobs or tasks per day

Mainframe focused; less distributed footprint

Consumption option

BMC consumption oriented model

Broadcom Mainframe Consumption Licensing (MCL)

Displacement posture

Actively targets Broadcom scheduling estates

Defends installed base under Broadcom portfolio terms

For most estates this is a renewal decision, not a procurement one. Use it this way:

Stay with the incumbent and negotiate if

The scheduler holds your live batch schedule, dependencies, and runbooks, as it almost always does
A prepared proposal from the competing vendor gives you a credible walk away to discipline the renewal
Right sizing the licensed MSU and choosing the consumption model deliberately captures most of the available saving

Genuinely consider switching if

You are consolidating onto one orchestration platform across mainframe, distributed, and cloud, where Control-M's reach earns its place
The displacing vendor offers migration terms and tooling large enough to clear the real cutover cost and risk
Your incumbent relationship has structural problems a renewal cannot fix, such as repeated uplift pressure

Either way, the foundational lever is the same as for any capacity priced product: confine the scheduler to the LPARs that genuinely need it, right size the MSU, and decide between the standard entitlement and the consumption model on the arithmetic, not the sales pitch.

How are they licensed?Both on MSU or MIPS capacity on the mainframe. CA 7 can use Broadcom MCL; Control-M adds distributed and cloud reach often measured in managed jobs.

Is switching worth it?Rarely as a pure cost play, because a scheduler is deeply embedded. The alternative is most valuable as negotiation leverage, since both vendors pursue displacement.

What decides the cost?Licensed capacity, scope and bundle, and your incumbency plus a credible alternative. Core scheduling parity is close enough that licensing and leverage drive the number.

What is the first lever?Right size the licensed MSU to the LPARs that genuinely need scheduling, and choose between the standard entitlement and the consumption model on the arithmetic.

Close on features. The deal is won on leverage.

Explainers: contractual MSU vs consumed MSU and MSU explained. Sibling products: BMC Control-M for z/OS licensing and CA 7 Workload Automation licensing. Guide: Control-M renewal, capacity and job count levers. Hubs and commercial: the BMC buyer side guide, the Broadcom (CA) buyer side guide, Broadcom (CA) license negotiation, and BMC license negotiation.

Control-M vs CA 7: the licensing, not the feature sheet.

The verdict

Head to head

Who should pick which

Frequently asked

The competing proposal is leverage. We turn it into a better renewal.