① Product · Broadcom (CA) Dispatch
CA Dispatch captures, archives, and distributes the report output of your mainframe applications, holding it in VSAM stores that downstream processes and retention rules depend on. It is licensed on capacity, and its switching cost is exactly why it holds its price unless you reconcile the capacity and make the line visible.
CA Dispatch is a report distribution and output management product for z/OS. It captures the printed and electronic output that mainframe applications generate, archives it in a central repository, and distributes it to the people and systems that consume it, with the retention and access controls that regulated reporting demands. It is the kind of utility that runs quietly for years in the background of back office operations, which is precisely why its licensing is rarely examined until a renewal forces the question.
CA Dispatch is licensed on mainframe capacity, consistent with the Broadcom (CA) portfolio. The legacy model is a contracted MIPS entitlement set at signature; Broadcom has been moving products onto Mainframe Consumption Licensing (MCL), which meters against MSU consumption. The charge tracks the size of the machine, not the number of reports captured, pages archived, or recipients served. So however heavily Dispatch is used, the cost lever is the same: does the contracted capacity still reflect the estate it runs on, and how would a model change meter that estate.
| Attribute | Detail |
|---|---|
| Product type | Report distribution and output management |
| Metric | Mainframe capacity (MIPS, or MSU under MCL) |
| Legacy model | Contracted MIPS set at signature |
| Current direction | Mainframe Consumption Licensing (MCL) |
| Removability | Low; archive migration carries real switching cost |
The VSAM stored archive and its downstream consumers are the source of the switching cost, and the reason the line holds its price.
The base driver is contracted capacity, and like most background utilities Dispatch is prone to carrying a figure set for a larger estate. The second driver is its stickiness: because the archive and its consumers are hard to move, the vendor can hold price at renewal with little fear of displacement. The third is bundling. Dispatch typically sits inside a CA output management or portfolio agreement alongside products such as CA View and CA Deliver, where a single capacity figure and uplift hide what each output product costs on its own.
CA Dispatch exposure is mostly about scope and how it is counted. Common traps we see at pattern level:
Where exposure hides
Dispatch is sticky, so the leverage comes from visibility and data rather than an easy exit. The five that pay:
Buyer side levers
Alternatives to CA Dispatch exist, including IBM and third party output management platforms and Broadcom's own CA View and CA Deliver line, but moving is not light work. The archive of captured output, its retention rules, and every downstream consumer of distributed reports all have to migrate, which makes displacement an output management program rather than a renewal lever. A modernization initiative that consolidates or replaces output management can be a genuine long term alternative and a negotiation backdrop, but only if it is costed and resourced; an unscoped threat will not move a vendor who knows how hard the archive is to leave.
Hard to leave is not the same as fairly priced.
Metric explainers: Broadcom Mainframe Consumption Licensing (MCL) and MIPS explained. Sibling products: Top Secret licensing and Easytrieve licensing. Hub and commercial: the Broadcom buyer side guide and Broadcom audit defense.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.