CA Datacom: a capacity priced database inside the bundle.

CA Datacom is a high performance mainframe database from Broadcom (CA), part of the database and development portfolio inherited from CA Technologies. It runs through its Multi User Facility and underpins transaction heavy applications in organizations that standardized on it years ago, often alongside or instead of Db2. Like CA IDMS, it is core infrastructure: the applications are written to it, the data lives in it, and that embeddedness is exactly what shapes the licensing conversation.

CA Datacom is capacity licensed. The traditional model prices it on the MIPS or MSU capacity of the machine or LPAR where it runs, not on measured database activity, so the bill tracks the size of the environment rather than how hard the database works. Broadcom also offers Mainframe Consumption Licensing (MCL), a usage based subscription spanning the mainframe portfolio for a committed annual figure. Which model applies, and the capacity basis it is measured on, is set in your agreement, and a renewal is often where Broadcom seeks to move you between them.

The MIPS to MSU restatement is where capacity contracts shift. See the MIPS to MSU conversion question before accepting a rebased renewal.

The primary driver is the licensed capacity figure, since the bill scales with the MIPS or MSU of the environment regardless of how much the database is actually exercised. The second is the bundle: Datacom commonly renews inside a portfolio package, and the consolidated number can carry families and tools you no longer use, with Broadcom uplifts applied across the whole bundle at renewal. The third is the model transition itself, because moving from MIPS to MSU, or from capacity to MCL, restates the baseline and can lift spend if the new basis is accepted without independent modeling.

Capacity licensing turns environment sprawl into exposure. Common traps we see at pattern level:

The levers work on capacity, on the bundle, and on the model transition. The five that pay:

There is no drop in replacement for a production Datacom estate. Applications are written to its access paths, and a move to Db2 or another database is a multi year migration carrying real risk. The credible alternatives are about footprint and posture: retiring unused databases, consolidating to lower licensed capacity, and holding a documented migration assessment as negotiating weight. A migration can be the right long term answer for a shrinking estate, but as a renewal lever its value is the credibility of the threat, not a switch you flip mid term.