Easytrieve Reserved Words Index

Reserved words are the fixed vocabulary Easytrieve owns—IF, JOB, REPORT, BEFORE-LINE, SYSDATE, PAGE-NUMBER, EOF, and hundreds more in Broadcom Symbols and Reserved Words. You cannot name your employee total field IF or your mode flag SET without fighting the compiler. Releases add reserved tokens over decades; 11.6 function mode reserved EXECUTE, HIGH-VALUES, LOGICAL-RECORD, and SYSUSERID among others, breaking innocent legacy DEFINE lines that used those spellings as business names. This index is the hub for section twenty-three: how reserved words differ from ordinary keywords, categories beginners hit daily, links to per-word tutorials with definition purpose version notes and migration guidance, and the reserved words by release page for upgrade planning. The syntax chapter reserved words (syntax) page teaches delimiter and grammar context; start here when you need a catalog, migration scan checklist, or deep dive on BREAK-LEVEL DRAW EXECUTE and related tokens.

Progress0 of 0 lessons

Reserved Versus Non-Reserved Keywords

Every reserved word is a keyword with special meaning, but not every keyword is reserved. FILE introduces a file definition; IF opens a condition. Reserved status adds the rule that field names cannot reuse the spelling. Some non-reserved keywords might legally appear as identifiers in narrow contexts—doing so confuses the next maintainer. Enterprise standards usually ban language tokens as field names entirely. When compile errors cite unexpected keyword or duplicate symbol, search the failing token in Symbols documentation first.

Major Categories

Reserved word families
CategoryExamplesLearn more
Statement keywordsJOB, FILE, DEFINE, IF, END-IF, SORT, PRINTStatements reference
Report PROC hooksREPORT-INPUT, BEFORE-LINE, AFTER-BREAK, ENDPAGEProcedures overview
Screen PROC hooksINITIATION, BEFORE-SCREEN, AFTER-SCREENScreen programming
System fieldsSYSDATE, SYSTIME, PAGE-NUMBER, LINE-COUNTSystem variables section
Control constantsEOF, DUPLICATE, LOW-VALUES, HIGH-VALUESPer-word pages below
11.6 migration tokensEXECUTE, SET, BREAK-LEVEL, SYSUSERIDReserved words by release

Per-Word Tutorial Pages

EASYTRIEVE_PAGES section twenty-three calls for one page per significant reserved word with definition, purpose, version introduced, whether it can be used as a variable, examples, and migration issues. The following tutorials are available in this site section; expand the list as Broadcom documentation and shop migration needs grow.

Reserved word deep dives
WordRoleTutorial
BREAK-LEVELControl break depth in reports/reserved-words/break-level
DRAWReserved in 11.6 migration set/reserved-words/draw
EXECUTEActivity invocation keyword/reserved-words/execute
HIGH-VALUESFigurative upper bound constant/reserved-words/high-values
LOW-VALUESFigurative lower bound constant/reserved-words/low-values
SETReserved assignment-related token in 11.6/reserved-words/set
SYSUSERIDSystem user identifier field/reserved-words/sysuserid

Paths above are relative to /tutorials/easytrieve. Statement keywords like IF and REPORT are covered across the statements reference rather than duplicate pages here—this index routes you to hooks, system symbols, figurative constants, and migration-sensitive names.

Report and Screen PROC Names

Report activities reserve procedure entry point names the product calls automatically. REPORT-INPUT filters records before detail printing. BEFORE-BREAK and AFTER-BREAK surround control level changes. BEFORE-LINE and AFTER-LINE bracket each detail line. ENDPAGE handles page boundaries. TERMINATION runs at report end. Screen activities mirror with INITIATION, BEFORE-SCREEN, AFTER-SCREEN, and TERMINATION. You write PROC bodies with these labels; you do not PERFORM them like user procedures. Naming a user PROC BEFORE-LINE for unrelated batch logic collides with report semantics.

text
1
2
3
4
5
6
7
8
9
10
11
12
REPORT PAY-RPT LINE EMPNO GROSS REPORT-INPUT. PROC IF GROSS LE 0 SKIP END-IF END-PROC TERMINATION. PROC DISPLAY 'COMPLETE' END-PROC

