When Broadcom acquired CA Technologies in 2018, Easytrieve joined a portfolio of mainframe devops, security, and automation products—but the release numbering did not restart at version 1. Practitioners still upgrade along the 11.x line documented as CA Easytrieve Report Generator, with 11.6 as the current TechDocs baseline. Confusion is normal: license screens show CA product codes, STEPLIB datasets still say CA.EZTPLUS, and veterans cite 6.x PDFs while new hires read 11.6 Programming guides. This page maps Broadcom version naming, major 11.x milestones, SMP/E maintenance concepts, options table evolution, and how to align compile listings with the release notes that govern your migration. Treat version identity as operational fact—wrong manual, wrong PARM defaults, wrong reserved word list.
Official product title: CA Easytrieve Report Generator. Language/runtime name: Easytrieve Plus Report Generator when distinguishing from historical Classic. Marketing may say Broadcom Easytrieve. All refer to the supported product under Broadcom Mainframe Software—not a fork, not a compatibility layer. FMIDs and SMP/E receive records retain CA identifiers for continuity; support tickets may request both CA legacy numbers and Broadcom case IDs during transition years.
| Version era | Vendor | Highlights |
|---|---|---|
| Classic / Pansophic | Ribek, Pansophic | Batch FILE/JOB/REPORT core |
| CA Plus 6.x | Computer Associates | SQL FILE, SCREEN, distributed ports, 6.x options table |
| 11.0 – 11.5 | CA then Broadcom | WORKFILE, larger modules, SQL FILE updates, transitional docs |
| 11.6 | Broadcom | Current TechDocs, function mode reserved words, GUI/VS Code tooling |
Exact FMID spellings and end-of-support dates change with Broadcom announcements—verify on TechDocs for your contract year. Migration projects anchor on installed FMID, not memory of conference slides.
Broadcom TechDocs organize 11.6 into Getting Started, Programming, Language Reference, Installation, Messages and Codes, and Release Notes. Developers migrating from 6.x should read Release Difference documents alongside Language Reference—statement spellings, deprecated options, and behavioral notes appear there before you encounter them in compile listings. 11.6 also documents Symbols and Reserved Words appendices critical for function mode cutover.
Systems programmers install Easytrieve through SMP/E with functional FMIDs and apply PTFs that increment maintenance levels. Developers experience the result as compiler message text changes, new reserved words, or fixed abends—not as abstract inventory rows. Before blaming source code for a migration failure, confirm test LPAR FMID matches the release notes PDF on your desk. A program compiling on an older maintenance level may fail on production after PTF apply—or vice versa when test lags production.
Keep a site standard table: production FMID, test FMID, compile proc STEPLIB order, authorized PARM profile, and options table DSN. Change control updates the table when PTS bundles promote.
A major version boundary for operations—not just developers—is options table format. CA 6.x sites often used installation-defined table layouts; 11.x on z/OS expects a file-based options table, commonly referenced by EZOPTBL DD in compile and go JCL. Broadcom supplies a conversion utility; run it in test, diff output, and validate buffer and abend settings before mass recompile. Wrong options produce silent performance degradation or unexpected ABEXIT behavior even when programs compile cleanly.
12345//EZTCOMP EXEC PGM=EZTPA00,REGION=0M //STEPLIB DD DSN=CA.EZTPLUS.R11.LOAD,DISP=SHR //EZOPTBL DD DSN=SITE.EZT.OPTBL.FILE,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSIN DD DSN=DEV.EZT.SRC(PAYRPT),DISP=SHR
Release notes across 11.x highlight themes migration teams should map to test plans:
| Theme | Developer impact | Operations impact |
|---|---|---|
| WORKFILE support | Temporary file grammar in programs | DD space, DASD management |
| SQL FILE automation | Simpler SELECT patterns; verify old explicit style | Db2 auth unchanged |
| Function mode / reserved words | Field renames, SET/EXECUTE collisions | Compile PARM standards updated |
| GUI Workbench / VS Code | IDE editing, not runtime syntax | Developer workstation packaging |
| REGION=0M guidance | Larger programs compile | JCL REGION on compile procs |
Broadcom documents Plus runtimes for z/OS, z/VM, z/VSE, UNIX, Linux, and Windows. Version numbers align conceptually but installation media and FMIDs differ. A shop may standardize on 11.6 language semantics on z/OS while distributed servers lag one maintenance level—document the skew. FILE statements aim for portability; path names, sort utilities, and code pages still differ by platform.
Broadcom versions are like edition numbers on a cookbook. Your kitchen might still have the 6th edition (CA 6.x) while the store sells the 11th edition (11.6). Most recipes look similar, but some ingredient names changed and the oven settings page moved (EZOPTBL). Before cooking for a big party, check which edition your kitchen actually uses and read the "what changed" page in the new book.
1. The current Broadcom documentation baseline for Easytrieve is:
2. After Broadcom acquired CA Technologies in 2018, Easytrieve support moved to:
3. EZOPTBL DD on z/OS 11.x identifies:
4. SMP/E maintenance for Easytrieve is tracked using:
5. GUI Workbench and VS Code extension appear in:
Broadcom documents the 11.x line with 11.6 as the current TechDocs baseline. Earlier CA 6.x and transitional 11.0 releases remain relevant for migration projects comparing release notes to installed FMIDs.
Systems programmers check SMP/E FMID inventory, module levels in STEPLIB, compile listing headers, and Broadcom receive logs. Developers should ask operations for the authorized production FMID before citing syntax from the wrong manual.
Licensing is contract-specific. Broadcom product documentation lists supported platforms; your account team confirms which runtimes are entitled. This tutorial describes technical versions, not commercial SKUs.
On Broadcom TechDocs under CA Easytrieve Report Generator — Release Notes and Release Difference documents for 11.6 and prior 11.x maintenance.
Not always immediately. Shops often compile in compatibility mode while fixing reserved words, then enable function mode for new language features. Release notes define PARM and options controlling mode behavior.