How are BMC MainView and Broadcom SYSVIEW licensed?

Both are z/OS performance monitoring products licensed on capacity, using MSU, the IBM measure of processor capacity, so each entitlement is built on the MSU rating of the LPARs where the monitor is authorized to run. BMC MainView, now branded within the BMC AMI Ops family, can be taken under BMC zConsumption Licensing (zCL), a consumption based model with a year end true up. Broadcom (CA) SYSVIEW can be taken under Broadcom Mainframe Consumption Licensing (MCL), Broadcom's consumption model. So the headline metric is the same on both sides, MSU capacity, and the meaningful difference is which vendor's consumption framework and contract structure you are negotiating inside.

Is it worth switching between MainView and SYSVIEW to save money?

Rarely as a pure cost play, because both are deeply embedded monitors woven into operations runbooks, automation, and staff expertise, so a switch carries real migration cost, retraining, and operational risk that usually outweighs the licensing saving on its own. The more reliable value of the alternative is as negotiation leverage: a genuinely prepared evaluation of the competing product gives you a credible walk away that disciplines the incumbent's renewal, especially since BMC and Broadcom each actively pursue displacement of the other. The win is usually a better deal on the incumbent, not the disruption of a full migration.

What actually decides MainView versus SYSVIEW cost?

Three things decide it more than feature differences. First, the licensed capacity: both price on the MSU of the LPARs they monitor, so right sizing that footprint is the primary lever on either side. Second, the consumption model and contract structure: BMC zCL versus Broadcom MCL, plus how the monitor is bundled into a wider BMC or Broadcom portfolio deal, where the real negotiation happens. Third, your incumbency and the credible alternative: the leverage you hold by being able to move, or being newly courted by the other vendor. Feature parity between the two is close enough that licensing and leverage, not function, drive the number.

MainView vs SYSVIEW: Licensing Compared

MainView vs SYSVIEW: the licensing, not the feature sheet.

BMC MainView and Broadcom (CA) SYSVIEW are both capable z/OS performance monitors, and both are licensed on MSU capacity. Feature parity is close. What actually moves the number is the consumption model, BMC zCL against Broadcom MCL, the bundle each sits in, and the leverage your incumbency and a credible alternative give you.

Keep your incumbent monitor and use the other as leverage. Both MainView and SYSVIEW cover z/OS monitoring well enough that a switch is rarely justified by features or by licensing saving alone, because the migration cost, retraining, and operational risk are real. The genuine value of the comparison is that BMC and Broadcom each chase displacement of the other, so a credible, prepared evaluation of the competing product is a real walk away that disciplines the incumbent's renewal. The prize is usually a better deal on what you already run.

MainView vs SYSVIEW, the licensing levers compared
Dimension	BMC MainView	Broadcom (CA) SYSVIEW
Vendor	BMC	Broadcom (CA)
Modern branding	BMC AMI Ops family	SYSVIEW Performance Management
Scope	z/OS performance, automation, event correlation	z/OS, CICS, MQ, IMS, JES, USS real time monitoring
Licensing metric	MSU capacity of authorized LPARs	MSU capacity of authorized LPARs
Consumption option	BMC zConsumption Licensing (zCL)	Broadcom Mainframe Consumption Licensing (MCL)
Bundle context	Often inside a wider BMC AMI portfolio deal	Often inside a Broadcom portfolio or MCL agreement
Displacement posture	Actively targets Broadcom monitoring estates	Actively targets BMC monitoring estates

MainView vs SYSVIEW, the licensing levers compared

Dimension

BMC MainView

Broadcom (CA) SYSVIEW

Vendor

BMC

Broadcom (CA)

Modern branding

BMC AMI Ops family

SYSVIEW Performance Management

Scope

z/OS performance, automation, event correlation

z/OS, CICS, MQ, IMS, JES, USS real time monitoring

Licensing metric

MSU capacity of authorized LPARs

Consumption option

BMC zConsumption Licensing (zCL)

Broadcom Mainframe Consumption Licensing (MCL)

Bundle context

Often inside a wider BMC AMI portfolio deal

Often inside a Broadcom portfolio or MCL agreement

Displacement posture

Actively targets Broadcom monitoring estates

Actively targets BMC monitoring estates

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

Stay with the incumbent and negotiate if

The monitor is embedded in your runbooks, automation, and staff expertise, as it usually is
A prepared evaluation of the competing product gives you a credible walk away to discipline the renewal
Right sizing the licensed MSU and choosing the consumption model deliberately gets you most of the available saving

Genuinely consider switching if

You are already mid transformation and the migration cost can ride on a program that is happening anyway
The other vendor offers displacement terms large enough to clear the real migration and retraining cost
Your incumbent relationship has structural problems that a renewal cannot fix

Either way, the foundational lever is the same as for any capacity priced product: confine the monitor 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 capacity of the authorized LPARs. MainView can use BMC zCL; SYSVIEW can use Broadcom MCL. The metric is the same; the consumption framework and bundle differ.

Is switching worth it?Rarely as a pure cost play, because both are deeply embedded. The alternative is most valuable as negotiation leverage, since each vendor actively pursues displacement of the other.

What decides the cost?Licensed capacity, the consumption model and bundle, and your incumbency plus a credible alternative. Feature 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 monitoring, and choose between the standard entitlement and the consumption model on the arithmetic.

Close on features. The deal is won on leverage.

Explainers: Broadcom Mainframe Consumption Licensing (MCL) explained and hardware model capacity ratings and software cost. Sibling product: BMC Control-M for z/OS licensing. Other comparison: Tailored Fit Pricing vs sub-capacity. Hubs and commercial: the BMC buyer side guide, the Broadcom (CA) buyer side guide, BMC cost optimization, and Broadcom (CA) license negotiation.

MainView vs SYSVIEW: the licensing, not the feature sheet.

The verdict

Head to head

Who should pick which

Frequently asked

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