① Product · Compuware (BMC)
Abend-AID is the fault diagnosis tool developers reach for first, now sold as BMC AMI DevX Abend-AID. The diagnostics did not change with the acquisition. The commercial model did, and that is where the renewal is won.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →Abend-AID is a mainframe application failure resolution tool. It intercepts abends and program failures and produces a diagnosis tuned to the language and data in play, capturing source, working storage, and file, IMS, Db2, and MQ context so a developer reaches the cause fast rather than reading a raw dump. It covers COBOL, PL/I, Assembler, C, and supports Db2, IMS, and IDMS. Abend-AID came to BMC through the Compuware acquisition and now sits in the BMC AMI DevX family as BMC AMI DevX Abend-AID. The function is the same one teams have relied on for decades. What a buyer needs to track is that the product now prices on BMC's terms.
As a BMC mainframe product, Abend-AID is licensed on MSU based capacity, the metric BMC applies across its z/OS portfolio. Many estates contract under BMC's zConsumption Licensing, paying on the prior year's actual consumption with an annual true up on overage, while older Compuware agreements may remain on fixed MSU capacity. The charge follows machine capacity, not the number of developers or the number of abends diagnosed. Where Compuware tools were converted onto the consumption model, the move commonly rested on a stated MIPS to MSU ratio tied to the machine models in place at the time.
| Element | How Abend-AID is treated |
|---|---|
| Metric | MSU based capacity |
| Model | zConsumption Licensing (zCL) or fixed MSU |
| Reconciliation | Annual true up on consumption overage |
| Conversion basis | Stated MIPS to MSU ratio, e.g. 8.2 to 1 |
| Cost driver | Licensed or consumed MSU |
Directional summary. Confirm the exact product entitlement and terms on your own BMC order.
Three drivers set the Abend-AID number. Consumed or licensed MSU, because the metric follows capacity, so estate growth lifts the charge regardless of how heavily the tool is actually used. The MIPS to MSU conversion ratio, because a ratio fixed to older machines can drift and inflate the consumption baseline as hardware changes. And bundling, because Abend-AID is frequently sold inside a larger BMC AMI DevX agreement where the individual line cannot be benchmarked. There is a particular tension here worth naming: Abend-AID is a developer diagnostic, used in bursts when something breaks, yet a capacity metric bills it against the whole machine. That mismatch is exactly where the gap between licensed and needed capacity opens up.
The traps live in the consumption mechanics BMC applies across the estate. An uncapped annual true up turns one high consumption year into a higher recurring baseline. A MIPS to MSU ratio carried forward without review, the classic being a figure such as 8.2 to 1 tied to retired machines, can overstate consumption against current hardware, a risk that is sharper on a tool inherited through an acquisition where nobody re examined the conversion. And scope creep, where Abend-AID is enabled on LPARs the entitlement never covered, widens the basis quietly. Independent validation of the consumption report and the conversion ratio is the defense, the same discipline behind Compuware audit defense.
The consumption levers come first: a true up cap so a single peak year cannot become a permanent floor, and a renegotiated MIPS to MSU ratio in good faith as hardware changes. The contract levers are uplift caps and unbundling Abend-AID from the wider BMC AMI DevX agreement so it can be benchmarked on its own. The lever specific to this tool is the diagnostic usage reality check: because Abend-AID is a developer instrument rather than a runtime engine, modeling where it is genuinely needed often shows the licensed capacity exceeds the real footprint, which reframes the whole conversation. We confirm the entitlement, model the consumption baseline, and test the ratio before the renewal sets the next term, the core of our Compuware renewal work.
Abend-AID is a BMC product now, sold as BMC AMI DevX Abend-AID, and it follows BMC's MSU based capacity model. Many estates contract under BMC's zConsumption Licensing, paying on prior year actual z/OS consumption with an annual true up on overage, while older Compuware agreements may still sit on fixed capacity. The charge follows machine capacity, not a per developer or per abend count. Confirm the entitlement on your own order, since the product moved from Compuware to BMC and was rebranded under AMI DevX.
Abend-AID came to BMC through the Compuware acquisition and now sits in the BMC AMI DevX family. Buyers search both names, so the dual naming holds: Compuware (BMC) Abend-AID. The fault diagnosis function is unchanged, but the commercial model is now BMC's standard MSU approach, which is what determines the renewal number.
When Compuware tools were folded onto BMC's consumption model, the MIPS to MSU conversion was commonly set on a stated ratio, an example being 8.2 MIPS to 1 MSU, tied to the machine models in place at the time. A ratio carried forward without review can overstate consumption against current hardware. It is negotiable, and it is commonly left unexamined on tools inherited through an acquisition.
The levers are a true up cap, a renegotiated MIPS to MSU ratio as hardware changes, uplift caps, and unbundling the line from the wider BMC AMI agreement so it can be benchmarked. Because Abend-AID is a diagnostic developer tool rather than a runtime engine, a usage based reality check often shows the licensed capacity exceeds the real footprint. Modeling that gap before renewal is what moves the price.
Publisher hub: Compuware mainframe licensing. Related concept: The MIPS to MSU conversion question. Related concept: MSU explained. Put it to work: Compuware renewal advisory.