Easytrieve has decades of production use under names many veterans still say aloud: Classic, Plus, CA Easytrieve, and today Broadcom Easytrieve Report Generator. Programs written in the 1990s may compile unchanged on 11.6—or fail on the first new reserved word collision. Migration is not a single weekend project; it is a portfolio discipline combining inventory, release-note review, compile-fix cycles, parallel output comparison, and controlled load module promotion. This overview orients beginners and maintainers on the journey, points to detailed child topics, and sets expectations about what changes between eras versus what stays familiar in FILE, JOB, and REPORT thinking.
Early Classic environments introduced the Library and Activity structure many developers still recognize. Easytrieve Plus expanded statements, online integration, and macro libraries common in 6.x documentation PDFs. Broadcom Report Generator 11.x aligns with modern z/OS features—WORKFILE, expanded modules requiring REGION=0M, updated Symbols and Reserved Words appendices, and TechDocs online Language Reference. Your shop may run one label while archives reference another; migration planning starts by recording which compiler version compiles tonight's production jobs.
| Era | Typical sources | Watch for |
|---|---|---|
| Classic / early CA | Older syntax, minimal online features | Obsolete verbs, pre-Plus FILE options |
| Easytrieve Plus 6.x | Application Reference PDFs, $functions | Statement name drift vs 11.6 Language Reference |
| Broadcom Report Generator 11.6 | TechDocs, release notes, Symbols appendix | New reserved words, WORKFILE, module size |
Vendor support windows, z/OS upgrades, security requirements, and DASD or tape infrastructure changes force compiler upgrades even when business logic is stable. Regulatory audits ask for supported software levels. New hires arrive trained on current TechDocs while your source comments reference 1987 run books. Migration converts that risk into a planned program with test evidence instead of an emergency compile failure on a holiday weekend.
A mass compile sweep surfaces most static incompatibilities quickly. Sort listing diagnostics by frequency: one macro definition fix may clear dozens of programs. Keep compile listings with error counts for audit. Programs that compile clean may still behave differently at runtime—reserved word fixes are necessary but not sufficient for sign-off.
123456PARM DEBUG(PMAP DMAP XREF) LIST FILE * Pilot compile PARM — remove verbose DEBUG before production FILE PAYROLL FB(500 25000) %PAYROLL JOB INPUT PAYROLL PRINT PAYRPT
Each release can add reserved identifiers that collide with legacy field names—especially short names copied from COBOL copybooks. The migration-new-reserved-words page catalogs patterns; your compile listing flags conflicts with recognizable diagnostics. Renaming fields in macros propagates fixes across programs—another reason central FILE macros beat duplicated definitions.
Migration is not source-only. JCL procs may need larger REGION, new DD for WORKFILE outputs, updated SORT product parameters, or changed SYSPRINT routing. Options table values (VFMSPAC, ABEXIT defaults, BUFNO) may differ between old and new installations. Run one known job end-to-end in test before portfolio-wide compile sweeps consume the team's attention.
Financial and payroll shops often diff report files—record counts, hash totals, sample account balances—between old and new compiles of the same source on identical input. Automate compare with standard mainframe utilities or downstream scripts. Document acceptable differences when release notes specify formatting changes (dates, rounding, page headers).
Update internal wikis with target PARM profiles, renamed fields, and proc changes. Train maintainers on TechDocs navigation if they relied on Plus PDFs. Link child migration pages from your team portal so Classic-specific quirks are not lost when senior staff retire.
Keep previous load modules and compiler libraries available until soak completes. Change control should define rollback triggers—compare failure rate, abend spike, or missed SLA—and how schedulers revert STEPLIB concatenations. Migration projects fail operationally when rollback is undefined.
Migration is moving your lemonade stand to a new kitchen. Most recipes still work, but the new stove has different buttons (reserved words) and bigger pots (REGION). You make one test pitcher, compare taste with the old kitchen, then move the whole business only when parents agree it tastes the same.
1. The first document set to read when migrating Easytrieve versions is usually:
2. New reserved words in a release most often break programs when:
3. Promotion to production after migration testing should use:
4. Regression testing after migration should include:
5. CA Easytrieve Plus manuals versus Broadcom 11.6 Language Reference:
Migration is moving programs, JCL, macros, and operational procedures from an older Easytrieve environment (Classic, Plus, or an earlier Broadcom release) to a newer compiler and runtime on z/OS or other supported platforms. It includes source changes, retesting, and promotion of load modules.
Rarely. Most batch reports compile after reserved word fixes, PARM updates, and occasional statement changes documented in release notes. A minority of programs using deprecated features need redesign—plan discovery via compile listings and migration checklists.
Proportional to portfolio size and criticality. Start with a pilot of high-value, moderate-complexity jobs. Automate compile-all jobs where possible. Full parallel running (old and new output compare) is common for financial applications before cutover.
Developers fix source and unit tests; operations upgrade procs, STEPLIB, and options tables; change control tracks promote dates. DBAs and storage teams join when VSAM or SORT changes appear.
Use child pages in this migration section—Classic, Plus, Broadcom versions, version differences, deprecated syntax, new reserved words, and compatibility—for deep dives. Always confirm against your installed maintenance level.