Comparison · fault diagnosis

Abend-AID vs IBM Fault Analyzer: the bundle decides, not the feature list.

Compuware (BMC) Abend-AID and IBM Fault Analyzer both diagnose mainframe abends, and both are licensed on capacity. Abend-AID rides in the BMC AMI DevX suite on MIPS or MSU; Fault Analyzer rides in the IBM Application Delivery Foundation family under IPLA. Feature parity is close, so the bundle each sits in and your incumbency decide the cost.

№ 01

The verdict

Bundle decidesLeverage on top

Follow the bundle, then use the other as leverage. Abend-AID and Fault Analyzer diagnose abends well enough that capability rarely settles it. What does settle it is which suite you already license: Fault Analyzer is the natural choice inside the IBM Application Delivery Foundation for z/OS tools, and Abend-AID is the natural choice inside the broader BMC AMI DevX suite. The switching cost is moderate, not extreme, since these tools sit beside operations rather than inside production data, so a move is feasible where the bundle economics justify it. And because IBM and BMC each chase displacement of the other, a prepared evaluation of the alternative is genuine leverage at renewal either way.

№ 02

Head to head

Side by side

The function is close. The differences that matter at renewal sit in the bundle and the contract model:

Abend-AID vs IBM Fault Analyzer, the licensing levers compared
DimensionAbend-AIDIBM Fault Analyzer
VendorBMC, former CompuwareIBM
Sits inBMC AMI DevX suiteIBM Application Delivery Foundation for z/OS
Licensing metricMIPS or MSU capacityIPLA, priced on capacity tier
Contract modelCapacity or BMC consumptionOne time charge plus subscription and support
Natural fitShops running the BMC AMI DevX toolsShops running the IBM ADFz tools
Switching costModerateModerate

Directional and pattern level. Branding, bundle composition, and consumption terms evolve, so confirm the current product names, the ADFz packaging, and the BMC agreement terms in your own schedules before modeling a renewal or a switch.

№ 03

Who should pick which

Decision

For most estates the bundle you already run points the way. Use it this way:

Lean toward IBM Fault Analyzer if

  • You already license the IBM Application Delivery Foundation for z/OS tools and can fold it into that family
  • You prefer the IPLA one time charge plus subscription and support shape over a recurring capacity charge
  • You are consolidating developer tooling into the IBM stack for support and integration reasons

Lean toward Abend-AID if

  • You run the broader BMC AMI DevX suite and gain from keeping fault diagnosis inside it
  • The BMC capacity or consumption model fits your estate better over the renewal horizon
  • Your developers rely on Abend-AID workflows that would be costly to rebuild

Either way, the first lever is the same as for any capacity priced tool: validate the licensed MIPS or MSU against the systems that genuinely need it, decide the contract model deliberately, and hold a prepared alternative as leverage in the incumbent's renewal.

№ 04

Frequently asked

FAQ
Q1
How are they licensed?Both on capacity. Abend-AID on MIPS or MSU inside the BMC AMI DevX suite; Fault Analyzer under IBM IPLA, one time charge plus subscription and support, inside ADFz.
Q2
Is switching worth it?Sometimes, since the switching cost is moderate. The driver is usually the bundle, with the alternative valuable as leverage because each vendor pursues displacement.
Q3
What decides the cost?The bundle each sits in, the contract model (BMC capacity or consumption versus IBM IPLA), and your incumbency plus a credible alternative.
Q4
What is the first lever?Validate the licensed MIPS or MSU against the systems that need it, choose the contract model deliberately, and prepare the alternative as leverage.

Close on features. The deal is won in the bundle and the leverage.

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

The bundle sets the price. We negotiate inside it.

Get expert help