System Field Reserved Words

System fields expose runtime values without DEFINE. SYSDATE and SYSTIME stamp titles and audit logs. PAGE-NUMBER and LINE-COUNT support report pagination. RECORD-COUNT ties to file statistics. FILE-STATUS reflects last I/O result per file. RETURN-CODE communicates job status. LEVEL and BREAK-LEVEL appear during control reports. Reference these names in expressions; never DEFINE duplicates. See system variables section for field-by-field tutorials.

Figurative and Special Constants

LOW-VALUES and HIGH-VALUES represent extreme byte patterns for comparisons and initialization— newly reserved in 11.6 for field naming conflicts. EOF signals end of file in conditions. DUPLICATE tests repeated keys. SPACE and ZERO appear in MOVE and figurative constant pages. Each figurative has dedicated constant tutorials; reserved status means your STATUS-FLAG field cannot be named HIGH-VALUES even if that seemed clever in 1998.

Migration and Scanning

Before enabling 11.6 function mode compile, scan source libraries for tokens in New Reserved Words documentation. Search DEFINE and FILE lines for BREAK-LEVEL, DRAW, EXECUTE, SET, SYSUSERID, and peers. Rename with prefixes and regression-test SORT, REPORT, and SCREEN paths. The reserved words by release page groups tokens by introduction version. Align with enterprise data dictionary tools that flag language collisions automatically.

Naming Rules for Developers

  • Prefix working storage: WS-TOTAL not TOTAL alone when TOTAL is sensitive.
  • Avoid statement verbs as names: USE RUN-MODE not EXECUTE as a field.
  • Qualify ambiguous business names with domain: PAY-SET-CODE not SET.
  • Cross-check new field names against Symbols PDF before merge.
  • Document renamed migration fields in program header comments.

Symbols Table and Delimiters

Symbols documentation also lists punctuation—period, comma, colon, quotes—with reference codes separate from field vocabulary. The R marker indicates reserved status on keywords. Delimiter pages teach RECORD-COUNT and FILEONE:RECORD-COUNT examples; reserved word pages teach semantic meaning of RECORD-COUNT as system symbol. Use both chapters when learning syntax versus semantics.

Explain It Like I'm Five

Reserved words are special name tags the Easytrieve teacher already uses for important jobs—like the word STOP on a red sign. You cannot put your lunch box label STOP on your sandwich bag because everyone would think you mean halt. The teacher adds new special tags when the school upgrades buildings—you must rename your boxes if you accidentally used the new tag words. This index is the poster board listing all special tags and pointing to pages that explain each one.

Exercises

  1. List five categories of reserved words and one example each.
  2. Explain why BEFORE-LINE cannot be a user PROC name for batch utilities.
  3. Name three system fields and one valid use per field.
  4. Outline a migration scan for SET and EXECUTE field renames.
  5. Contrast this index with reserved words (syntax) page purpose.

Quiz

Test Your Knowledge

1. Reserved words in Easytrieve:

  • Cannot be used as user field names
  • Are optional comments
  • Replace DD names
  • Only appear in JCL

2. BEFORE-LINE is reserved because:

  • It names a report procedure hook
  • It is a SORT key
  • It is a tape label
  • It opens files

3. SYSDATE is:

  • System date field you reference not DEFINE
  • A JCL keyword
  • A SORT option
  • A DD name

4. 11.6 migration broke programs that used SET as:

  • A user field name
  • A comment
  • A DD parameter
  • A sequence number

5. The syntax chapter reserved words page differs from this index because:

  • This index links per-word tutorials and migration pages
  • They cover COBOL
  • Only JCL
  • There is no difference
Published
Read time17 min
AuthorMainframeMaster
Reviewed by MainframeMaster teamVerified: Broadcom Easytrieve 11.6 Symbols and Reserved Words indexSources: Broadcom Easytrieve 11.6 Symbols and Reserved Words, New Reserved WordsApplies to: Easytrieve reserved words catalog