Product · Broadcom (CA) InterTest

CA InterTest: a debugger priced on machine capacity.

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.

№ 01

What it is

Debugging toolz/OS

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.

№ 02

How it is licensed

MSU capacityMCL option

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.

CA InterTest licensing at a glance
AttributeDetail
Charge modelCapacity entitlement, multi year agreement
MetricMSU capacity (older deals in MIPS)
Priced onAuthorized machine or LPAR capacity
Not priced onNumber of developers or seats
Consumption optionMainframe Consumption Licensing (MCL)

Directional, pattern level. Confirm your own metric and authorized capacity against the contract schedules before modeling a renewal.

№ 03

Cost drivers

Authorized capacityEscalators

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.

№ 04

Audit traps

Authorized footprintProd creep

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

  • Debugging tools left installed on production LPARs they were never meant to run on, pulling production capacity into scope
  • Authorized capacity that followed a hardware upgrade upward without anyone truing it down to actual need
  • Test and disaster recovery environments whose coverage the entitlement does not clearly state
  • Portfolio agreements where InterTest's authorized capacity cannot be cleanly reconciled against deployment
  • Stale install footprints left after a development environment was reorganized or consolidated
№ 05

Renewal levers

5 levers

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

  • Confine to development: authorize InterTest only on the development and test capacity where debugging actually happens, and remove it from production scope
  • Challenge the escalators: cap or strip the annual uplift clauses that quietly raise the rate every year
  • Unbundle the view: model InterTest's own cost inside any portfolio deal so the gap between price and usage is visible
  • Right size against real users: align the capacity to the small population that uses the tool rather than to the whole estate
  • Model MCL carefully: test the consumption option only with a clear eye on how the baseline and its growth terms are set
№ 06

Alternatives, where credible

Reality check

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.

№ 07

Frequently asked

FAQ
Q1
How is CA InterTest licensed?On mainframe capacity, typically MSU (older deals in MIPS), as a multi year entitlement tied to authorized machine or LPAR capacity rather than developer count.
Q2
Is it priced per developer?Typically no. It is priced on authorized capacity, so a tool used by a few programmers can be billed against a large block of MSU. That mismatch is the cost story.
Q3
Does MCL cover InterTest?It can. Mainframe Consumption Licensing bundles CA tools under a committed baseline. Whether it helps depends on how that baseline and its growth are set against real usage.
Q4
How do you cut the cost?Confine InterTest to development and test capacity, remove production authorization, and cap the annual escalators so the rate is built on a smaller, real footprint.

A few developers, a big capacity bill. Close the gap.

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

Priced on capacity, used by a few. We help you right size it.

Get expert help