How are Strobe and IBM APA licensed?

Both are z/OS application performance analysis tools that profile where CPU goes in COBOL, Assembler, PL/I, and other programs, but they sit in different vendor models. Compuware (BMC) Strobe, now BMC AMI Strobe, is commonly licensed on mainframe capacity in MSU and typically negotiated within a wider BMC AMI or Compuware portfolio agreement. IBM Application Performance Analyzer for z/OS, often shortened to APA, is part of IBM's application development tooling and is licensed under IBM's IPLA model with annual subscription and support, inside the wider IBM z/OS relationship. Confirm the exact metric on each in your own schedules, because performance tooling terms vary more than runtime products.

Is it worth switching between Strobe and IBM APA?

Performance profilers are more displaceable than core infrastructure because they are used by performance and development teams rather than woven into every production job, so a switch is more feasible here than for a database or a security manager. Even so, it is rarely a pure cost play once you count retraining, the loss of historical baselines, and the workflow rebuild. The alternative is most valuable as leverage: a credible evaluation of the competing profiler disciplines the incumbent's renewal, and it can often ride on a modernization or tooling consolidation program already underway. The usual win is a better deal on what you run.

What decides Strobe versus IBM APA cost?

The bundle and the leverage, more than the feature sheet. For Strobe, how it is priced and packaged within the wider BMC AMI and Compuware portfolio deal is the main driver; for APA, how it sits inside your IBM IPLA, subscription and support, and overall IBM z/OS relationship. On both sides, right sizing the licensed scope to the teams and environments that genuinely profile performance is the foundational lever, and a prepared evaluation of the rival is the negotiation backdrop. Because both vendors would happily displace the other on tooling, that backdrop has real weight.

Strobe vs IBM APA: Tooling Costs

Strobe vs IBM APA: priced by the bundle, not the profile.

Compuware (BMC) Strobe, now BMC AMI Strobe, and IBM Application Performance Analyzer (APA) both profile where CPU goes in z/OS applications. The function overlaps; the licensing does not. Strobe is usually negotiated inside the BMC AMI portfolio, APA inside IBM IPLA. The bundle and the leverage decide the cost.

Keep your incumbent profiler and price it against the rival. Strobe and APA both do the core job, identifying the CPU intensive code paths that drive cost, well enough that a switch is rarely justified by features. Performance tooling is more displaceable than infrastructure, which makes the alternative a usable lever, but a migration still costs retraining and the loss of historical baselines, so it rarely pays as a pure cost move. The decision turns on packaging: Strobe inside the BMC AMI and Compuware portfolio deal, APA inside your IBM IPLA and z/OS relationship. Right size the scope, prepare the competing evaluation, and the prize is usually a better deal on what you already run.

Strobe vs IBM APA, the licensing levers compared
Dimension	BMC AMI Strobe	IBM APA
Vendor	BMC (Compuware heritage)	IBM
Branding	BMC AMI Strobe, formerly Compuware Strobe	IBM Application Performance Analyzer for z/OS
Function	Application performance measurement and profiling	Application performance measurement and profiling
Languages	COBOL, Assembler, PL/I, C, with Db2, IMS, CICS	COBOL, Assembler, PL/I, C/C++, with Db2, IMS, CICS, MQ
Typical licensing	MSU capacity, within BMC AMI portfolio deal	IPLA with subscription and support, IBM ADTools
Bundle context	Compuware and BMC AMI tooling stack	IBM z/OS development tooling relationship
Displacement posture	Targets IBM tooling estates	Bundled appeal across IBM development tools

Strobe vs IBM APA, the licensing levers compared

Dimension

BMC AMI Strobe

IBM APA

Vendor

BMC (Compuware heritage)

IBM

Branding

BMC AMI Strobe, formerly Compuware Strobe

IBM Application Performance Analyzer for z/OS

Function

Application performance measurement and profiling

Languages

COBOL, Assembler, PL/I, C, with Db2, IMS, CICS

COBOL, Assembler, PL/I, C/C++, with Db2, IMS, CICS, MQ

Typical licensing

MSU capacity, within BMC AMI portfolio deal

IPLA with subscription and support, IBM ADTools

Bundle context

Compuware and BMC AMI tooling stack

IBM z/OS development tooling relationship

Displacement posture

Targets IBM tooling estates

Bundled appeal across IBM development tools

For most estates this is a renewal decision shaped by which vendor stack you already lean on. Use it this way:

Stay with the incumbent and negotiate if

The profiler is established in your performance practice with historical baselines your teams rely on
A prepared evaluation of the competing tool gives you a credible walk away to discipline the renewal
Right sizing the licensed scope and packaging the tool well within the wider deal capture most of the saving

Genuinely consider switching if

You are consolidating onto one vendor's tooling stack, all IBM or a broad BMC AMI footprint, and the bundle economics favor it
A modernization program is already funding the retraining and workflow rebuild a switch requires
The competing vendor offers terms large enough to clear the real migration and baseline rebuild cost

Either way, the first lever is the same: confine the tool to the teams and environments that genuinely profile performance, right size the licensed scope, and treat the rival's quote as the backdrop that disciplines the number.

How are they licensed?Strobe commonly on MSU capacity within a BMC AMI portfolio deal; APA under IBM IPLA with subscription and support inside the wider IBM relationship.

Is switching worth it?Profilers are more displaceable than infrastructure, but a switch still costs retraining and lost baselines. The alternative is most valuable as leverage.

What decides the cost?The bundle and the leverage more than features. Packaging within the BMC AMI or IBM stack, right sized scope, and a credible rival evaluation.

What is the first lever?Confine the tool to the teams and environments that genuinely profile performance, and right size the licensed scope before renewal.

Same profile. Different bundle. The bundle is the deal.

Explainers: IPLA one time charge licensing explained and single vendor vs best of breed tooling costs. Related comparison: Abend-AID vs IBM Fault Analyzer. Products: Strobe licensing and Xpediter licensing. Hubs and commercial: the Compuware buyer side guide, the IBM buyer side guide, and Compuware cost optimization.

Strobe vs IBM APA: priced by the bundle, not the profile.

The verdict

Head to head

Who should pick which

Frequently asked

The profilers are even. The bundles are not.