① Publishers · Compuware (BMC)
Compuware sold the developer tooling that half the mainframe world still runs: Topaz, Xpediter, Abend-AID, File-AID, Strobe. BMC acquired the company in 2020 and folded the portfolio into BMC AMI DevX. Your contracts, and your renewal leverage, live in that transition.
If your developers debug, browse data, or chase abends on z/OS, you probably run Compuware.
The Compuware (BMC) estate is developer tooling: Topaz Workbench as the modern front end (now sold as BMC AMI DevX Workbench), Xpediter for interactive debugging (now BMC AMI DevX Code Debug), Abend-AID for fault analysis, File-AID for data management, Strobe for application performance measurement, ISPW for source and release management (now BMC AMI DevX Code Pipeline), plus Hiperstation for test automation and ThruPut Manager for batch optimization.
These products earned their installs over decades, which is exactly why they price the way they do at renewal: they are deeply embedded in developer workflow, the perceived switching cost is high, and the vendor knows it. Since the 2020 acquisition, BMC has maintained the products and invested in the DevX line, while progressively moving customers from legacy Compuware paper onto BMC contract vehicles.
That migration of paper is where buyers win or lose. Legacy Compuware agreements, BMC agreements, and the bridge between them rarely say the same thing about capacity, bundling, or termination.
Compuware products have historically been licensed against machine capacity, MIPS or MSU tiers, and that remains the dominant pattern under BMC. Capacity growth in the estate typically flows through to the software bill even when tool usage is flat, which is why hardware refresh planning and license planning have to happen together.
Under BMC, the tools are commonly positioned inside BMC AMI DevX bundles rather than as standalone line items. Bundles simplify procurement and obscure unit economics: a suite renewal can carry products nobody has launched in years, priced as if they were load bearing.
Estates typically hold a mix of legacy Compuware agreements and newer BMC vehicles. Terms differ on audit rights, capacity definitions, transferability, and termination. Which paper governs which entitlement is a question worth answering precisely, before the vendor answers it for you.
Post acquisition renewals tend to consolidate, co term, and climb.
The patterns we commonly observe after a publisher acquisition hold here: renewals arrive with proposals to consolidate legacy Compuware paper into broader BMC agreements, co terming the developer tooling with the rest of the BMC estate. That can be genuinely efficient, and it can also dissolve favorable legacy terms and convert a focused renewal into an all or nothing portfolio negotiation.
Uplift pressure typically concentrates on estates that have grown capacity since signature, and on standalone Compuware contracts the vendor would prefer to retire. On the audit side, capacity based metrics make machine growth the most common compliance theme: a processor upgrade can create exposure without a single new user. Audit activity is, in our experience, less frequent than with some other publishers but follows the same economics: findings appear where the contract metric and the deployed estate have quietly diverged.
If a Compuware audit or compliance review is on your desk, start with Compuware (BMC) audit defense.
Measure actual developer usage per product before the renewal cycle starts. Suites priced on full deployment rarely survive contact with usage data showing which tools carry the workflow and which are shelfware.
Where the estate runs both BMC and Compuware tooling, overlap is common: monitoring, data management, and DevOps functions can be double covered. Documented overlap is direct savings or direct leverage, whichever the negotiation needs.
IBM's ADFz family (Debug Tool, Fault Analyzer, File Manager, Application Performance Analyzer) and open tooling cover much of the same ground. A modeled transition, even one you never execute, changes the renewal conversation; see using competitive alternatives as leverage.
Consolidation into BMC paper is a concession to be priced, not a default to be accepted. If co terming happens, it should buy caps, consumption protections, and exit rights in return.