Broadcom Easytrieve Versions

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.

Progress0 of 0 lessons

Naming: Broadcom, CA, Plus, Report Generator

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.

Release Line Overview

Easytrieve version eras (migration-oriented)
Version eraVendorHighlights
Classic / PansophicRibek, PansophicBatch FILE/JOB/REPORT core
CA Plus 6.xComputer AssociatesSQL FILE, SCREEN, distributed ports, 6.x options table
11.0 – 11.5CA then BroadcomWORKFILE, larger modules, SQL FILE updates, transitional docs
11.6BroadcomCurrent 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.

11.6 as Documentation Baseline

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.

  • Getting Started — terminology, first compile, runtime overview.
  • Programming / Application Guide — tutorial-style examples by feature area.
  • Language Reference — authoritative syntax for statements and parameters.
  • Installation — SMP/E, library deployment, distributed setup.
  • Release Notes — new features, fixes, migration breaking changes.

SMP/E, FMIDs, and Maintenance Levels

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.

Options Table: 6.x to 11.x EZOPTBL

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.

jcl
1
2
3
4
5
//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

Notable 11.x Feature Themes

Release notes across 11.x highlight themes migration teams should map to test plans:

11.x feature themes and migration impact
ThemeDeveloper impactOperations impact
WORKFILE supportTemporary file grammar in programsDD space, DASD management
SQL FILE automationSimpler SELECT patterns; verify old explicit styleDb2 auth unchanged
Function mode / reserved wordsField renames, SET/EXECUTE collisionsCompile PARM standards updated
GUI Workbench / VS CodeIDE editing, not runtime syntaxDeveloper workstation packaging
REGION=0M guidanceLarger programs compileJCL REGION on compile procs

Distributed vs z/OS Versions

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.

How to Read Release Notes During Upgrade

  1. Identify source FMID and target FMID from operations.
  2. Open Release Difference / Release Notes for the target.
  3. Highlight deprecated syntax, new reserved words, and JCL changes.
  4. Build a spreadsheet mapping program count to error categories from pilot compile.
  5. Schedule options table conversion and proc updates before compile-all week.
  6. Plan parallel-run window with rollback load modules retained.

Explain It Like I'm Five

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.

Exercises

  1. Record your site production Easytrieve FMID and maintenance level.
  2. List three TechDocs books you would open before a 6.x to 11.6 upgrade.
  3. Explain EZOPTBL to a new developer in two sentences.
  4. Find one 11.6 release note item that affects JCL, not source.
  5. Draft a test LPAR promotion checklist including FMID verification.

Quiz

Test Your Knowledge

1. The current Broadcom documentation baseline for Easytrieve is:

  • 11.6
  • 3.1
  • 6.2 only
  • 15.0 beta

2. After Broadcom acquired CA Technologies in 2018, Easytrieve support moved to:

  • Broadcom TechDocs and Broadcom support portals
  • A discontinued product line
  • Open-source GitHub only
  • IBM Redbooks exclusively

3. EZOPTBL DD on z/OS 11.x identifies:

  • The file-based options table
  • The Db2 plan name
  • The CICS region
  • The tape unit

4. SMP/E maintenance for Easytrieve is tracked using:

  • FMIDs and functional PTS/APAR levels
  • Only JCL job names
  • Spreadsheet row numbers
  • DNS host names

5. GUI Workbench and VS Code extension appear in:

  • Modern 11.x release notes as developer tooling
  • Classic 1972 Ribek manuals only
  • COBOL compiler guides
  • JCL procs only

Frequently Asked Questions

What Broadcom Easytrieve versions exist today?

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.

How do I find my installed version?

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.

Do I need separate licenses for z/OS and Windows Plus?

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.

Where are Broadcom release notes?

On Broadcom TechDocs under CA Easytrieve Report Generator — Release Notes and Release Difference documents for 11.6 and prior 11.x maintenance.

Is 11.6 function mode mandatory?

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.

Published
Read time17 min
AuthorMainframeMaster
Reviewed by MainframeMaster teamVerified: 11.6 TechDocs baseline, EZOPTBL, SMP/E versioning conceptsSources: Broadcom TechDocs 11.6 release notes and installation guidesApplies to: Broadcom CA Easytrieve Report Generator version planning and upgrades