① Journal · Compuware (BMC) · Audit
Compuware (BMC) licenses its developer tools by capacity, measured through its own License Management System, and BMC has since renamed the suite as AMI DevX. From the buyer side the activity clusters on that capacity data and on entitlement across a suite whose product names have moved.
A Compuware audit reconciles the daily capacity check. Validate the LMS data first.
Compuware (BMC), now part of BMC and marketed as the AMI DevX line, licenses its mainframe developer tools mainly by capacity. The suite, Topaz, Xpediter, Abend-AID, File-AID, Strobe and Hiperstation among them, has commonly been governed through the Compuware License Management System (LMS), which initializes the entitlement and runs a daily check against the environment. That daily check is the data a Compuware audit reconciles against. The activity we observe clusters on the LMS capacity output, on entitlement across the developer tool suite, on the MSU or MIPS band the products are licensed to, and on the renaming that arrived with the BMC acquisition, which can break the link between the product you run and the agreement that covers it.
The pattern we commonly observe is a capacity and entitlement reconciliation that the buyer is well positioned to win if the inputs are validated first. The LMS daily check produces the numbers, and a buyer who has not validated that output is letting BMC read the capacity for them. The licensed band may have been set against capacity that has since grown or shrunk. The product names have moved under AMI DevX, so the invoice, the deployment, and the entitlement document can quietly fall out of alignment. The buyers who come through a Compuware audit cleanly are the ones who validated the LMS data, inventoried the DevX suite against entitlement, and reconciled the licensed band against current capacity before the notice arrived. Read this with ThruPut Manager licensing and the Compuware (BMC) publisher hub.
Where Compuware (BMC) audits cluster · what we commonly observe and the buyer defense
| Focus area | What Compuware checks | Buyer defense |
|---|---|---|
| LMS capacity data | The daily check from the License Management System | Validate LMS output independently against your deployment |
| DevX product entitlement | Topaz, Xpediter, Abend-AID, File-AID, Strobe against deployment | Inventory the suite, match each product to entitlement |
| MSU or MIPS band | The capacity band the products are licensed to | Reconcile the licensed band against current capacity |
| Post acquisition renaming | Products renamed into BMC AMI DevX since the acquisition | Map renamed products back to their original entitlement |
These are patterns we commonly observe across Compuware (BMC) audits, not statements of audit policy. Your specific entitlements, LMS terms, and capacity band govern; validate against your own LMS data and your contract before relying on any position.
The License Management System runs the daily check that a Compuware audit reconciles against, so the buyer who validates that output first controls the discussion. Pull the LMS data, reconcile it against your actual deployment and capacity, and resolve any discrepancy internally rather than discovering it in BMC's report. Capacity data you have checked is capacity data you can defend. See our explainer on MSU and capacity metrics.
Read the daily check before the auditor does.
The developer tool suite is broad, and the products are easy to deploy and hard to track once the names change. Inventory every DevX product actually in use, match each to a specific entitlement, and document anything decommissioned. The renaming under BMC AMI DevX is exactly where the thread between deployment and entitlement breaks, so a clean crosswalk is the defense. See Xpediter versus IBM Debug Tool.
Trace every tool to the agreement that covers it.
The products are licensed to a capacity band, and that band may have been set against a configuration that no longer matches your environment. Reconcile the licensed band against current capacity, identify whether you are over or under the band, and bring that reading to the table rather than accepting BMC's. A band reconciled to your real capacity is a defensible position and often a renewal lever. See our cost optimization service.
Match the band to the capacity you actually run.
④ Where the Compuware audit is won
A Compuware audit reconciles the daily capacity check. The defense is data you validated first. Validate the LMS, inventory the suite, reconcile the band.
Mobilization on an audit notice
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
Four areas: capacity data from the Compuware License Management System and its daily check, entitlement across the developer tool suite now consolidated into BMC AMI DevX, the MSU or MIPS band the products are licensed to, and the renaming that came with the BMC acquisition. The common thread is capacity and entitlement on a renamed suite.
Compuware products are commonly licensed by capacity through the License Management System, which initializes the entitlement and runs a daily check against the environment. That daily check is the data a Compuware audit reconciles against, so a buyer who has not validated the LMS output is letting the vendor read the capacity. Validating the LMS data against your own deployment is the starting point.
Treat it as a capacity and entitlement reconciliation across a renamed suite. Validate the LMS data before sharing anything, inventory every DevX product against entitlement, reconcile the licensed band against current capacity, map renamed products back to their original entitlement, and answer each request in writing scoped to the products in question. See what happens to pricing after a vendor is acquired.
We validate the LMS capacity data, inventory the DevX suite against entitlement, reconcile the licensed band, and manage the response from the buyer side so the reconciliation runs on your evidence. Our audit defense service mobilizes within 48 hours of a notice and our cost optimization service trims the profile the audit and the next renewal build on.
Related: Compuware (BMC) publisher hub · BMC audit activity · IBM audit activity · ThruPut Manager licensing · audit defense
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →