① Journal · Renewal Playbook
InterTest is a Broadcom (CA) CICS and batch debugger, typically priced on MIPS or MSU capacity, not on developer seats, and often bundled with SymDump. Unlike an embedded SCM or database, a debugger is relatively displaceable, which is the buyer's advantage. The footprint, the bundle, the MCL model, and a real alternative are the levers. Here is what moves the number.
A debugger is priced like infrastructure but displaces like a tool.
InterTest is a Broadcom (CA) interactive testing and debugging product for CICS and batch applications written in COBOL, PL/I, and Assembler, frequently paired with SymDump in a single offering and now reachable from modern surfaces including a Visual Studio Code debugging extension. Like most of the Broadcom mainframe portfolio it is typically licensed on capacity, measured in MIPS or MSU, rather than on the number of developers who use it. That produces a useful tension. The product is priced like infrastructure, on the capacity of the environments it runs in, but functionally it sits much closer to the edge of the toolchain than an embedded source manager or database does, which makes it more displaceable than its pricing model implies.
That tension is the buyer's opening. On the cost side, because the metric is capacity, the number tracks the environments InterTest is entitled across, so consolidating and controlling that footprint moves the bill directly, while developer headcount is irrelevant to it. On the leverage side, the debugger market has real alternatives, IBM z/OS Debugger and the former Compuware Xpediter now in BMC AMI DevX among them, so a credible option to switch is a genuine threat rather than an empty one. Reading an InterTest renewal means working both: the capacity footprint that sets the price and the displaceability that the vendor would rather you forget. This builds on our InterTest licensing page and our Xpediter vs IBM Debug Tool comparison.
Lever · what it moves · how to pull it
| Lever | What it moves | How to pull it |
|---|---|---|
| Capacity footprint | The MIPS or MSU InterTest is licensed across drives the price | Consolidate environments; remove non production and dead capacity from scope |
| InterTest and SymDump bundle | How the pair is packaged affects the effective price | Price each component; confirm you use what the bundle entitles |
| MCL vs traditional MIPS | The model sets how all Broadcom capacity is charged | Model both and choose deliberately rather than accepting the default |
| Displaceable debugger market | A credible alternative is real walk away leverage | Cost IBM z/OS Debugger or BMC AMI DevX Code Debug as a switch option |
| Fiscal year timing | Quota pressure near Broadcom's year end softens the number | Align the close to Broadcom's autumn fiscal year end where possible |
InterTest is priced on capacity but lives at the edge of the toolchain. Control the footprint and keep the switch option real.
Capacity pricing makes InterTest feel embedded. The debugger market says otherwise.
Capacity based pricing tends to make every Broadcom product feel equally entrenched, because the bill arrives the same way whether the product is a deeply woven source manager or a debugging tool a team could swap. InterTest is firmly in the second category. A debugger is closer to the edge of the toolchain than an SCM or a DBMS; developers build habits and small integrations around it, but the workflow does not collapse if it changes the way it would if source control or a database moved. The market reflects that: IBM z/OS Debugger, the former Compuware Xpediter now in BMC AMI DevX, and other interactive debugging tools are real, functioning alternatives. Switching is not free, but it is a far lighter lift than replacing infrastructure, and that asymmetry is exactly the leverage a buyer should bring to the renewal.
Working that leverage well means making the alternative concrete rather than rhetorical. A costed switch plan, with the alternative debugger named, the migration effort estimated, and the developer retraining acknowledged, is a position the vendor must answer, where a vague threat is not. Combined with control of the MIPS or MSU footprint InterTest is priced on, clarity about how InterTest and SymDump are bundled so neither is paid for twice, a deliberate choice between traditional MIPS pricing and MCL, and timing aligned to Broadcom's autumn fiscal year end, the displaceability of the debugger becomes the spine of the negotiation. The product the vendor prices like infrastructure is the product the buyer can most plausibly replace. Our Broadcom (CA) contract review works the bundle, and our license negotiation service turns the switch option into a position.
InterTest is priced on MIPS or MSU, not developers. Map exactly what capacity it is entitled across, consolidate environments, and remove non production and dead capacity from scope, because that footprint is the number.
License the capacity you debug on, not the capacity you forgot about.
InterTest and SymDump are often packaged together. Price each component, confirm you actually use what the bundle entitles, and do not pay a combined number for a capability only half deployed.
A bundle you half use is a price you fully pay.
Debuggers are displaceable. Name the alternative, IBM z/OS Debugger or BMC AMI DevX Code Debug, estimate the migration and retraining effort, and bring a concrete switch plan rather than a vague threat the vendor can ignore.
A costed alternative is a threat; a vague one is noise.
Model traditional MIPS against MCL and choose on the numbers, and align the close to Broadcom's autumn fiscal year end where the term allows, so the vendor negotiates against its own quota clock as well as yours.
The model and the quarter are both part of the price.
⑤ The discipline that pays
InterTest is priced like infrastructure but displaces like a tool. Control the footprint and make the switch option real, and the number moves.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
InterTest is a Broadcom (CA) interactive debugger for CICS and batch in COBOL, PL/I, and Assembler, often paired with SymDump, and typically licensed on capacity in MIPS or MSU rather than developer count. The number tracks the environments it is entitled across, not team size. Many estates also have the option of Broadcom Mainframe Consumption Licensing.
More easily than core infrastructure. A debugger sits at the edge of the toolchain, and the market has real alternatives: IBM z/OS Debugger, the former Compuware Xpediter now in BMC AMI DevX, and others. Switching is not free, because developers build habits around a debugger, but it is a far lighter lift than replacing an embedded SCM or database, and that asymmetry is leverage.
Capacity footprint plus a displaceable market. Controlling the MIPS or MSU InterTest is licensed across moves the number directly, and a costed alternative gives real walk away credibility. Add a deliberate MIPS versus MCL choice, clarity on the SymDump bundle, and fiscal timing, and the renewal becomes negotiable.
Audit the capacity footprint and remove dead scope, unpack the SymDump bundle, cost a real switch to IBM z/OS Debugger or BMC AMI DevX Code Debug, model MIPS against MCL, and time the close to Broadcom's autumn fiscal year end. See our InterTest licensing page.
Related: InterTest licensing · Xpediter vs IBM Debug Tool · Broadcom (CA) contract review · MCL vs traditional MIPS licensing · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →