Product · Broadcom (CA) Dispatch

CA Dispatch: output management with a high cost to leave.

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.

№ 01

What it is

Output managementz/OS

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.

№ 02

How it is licensed

CapacityMIPS / MSUMCL

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.

CA Dispatch licensing at a glance
AttributeDetail
Product typeReport distribution and output management
MetricMainframe capacity (MIPS, or MSU under MCL)
Legacy modelContracted MIPS set at signature
Current directionMainframe Consumption Licensing (MCL)
RemovabilityLow; 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.

№ 03

Cost drivers

CapacityStickiness

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.

№ 04

Audit traps

Capacity driftBundling

CA Dispatch exposure is mostly about scope and how it is counted. Common traps we see at pattern level:

Where exposure hides

  • Contracted capacity set when the estate was larger and never reset as the footprint shrank
  • Dispatch running on LPARs or machines that fall outside the assumed licensed scope
  • Disaster recovery and test instances carrying the product without a distinct entitlement line
  • Output management bundling that obscures whether Dispatch capacity is counted once or rolled in with CA View or CA Deliver
  • An MCL transition accepted without checking how it meters a product whose usage does not follow machine peak
№ 05

Renewal levers

5 levers

Dispatch is sticky, so the leverage comes from visibility and data rather than an easy exit. The five that pay:

Buyer side levers

  • Reconcile capacity: prove the MSU the estate actually runs against the contracted figure and reset a commitment sized for a larger past
  • Unbundle the output stack: make the vendor show what Dispatch costs separately from CA View and CA Deliver so each line can be defended
  • Scrutinize the model change: model how MCL would meter Dispatch before agreeing, since the transition is negotiable
  • Scope non-production: decide where Dispatch really needs to run in test and DR rather than letting entitlements default on
  • Cost a real exit: if modernization of output management is on the roadmap, scope it properly so it carries weight, rather than bluffing a switch the archive makes hard
№ 06

Alternatives, where credible

Reality check

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.

№ 07

Frequently asked

FAQ
Q1
How is CA Dispatch licensed?On mainframe capacity, historically contracted MIPS, now moving onto MSU metered MCL. The charge follows the machine size, not report volume.
Q2
Why is it hard to replace?It stores captured output in VSAM that downstream processes and retention rules depend on. Replacing it means migrating an archive and re plumbing every consumer, an output management project.
Q3
What are the audit risks?Mostly capacity drift and scope: a stale contracted figure, capacity on out of scope LPARs, DR and test instances, and bundling that hides whether it is counted once.
Q4
What moves the number?Reconciling capacity to actual MSU, unbundling it from CA View and CA Deliver, and scrutinizing an MCL transition before agreeing to it.

Hard to leave is not the same as fairly priced.

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

The archive locks you in. We help you price the lock fairly.

Get expert help