Product · Broadcom (CA) Easytrieve

Easytrieve: the small line that renews on autopilot.

CA Easytrieve Report Generator is a reporting language, not a system of record, so it usually rides inside a larger Broadcom (CA) portfolio agreement where nobody revisits it. It is licensed on capacity, and a stale capacity figure carried for years is exactly the kind of quiet overspend that adds up.

№ 01

What it is

Reporting languagez/OS

CA Easytrieve Report Generator is a high level reporting and data extraction language for z/OS, long used to pull, summarize, and format data from VSAM, sequential files, and databases without writing full COBOL. Decades of report jobs and extract routines across banking, insurance, and government back offices are written in it. It is productive and embedded in operational reporting, but it is application tooling, not core infrastructure, and that distinction shapes both its cost profile and its leverage.

№ 02

How it is licensed

CapacityMIPS / MSUMCL

Easytrieve is licensed on mainframe capacity, consistent with the rest of the Broadcom (CA) portfolio. The legacy model is a contracted MIPS entitlement fixed at signature; Broadcom has been migrating products onto Mainframe Consumption Licensing (MCL), which meters against MSU consumption. Either way the charge follows the size of the machine, not how many Easytrieve programs run or how much reporting they produce. So the cost question is never about usage volume; it is whether the contracted capacity still reflects the estate Easytrieve actually runs on.

Easytrieve licensing at a glance
AttributeDetail
Product typeReporting and data extraction language
MetricMainframe capacity (MIPS, or MSU under MCL)
Legacy modelContracted MIPS set at signature
Current directionMainframe Consumption Licensing (MCL)
RemovabilityModerate; logic can be converted with effort

Because Easytrieve is application logic rather than infrastructure, it has more credible exit paths than most CA products, which matters at the table.

№ 03

Cost drivers

CapacityBundling

The base driver is contracted capacity, and because Easytrieve is rarely the product anyone is watching, its capacity figure is among the most likely to be stale. The second driver is bundling. Easytrieve almost always renews inside a multi product CA agreement, where one capacity figure and one uplift cover the whole portfolio and the individual line is invisible. A small product carried for years at a footprint the business has since shrunk is the textbook case of cost that nobody decided to keep paying, it simply was never questioned.

№ 04

Audit traps

Capacity driftShadow installs

Easytrieve exposure is mostly about scope and drift. 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
  • Easytrieve installed and running on LPARs or machines outside the assumed licensed scope
  • Copies left active in test, development, or disaster recovery environments without a clear entitlement line
  • Portfolio bundling that makes it impossible to see whether Easytrieve capacity is counted once or rolled into another product
  • An MCL transition accepted without checking how the model would meter a product whose usage does not track machine peak
№ 05

Renewal levers

5 levers

Easytrieve has more exit optionality than most CA products, so the levers combine visibility with a credible alternative. The five that pay:

Buyer side levers

  • Unbundle it: make the vendor show what Easytrieve costs as its own line, so a small product stops hiding inside a portfolio uplift
  • Reconcile capacity: prove the MSU the estate actually runs against the contracted figure and reset a commitment sized for the past
  • Scope the conversion: cost the effort to rewrite the Easytrieve estate in COBOL, SQL, or a compatible compiler, so the alternative is real, not rhetorical
  • Decide the install base: confirm where Easytrieve is genuinely needed and retire entitlements for environments that no longer use it
  • Test the model change: before accepting MCL, model how it meters a reporting tool against your real consumption rather than assuming parity
№ 06

Alternatives, where credible

Reality check

Easytrieve is one of the more replaceable products in the CA portfolio, because its programs are reporting and extract logic rather than infrastructure. That logic can be rewritten in COBOL, expressed in SQL where the data sits in a database, moved to another reporting tool, or recompiled with a third party Easytrieve compatible compiler. None of these is free; a large Easytrieve estate represents real conversion effort and testing. But a costed migration plan is a genuine lever here in a way it rarely is elsewhere on the mainframe, and even an unexecuted plan reshapes the renewal conversation.

№ 07

Frequently asked

FAQ
Q1
How is Easytrieve licensed?On mainframe capacity, historically contracted MIPS, now moving onto MSU metered MCL. The charge follows the machine size, not how many reports run.
Q2
Why does it get overlooked?It is a small reporting line inside a larger CA portfolio agreement, so its capacity figure is rarely revisited and it renews on autopilot inside a bundle.
Q3
Are there alternatives?Yes. Easytrieve logic can be rewritten in COBOL or SQL, moved to another reporting tool, or recompiled with a compatible compiler. It has more exit optionality than most CA products.
Q4
What moves the number?Unbundling it for visibility, reconciling contracted capacity to actual MSU, and scoping a real conversion path so the alternative carries weight at the table.

A small line still deserves a hard look.

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

It renews on autopilot. We help you take the wheel.

Get expert help