CA View licensing: the archive runs on capacity, not volume.

CA View is Broadcom (CA) output management software, the system that captures, archives, indexes, and retrieves report and spool output on z/OS. It is the product that lets users find and view historical reports long after the job that produced them has finished, and it underpins retention and compliance requirements in estates that generate large volumes of printed and electronic output. It is frequently deployed alongside CA Deliver, which handles report distribution, and together they form the output management backbone in many CA shops. That pairing is central to how its cost should be read.

CA View is licensed on capacity, not on the volume of report data it stores. Historically that has meant a MIPS or MSU based charge tied to the machines or LPARs where the product runs, and Broadcom has been moving its mainframe customers toward Mainframe Consumption Licensing (MCL), which prices on measured MSU consumption reported through SCRT across the production environment. Whether your CA View entitlement is a legacy capacity license or sits under a consumption agreement depends on your contract. The distinction between license metric and archive size matters, because cost follows the capacity of the system, while the archive volume is an operational and storage concern.

The first driver is the licensed capacity baseline, which can sit above current need when it was set before a hardware change and never revisited. The second is the output management bundle, since CA View is often acquired with CA Deliver and related components, and a suite price can carry pieces that are no longer used. The third is portfolio context, because Broadcom renews its mainframe products together and uplift pressure on the whole CA estate flows through to CA View. The MIPS to MSU conversion sits underneath all three, because a conversion done on the vendor's assumptions can quietly raise the licensed position during a transition.

CA View exposure comes from its bundle and its breadth. Common traps we see at pattern level:

CA View responds to the portfolio levers, applied with the output management bundle in mind. The five that pay:

Output management and archival is a competitive category, and CA View has a genuine alternative in IBM Content Manager OnDemand (CMOD) and other report archive platforms. Displacement is real leverage, but a migration is not trivial: years of archived output, indexes, and retention policy have to move, and the retrieval applications and user workflows that depend on them have to be rebuilt or repointed. That makes a switch a project to be costed honestly rather than a quick renewal saving. The more common move is to use a credible alternative as a reference point in the Broadcom renewal while consolidating any duplicate archive tooling already in the estate.