How are CA Endevor and Compuware ISPW licensed?

Both are mainframe source code management systems whose entitlement is built on capacity. Broadcom (CA) Endevor SCM is licensed on MSU or MIPS capacity of the LPARs it runs on and can sit under Broadcom Mainframe Consumption Licensing (MCL). Compuware (BMC) ISPW, now carried within the BMC AMI DevX family, is also priced on mainframe capacity, with a smaller, more modern footprint than the long established Endevor codebase. So the headline metric is similar, capacity, and the meaningful differences sit in the consumption framework, the bundle each sits in, and the migration economics the challenger offers.

Is switching from Endevor to ISPW worth it?

This is one of the more genuinely contestable switches on the mainframe, because Compuware and now BMC have positioned ISPW explicitly as an Endevor replacement, built a migration practice and methodology to move customers off Endevor, Panvalet, Librarian, and ChangeMan, and publicized typical timelines and savings for the move. That makes a switch a real option rather than a bluff. But SCM still sits at the center of the development lifecycle, so a migration carries conversion of source and history, rebuilding of promotion and approval flows, retraining of developers, and revalidation that builds and deployments behave identically. The decision turns on whether the modernization value plus the saving clears that program cost, or whether the credible threat is better used to discipline an Endevor renewal.

What decides Endevor versus ISPW cost?

Three things. First, the licensed mainframe capacity, the MSU or MIPS of the LPARs the SCM runs on, the primary lever on either side. Second, the consumption model and bundle: Broadcom MCL and the wider Broadcom portfolio against the BMC AMI DevX family ISPW now belongs to. Third, the switching economics, since ISPW is sold partly on migration savings and resource reduction, which gives a buyer a concrete alternative to price against the Endevor renewal. Feature differences exist, particularly around agile and parallel development, but licensing, the bundle, and the migration math drive the number.

Endevor vs ISPW: SCM Licensing

Endevor vs ISPW: the licensing and the switching math.

Broadcom (CA) Endevor and Compuware (BMC) ISPW both manage mainframe source code, and both are priced on capacity. Unlike most mainframe head to heads, this one is a genuine switching question: ISPW is positioned explicitly to replace Endevor, with a migration practice behind it. The decision turns on whether the modernization value and the saving clear the program cost, or whether the threat is better used as leverage.

Treat this as a real decision, not a bluff, then make it on the numbers. ISPW is positioned squarely as an Endevor replacement, with a migration practice and published timelines and savings, so unlike most mainframe head to heads the alternative is genuinely actionable. But source code management sits at the center of the development lifecycle, and a migration means converting source and history, rebuilding promotion and approval flows, retraining developers, and revalidating every build and deployment. The right move is to price that program honestly against the modernization value and the saving. Where the math clears, switch. Where it does not, the credible, costed threat still disciplines the Endevor renewal.

Endevor vs ISPW, the licensing levers compared
Dimension	Broadcom (CA) Endevor	Compuware (BMC) ISPW
Vendor	Broadcom (CA)	Compuware, now BMC
Modern branding	CA Endevor Software Change Manager	ISPW, within the BMC AMI DevX family
Heritage	Long established, large installed base	Newer, positioned as the agile replacement
Licensing metric	MSU or MIPS capacity of authorized LPARs	MSU or MIPS capacity of authorized LPARs
Consumption option	Broadcom Mainframe Consumption Licensing (MCL)	BMC consumption oriented model
Migration posture	Defends installed base under Broadcom terms	Active migration practice off Endevor and peers
Bundle context	Often inside a wider Broadcom portfolio deal	Often inside a BMC AMI DevX portfolio deal

Endevor vs ISPW, the licensing levers compared

Dimension

Broadcom (CA) Endevor

Compuware (BMC) ISPW

Vendor

Broadcom (CA)

Compuware, now BMC

Modern branding

CA Endevor Software Change Manager

ISPW, within the BMC AMI DevX family

Heritage

Long established, large installed base

Newer, positioned as the agile replacement

Licensing metric

MSU or MIPS capacity of authorized LPARs

Consumption option

Broadcom Mainframe Consumption Licensing (MCL)

BMC consumption oriented model

Migration posture

Defends installed base under Broadcom terms

Active migration practice off Endevor and peers

Bundle context

Often inside a wider Broadcom portfolio deal

Often inside a BMC AMI DevX portfolio deal

This one splits more cleanly than most, because the challenger has built a path to switch. Use it this way:

Stay with Endevor and negotiate if

Endevor is deeply woven into your promotion model, approvals, and a large body of source history
A prepared, costed ISPW migration gives you a credible walk away to discipline the Endevor renewal
Right sizing the licensed MSU and choosing the consumption model captures most of the available saving without the program risk

Genuinely consider ISPW if

You are modernizing the development lifecycle and want agile and parallel development the older SCM struggles with
The migration offer, tooling, and projected savings clear the conversion, retraining, and revalidation cost
Your Endevor relationship faces repeated uplift pressure that a renewal alone will not fix

Either way, the foundational lever is the same as for any capacity priced product: confine the SCM 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. Endevor can use Broadcom MCL; ISPW sits in the BMC AMI DevX family under a BMC consumption oriented model.

Is switching worth it?More so than most mainframe switches, because ISPW has a migration practice off Endevor. Price the conversion, retraining, and revalidation against the saving.

What decides the cost?Licensed capacity, the consumption model and bundle, and the migration economics the challenger offers as a concrete alternative.

What is the first lever?Right size the licensed MSU to the LPARs that genuinely need the SCM, and build a costed migration so the threat, or the switch, is real.

A switch you can actually price. So price it, then decide.

Explainers: contractual MSU vs consumed MSU and MSU explained. Sibling products: CA Endevor licensing and Compuware ISPW licensing. Guides: estimating switching costs before you threaten to switch and running an RFP for mainframe tooling replacements. Hubs and commercial: the Broadcom (CA) buyer side guide, the Compuware buyer side guide, Broadcom (CA) license negotiation, and BMC license negotiation.

Endevor vs ISPW: the licensing and the switching math.

The verdict

Head to head

Who should pick which

Frequently asked

A switch with real numbers. We run them both ways.