Version differences are where migration projects succeed or fail in subtle ways. Two compile listings can both show zero errors while payroll totals diverge by pennies because rounding or mask editing changed between CA Plus 6.x and Broadcom 11.6. A FILE statement copied from a 1998 Application Guide may use an ACCESS spelling replaced in modern Language Reference. DISPLAY NEWPAGE semantics that veterans memorized may now align with DISPLAY TITLE per release notes. Function mode adds reserved words that turn innocent field names like SET or EXECUTE into hard compile errors. This page compares Classic, Plus 6.x, and 11.6 across options, syntax, runtime, and testing—giving beginners a structured checklist instead of tribal knowledge scattered across PDF shelves and retired mentors.
Compare versions across four layers: compile-time syntax, site options/PARM, runtime JCL environment, and output semantics. Teams that only fix compile errors miss the fourth layer until finance opens a ticket. Build test packs that exercise all four: compile listing archive, options table dump, proc STEPLIB capture, and diffed output files.
| Layer | Examples | How to verify |
|---|---|---|
| Syntax | Statement spellings, deprecated FILE options | Pilot compile on target FMID |
| Options/PARM | EZOPTBL, DEBUG, function vs compatibility mode | Compare options file and compile PARM procs |
| Runtime JCL | REGION, WORKFILE DDs, SORT product | End-to-end job with production-like volumes |
| Output semantics | Totals, masks, page breaks, dates | Parallel compare on frozen input files |
Classic programs emphasize batch FILE/JOB/REPORT with limited online and SQL features. Plus adds SQL FILE, SCREEN activities, extended $functions, and PROGRAM parameters. Classic source usually upgrades forward; Plus-only statements do not downgrade to Classic compilers. Migration from Classic to 11.6 is effectively Plus migration with possible older idioms (unlabeled flow, terse names).
The options table migration is operational but changes developer-visible behavior: buffer sizes, abend handling, sort delegation, listing defaults. Broadcom's conversion utility maps many 6.x keywords; some become unsupported with warnings in the utility report. Compile PARM profiles also evolve—DEBUG suboptions, LIST variants, and function mode switches appear in 11.6 standards. Standardize PARM on test before mass compile; ad hoc developer PARM hides version assumptions.
1236.x mindset: site table embedded in installation libraries 11.6 mindset: EZOPTBL DD -> SITE.EZT.OPTBL.FILE PARM: review function mode vs compatibility in release notes
Release difference notes document DISPLAY NEWPAGE alignment with DISPLAY TITLE in 11.x—reports that relied on subtle page-break side effects may reflow. REPORT masks and edit patterns can change width or rounding when picture clauses map differently to internal formats. Test printed output visually and numerically; PDF compare tools help for wide reports. Document acceptable formatting deltas when business owners agree cosmetic changes are OK.
11.x simplified some SQL FILE declaration patterns while retaining older explicit SELECT styles. Migration teams must classify SQL programs separately from flat-file batch: row counts, NULL handling, join order, and cursor behavior may differ. Coordinate with DBAs for plan stability; Easytrieve syntax change does not replace Db2 statistics or bind maintenance.
WORKFILE support in 11.x enables temporary dataset grammar that 6.x programs may emulate with manual SORT or intermediate files. Converting to WORKFILE can reduce I/O but requires JCL space planning and new failure modes if DD names collide. Compare elapsed time and DASD use in test before rewriting stable jobs for marginal gains.
11.6 function mode is a sharp version boundary for identifiers. Tokens such as SET, EXECUTE, SYSUSERID, BREAK-LEVEL, DRAW, HIGH-VALUES, and LOW-VALUES break programs when used as field names. Compatibility mode may compile some legacy sources while you rename fields; function mode enables newer grammar. Plan a two-phase cutover: rename sweep, then enable function mode site-wide. See migration-new-reserved-words and reserved-words-by-release for token lists.
| Topic | 6.x typical | 11.6 typical |
|---|---|---|
| Options table | Legacy install format | EZOPTBL file |
| Compile REGION | Smaller defaults sometimes | REGION=0M common on compile procs |
| Field named EXECUTE | Often allowed | Reserved in function mode |
| IDE tooling | ISPF, PDF manuals | VS Code extension, GUI Workbench |
| Release docs | CA Advantage PDFs | Broadcom TechDocs web library |
Larger 11.x compiler and runtime modules drove REGION=0M guidance on compile and go procs. Jobs that abended with 878 or storage errors after upgrade may need JCL REGION and WORKMEM adjustments unrelated to source logic. Capture CEEDUMP and abend codes during pilot runs; involve systems programming early when storage errors cluster on compile steps.
Version differences are like when your school gets new rulers that measure the same but have different colored lines. Most drawings look the same, but a few lines might start in slightly different places (page breaks) or round crayon lengths differently (totals). Before turning in homework, compare your old and new ruler on the same picture.
1. DISPLAY NEWPAGE behavior in 11.x relative to 6.x often aligns with:
2. The largest operational difference between CA 6.x and 11.x on z/OS is frequently:
3. 11.6 function mode primarily affects:
4. When Plus 6.x manuals disagree with 11.6 Language Reference, you should trust:
5. Runtime differences after a clean compile are caught by:
Differences span options table format, PARM keywords, reserved words, SQL FILE syntax, DISPLAY/REPORT formatting, WORKFILE support, module size/REGION needs, and online SCREEN hooks. Release Difference documents enumerate breaking changes between specific FMIDs.
Often yes after fixes for reserved words and deprecated syntax. Classic alone is not a compiler switch on modern Broadcom installs—you compile as Plus/Report Generator with migration adjustments.
Rounding rules, edited numeric masks, SORT key stability, implicit conversions, or changed default options can alter accumulators. Parallel-run compares on known input files detect these before production cutover.
Maintain an internal migration wiki listing renamed fields, proc changes, acceptable output diffs, and PARM profiles per environment. Link Broadcom PTS notes when behavior changes mid-year.
Most core statements remain recognizable, but some options were renamed, deprecated, or restricted. Always verify spelling and parameters in 11.6 Language Reference rather than assuming 6.x PDFs apply.