Guide · Compuware (BMC) audit defense

BMC now audits the tools Compuware sold you.

Xpediter, Abend-AID, File-AID, and Strobe came under BMC with the 2020 acquisition, and so did their audits. The first question in any Compuware tool audit is which paper governs it. Here is how the defense runs, and where buyers protect the most money.

№ 01

What changed under BMC

DevXLegacy paper

BMC acquired Compuware (BMC) in 2020. The developer and fault diagnosis tools your teams rely on, Topaz Workbench, Xpediter, Abend-AID, File-AID, and Strobe, now sit in the BMC AMI DevX line and under BMC's commercial and compliance practices. The software did not change. The owner, the contract motion, and the audit posture did.

The pattern we commonly observe: an audit of the former Compuware tools that proceeds as if current BMC paper governs, when in fact a meaningful part of the estate still runs under pre acquisition Compuware agreements with different audit rights, capacity definitions, and metrics. Letting the auditor pick which terms apply is the first and most expensive mistake.

№ 02

Six defenses

In order

Where the defense is won

  • Establish which paper governs each product: legacy Compuware terms or current BMC terms, because audit rights and capacity definitions differ between them
  • Hold the audit clause: confirm what BMC may verify, with what notice, over which products, and refuse scope beyond it
  • Validate capacity by LPAR: confirm which LPARs and environments actually run each tool, and that the measured MSUs match what the contract licenses
  • Check the non production treatment: ensure development, test, and disaster recovery capacity is counted as the contract requires, not swept in as production
  • Reconcile hardware refresh history: capacity that grew through a box upgrade without revisiting entitlement is a common, and challengeable, source of findings
  • Assemble full entitlement: surface every license, migration, and prior Compuware purchase before accepting any shortfall
№ 03

Where the money hides

Capacity countsScope

These tools are typically licensed by mainframe capacity for the environments where they run, so the audit turns on how capacity is counted. The recurring exposures are capacity that grew through a hardware refresh or an LPAR reconfiguration without the entitlement being revisited, tools that spread to more environments than were licensed, and scope that quietly expands to include development, test, or disaster recovery that the agreement treats differently. Each is a place where the vendor's count and the contract's terms diverge, and each is challengeable with validated deployment data mapped against entitlement, product by product and LPAR by LPAR.

№ 04

What changes with us on your side

Which paper governs48 hour mobilization

We start where the vendor would rather not: establishing which contract governs each product, then holding the audit to that clause. We validate capacity by LPAR, correct the non production treatment, reconcile the refresh history, and rebuild entitlement in full before any shortfall is accepted. Directionally, across 500+ engagements and $180M+ in negotiated mainframe spend, audit defenses of this kind typically bring findings and the settlements that follow 20 to 35 percent below the opening claim. On an active audit notice, we mobilize within 48 hours.

№ 05

Frequently asked

FAQ
Q1
Does BMC audit the former Compuware products?Yes. Since the 2020 acquisition the former Topaz, Xpediter, Abend-AID, File-AID, and Strobe products sit under BMC and its audit practices. Which contract governs is the first thing to establish.
Q2
Which contract governs a Compuware tool audit now?It depends on your estate. Many buyers still run partly on pre acquisition Compuware paper, with audit rights and metrics that differ from current BMC terms. Confirm which applies to which products first.
Q3
How are the tools licensed and measured?Typically by mainframe capacity in MSUs for the LPARs where they run. The exposure is in how that capacity is counted, which LPARs are in scope, and whether non production is treated correctly.
Q4
What is the most common exposure?Capacity that grew through hardware refresh without revisiting entitlement, tools deployed more widely than licensed, and scope expanding to excluded environments. Validating deployment against entitlement is where the defense is won.

Settle which paper governs first.

Audit notice or renewal under 18 months out? We mobilize within 48 hours.

Same tools. New owner. Read the paper.

Get expert help