How are Xpediter and IBM Debug Tool licensed?

Compuware (BMC) Xpediter, now carried within the BMC AMI DevX Code Debug line, is licensed on mainframe MSU or MIPS capacity of the LPARs it runs on, controlled through the Compuware License Management System. The IBM debugger long sold as IBM Debug Tool has been superseded by IBM z/OS Debugger, which IBM ships through IBM Debug for z/OS and as part of IBM Developer for z/OS. The IBM product is commonly an IPLA style entitlement with one time charge plus subscription and support, and its capability is frequently already bundled into a Developer for z/OS seat. So one side is a capacity priced premium tool and the other is often effectively included in an IDE entitlement the shop already owns.

Is it worth switching from Xpediter to the IBM debugger?

A debugger is lighter to switch than a scheduler or a source code manager, because there is no source history or schedule to convert, only developer habit and workflow to retrain. That makes the IBM z/OS Debugger a more credible alternative than many mainframe peers, especially where the estate already licenses IBM Developer for z/OS and the debugger capability is therefore largely paid for. The friction is real but bounded: developer productivity dips during retraining, and teams accustomed to Xpediter features such as code coverage and reverse execution will weigh whether the IBM tool meets their workflow. The decision usually turns on whether the IBM capability is already in the stack and whether the premium for Xpediter is justified by features the team genuinely uses.

What decides Xpediter versus IBM Debug Tool cost?

Three things. First, whether the IBM debugger is already bundled into a Developer for z/OS entitlement you hold, which can make it effectively a sunk cost and reframes the Xpediter spend as incremental. Second, the licensed mainframe capacity Xpediter is priced on, the MSU or MIPS of the authorized LPARs, the primary lever on the Compuware side. Third, the strength of the workflow case, since Xpediter's premium rests on features and developer familiarity, and a buyer should test whether those are used enough to justify the gap. Feature parity for core source level debugging is close, so licensing and what you already own drive the number.

Xpediter vs IBM Debug Tool: Licensing

Xpediter vs IBM Debug Tool: what you already own decides it.

Compuware (BMC) Xpediter and the IBM debugger now branded z/OS Debugger both deliver source level debugging for COBOL, PL/I, and more. Core parity is close. What moves the number is whether the IBM capability is already bundled into a Developer for z/OS entitlement you hold, the capacity Xpediter is priced on, and whether its premium features earn their keep.

Start by checking what you already own. The IBM debugger, superseded from Debug Tool to z/OS Debugger, is frequently bundled into an IBM Developer for z/OS entitlement, so where the estate already licenses IDz the capability is largely paid for, and the Xpediter spend becomes incremental rather than essential. A debugger is also one of the lighter mainframe tools to switch, since there is no source history or schedule to convert, only developer habit to retrain. The decision turns on two questions: is the IBM capability already in your stack, and does Xpediter's premium, its code coverage, reverse execution, and developer familiarity, get used enough to justify the gap. Answer both before you renew.

Xpediter vs IBM Debug Tool, the licensing levers compared
Dimension	Compuware (BMC) Xpediter	IBM Debug Tool / z/OS Debugger
Vendor	Compuware, now BMC	IBM
Current branding	Xpediter, within BMC AMI DevX Code Debug	IBM z/OS Debugger, shipped via Debug for z/OS and Developer for z/OS
Naming note	Long established Compuware debugger	IBM Debug Tool superseded by IBM z/OS Debugger
Licensing metric	MSU or MIPS capacity, via Compuware LMS	Commonly IPLA one time charge plus S&S, or per authorized user
Bundling	Standalone or within a BMC AMI DevX deal	Frequently bundled into IBM Developer for z/OS (IDz)
Switching weight	Premium incumbent, developer familiarity	Often already owned; retraining is the main cost

Xpediter vs IBM Debug Tool, the licensing levers compared

Dimension

Compuware (BMC) Xpediter

IBM Debug Tool / z/OS Debugger

Vendor

Compuware, now BMC

IBM

Current branding

Xpediter, within BMC AMI DevX Code Debug

IBM z/OS Debugger, shipped via Debug for z/OS and Developer for z/OS

Naming note

Long established Compuware debugger

IBM Debug Tool superseded by IBM z/OS Debugger

Licensing metric

MSU or MIPS capacity, via Compuware LMS

Commonly IPLA one time charge plus S&S, or per authorized user

Bundling

Standalone or within a BMC AMI DevX deal

Frequently bundled into IBM Developer for z/OS (IDz)

Switching weight

Premium incumbent, developer familiarity

Often already owned; retraining is the main cost

This is decided as much by your IBM tooling position as by the debugger itself. Use it this way:

Keep Xpediter and negotiate if

Your developers rely on Xpediter specific features such as code coverage and reverse execution day to day
The team's productivity case for the premium is genuine, not just habit, and a retraining dip would be costly
A credible move to the IBM debugger gives you a costed walk away to discipline the Xpediter renewal on capacity

Lean to the IBM debugger if

You already license IBM Developer for z/OS, so z/OS Debugger is largely paid for and the Xpediter spend is incremental
You are standardizing the development toolchain on IBM and want fewer vendors in the lifecycle
The premium features are used by few enough developers that the gap no longer justifies itself

Either way, two foundational levers apply: confirm what z/OS Debugger capability you already own in existing IDz entitlements, and right size the licensed MSU on the Xpediter side to the LPARs that genuinely need it.

How are they licensed?Xpediter on MSU or MIPS capacity via Compuware LMS. The IBM debugger, now z/OS Debugger, is commonly IPLA plus S&S or bundled into Developer for z/OS.

Is switching worth it?Lighter than switching a scheduler or SCM, since there is no data to convert, only retraining. It is most attractive where you already own the IBM capability.

What decides the cost?Whether z/OS Debugger is already bundled in your IDz seats, the capacity Xpediter is priced on, and whether its premium features are genuinely used.

What is the first lever?Audit your existing Developer for z/OS entitlements for debugger capability, then right size the Xpediter MSU to the LPARs that need it.

The cheapest debugger is often the one you already paid for.

Explainers: MSU explained and mainframe TCO, the real cost model. Sibling products: Compuware Xpediter licensing, Topaz Workbench licensing, and IBM Z Development and Test Environment licensing. Other comparison: BMC AMI DevX vs Compuware Topaz. Hubs and commercial: the Compuware buyer side guide, the IBM buyer side guide, BMC license negotiation, and IBM MSU optimization.

Xpediter vs IBM Debug Tool: what you already own decides it.

The verdict

Head to head

Who should pick which

Frequently asked

Maybe you already own it. We check before you renew.