Easytrieve Reserved Words by Release

Why Releases Add Reserved Words

Language evolution introduces SCREEN online activities, extended REPORT control, SQL integration, and new system fields. Each feature needs keywords the parser recognizes unambiguously. If SET remained available as a field name while also meaning assignment configuration, the compiler could not decide whether SET referred to data or grammar. Reserving the token pushes shops to rename fields—a one-time migration cost for long-term parser clarity. Classic programs that never upgrade compilers avoid the pain until the operations mandate forces the jump.

Classic and Plus Baseline

Early Easytrieve reserved core statement vocabulary: JOB, FILE, DEFINE, IF, REPORT, SORT, PERFORM, PROC, END-PROC, and report hooks BEFORE-LINE REPORT-INPUT TERMINATION. System fields SYSDATE SYSTIME and pagination symbols PAGE-NUMBER LINE-COUNT were reserved before many shops digitized standards. Plus releases added SCREEN hooks INITIATION BEFORE-SCREEN AFTER-SCREEN and expanded file ACCESS grammar. Migrating from Classic to Plus often required REPORT syntax changes before reserved word collisions became the dominant issue.

11.6 Function Mode Migration Set

Broadcom New Reserved Words documentation for 11.6 function mode is the critical upgrade list. Tokens below broke programs when used as user field names. Verify exact list on your PDF—site tutorials mirror common entries; your installation letter is authoritative.

Screen and Report Additions

INITIATION and TERMINATION reserved as screen and report procedure names block reuse for unrelated batch PROC labels. NOTITLE reserved status affects fields that mimicked report title switches. GRAPH and DRAW appear in migration sets tied to extended output features—confirm on your Symbols table if compile errors reference them. END-REPEAT relates to repeated report or macro constructs in newer grammar.

Migration Scan Playbook

1. Export New Reserved Words PDF for target 11.6 or Plus level.
2. Grep production libraries for each token on DEFINE and FILE lines.
3. Flag comments and strings separately—only identifiers matter.
4. Assign rename mapping WS- prefix convention in spreadsheet.
5. Compile one program pilot in function mode; collect error list.
6. Batch rename with change control; regression-test JOB SORT REPORT SCREEN.
7. Update copybooks and enterprise dictionary before mass compile.

1
2
3
4
5
* Before migration — compile error expected in 11.6 function mode
DEFINE SET 1 A 1
 
* After rename
DEFINE WS-SET-IND 1 A 1

Compile Error Patterns

Duplicate symbol or field name conflicts with reserved word messages point directly at rename targets. Unexpected keyword in DEFINE section means the compiler parsed your field name as grammar—classic SET and EXECUTE symptoms. Less obvious cases: LOGICAL-RECORD in copybook shared across fifty programs requires coordinated copybook version bump. Partial migration leaves some members compiling in old mode while others fail in CI—standardize compile options per library.

Compatibility Mode Strategy

Shops schedule dual-track compiles: maintain production on prior compiler while a migration branch renames fields and enables function mode in test LPAR. Compare listing and SYSPRINT output record counts and totals before cutover. Do not assume behavioral equivalence without parallel run—reserved word fixes are syntax-level but refactors may expose latent logic bugs when field names change in macro expansions or INCLUDE members.

Per-Release Documentation Habits

Archive Symbols PDF per compiler SMP level in version control beside source. When audit asks which reserved words applied in 2019, you need the PDF from that SMP—not today's web download. Program headers should cite compile option mode and SMP level after migration for forensic clarity.

Per-Word Tutorials on This Site

Section twenty-three per-word pages drill into individual tokens: definition, purpose, version introduced, variable naming prohibition, examples, and migration fixes. Start with tokens your scan hits most often—SET and EXECUTE appear frequently in legacy naming because English words felt natural. BREAK-LEVEL and SYSUSERID appear in report-heavy and security-aware applications. HIGH-VALUES and LOW-VALUES collide when programmers named threshold fields after figurative constants they mimicked in MOVE statements.

Beyond 11.6

Future Broadcom maintenance may reserve additional words. Subscribe to fix lists and re-run scan when applying SMP maintenance. Automated dictionary tools that compare DEFINE against live Symbols extract reduce surprise. This page will accumulate release notes as new site tutorials publish— treat EASYTRIEVE_PAGES checklist as the master backlog for per-word coverage gaps.

Common Migration Mistakes

• Renaming only main program, not copybooks and PROC includes.
• Enabling function mode before scan completes.
• Assuming literals in TITLE need rename—usually identifiers only.
• Ignoring macro-generated DEFINE lines in scan scope.
• Partial compile option mix across parallel development teams.
• Skipping regression on SCREEN paths after batch-only testing.

Explain It Like I'm Five

Every school year the teacher may add new rule words you cannot use as nicknames for your toys. Last year SET was a fine nickname for your red block; this year SET is a teacher command word so you rename the block SETTY. This page is the list of new command words by school year and how to relabel your toys before the teacher checks your desk in 11.6 class.

Exercises

1. Write a seven-step migration scan outline for SET and EXECUTE.
2. Map three 11.6 tokens to suggested WS- rename patterns.
3. Explain why INITIATION is reserved for screen activities.
4. Describe a pilot compile strategy before mass rename.
5. List two compile error messages that imply reserved word collision.