① Product · Broadcom (CA) InterTest
CA InterTest is a developer debugging tool, yet it is licensed on mainframe MSU capacity rather than on the programmers who use it. The population that touches the tool is small; the capacity it is priced against is not. Closing that gap is the renewal play.
CA InterTest is Broadcom (CA)'s interactive testing and debugging tool for mainframe applications, used by programmers to step through and diagnose COBOL, Assembler, and CICS code as it runs. It is a productivity tool for a development team rather than a production runtime, which shapes both how it should be deployed and how its licensing mismatch arises. A tool whose entire value is to a group of developers is, in the CA model, still priced against the capacity of the machines it is authorized on.
CA InterTest is licensed on capacity, in line with the rest of the Broadcom (CA) mainframe portfolio: typically the MSU rating of the machines or LPARs where it is authorized, with older agreements written in MIPS. It is a capacity entitlement under a multi year contract rather than a per seat or per developer charge, so the price tracks the authorized capacity of the environment, not the number of people who debug with it. Broadcom also offers Mainframe Consumption Licensing (MCL), a usage based subscription that can bundle development tools like InterTest under a committed baseline.
| Attribute | Detail |
|---|---|
| Charge model | Capacity entitlement, multi year agreement |
| Metric | MSU capacity (older deals in MIPS) |
| Priced on | Authorized machine or LPAR capacity |
| Not priced on | Number of developers or seats |
| Consumption option | Mainframe Consumption Licensing (MCL) |
Directional, pattern level. Confirm your own metric and authorized capacity against the contract schedules before modeling a renewal.
The primary driver is authorized capacity. Because InterTest is priced to the MSU of the machines it can run on, a tool used by a development group can carry a cost built on production scale capacity it never needs. The second driver is the renewal mechanics commonly observed across Broadcom (CA) agreements: per unit rate uplift and annual escalator clauses that lift the cost whether or not your usage moved. The third is portfolio bundling, where InterTest sits inside a larger CA deal and its individual cost is hard to see, which makes it easy to over renew.
InterTest exposure usually comes from where it is installed relative to where it is licensed. Common traps we see at pattern level:
Where exposure hides
The cost is built on capacity a debugger does not need, so the levers center on shrinking that footprint. The five that pay:
Buyer side levers
Unlike a system of record, a debugging tool is genuinely replaceable, which gives InterTest more credible alternatives than most CA products. IBM Debug for z/OS and Compuware (BMC) Xpediter cover similar interactive debugging ground, and a shop unhappy with the capacity based pricing can evaluate a switch with less existential risk than displacing a source manager or a scheduler. That said, retraining a development team and rebuilding debugging workflows still carries real cost, so the switching threat is most useful when it is genuinely prepared. For many estates the faster win is simply to confine InterTest to development capacity and discipline the renewal terms.
A few developers, a big capacity bill. Close the gap.
Metric explainers: Broadcom Mainframe Consumption Licensing (MCL) explained and hardware model capacity ratings and software cost. Sibling products: CA Endevor licensing and CA Spool licensing. Hub and commercial: the Broadcom (CA) buyer side guide and Broadcom (CA) license negotiation.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.