How is this different from the statements reference index?

This cheat sheet compresses syntax patterns for quick lookup during coding. Per-statement tutorial pages explain semantics, errors, and examples in depth.

Are all statements on every Easytrieve product?

SCREEN and some online statements require appropriate product and environment. Batch FILE JOB REPORT are universal core.

Where do PARM and STOP go?

PARM typically starts Library; STOP ends Activity. Site standards may vary—follow local coding standard.

Can statements appear in any order?

Library declarations must precede use; REPORT before PRINT reference. Activity order follows program logic—verify compile errors for forward references.

Easytrieve Statement Cheat Sheet - FILE, JOB, IF, REPORT Quick Reference

Easytrieve Statement Cheat Sheet

Statements are the verbs of Easytrieve—FILE describes data, JOB reads it, IF filters it, REPORT and PRINT shape output. This cheat sheet groups statements by purpose with minimal syntax patterns so you can find the right keyword during development without opening a manual. Placement column reminds whether each statement lives in Library or Activity. For semantics, error messages, and extended examples, follow links to individual statement tutorials. Statement set reflects Broadcom Report Generator 11.6 batch and report focus; online SCREEN statements included for completeness.

Definition Statements (Library)

Definition statements
Statement	Syntax sketch	Purpose
PARM	PARM options...	Compile/runtime options—LIST, DEBUG, COMPAT
FILE	FILE name org... / fields	Declare file and record layout
DEFINE	DEFINE name type...	Working storage fields
REPORT	REPORT name options / TITLE LINE	Report layout definition
MACRO	MACRO name ... %MACRO	Macro definition (compile-time)

text

1
2
3
4
5
FILE PAYROLL FB(200 20000)
  EMP-ID    1  5  N
DEFINE WS-TOTAL W 9 P 2
REPORT PAY-RPT LINESIZE 132
  LINE 01 EMP-ID WS-TOTAL

I/O and Activity Driver Statements

I/O statements
Statement	Syntax sketch	Purpose
JOB INPUT	JOB INPUT file	Batch read loop on primary file
GET	GET file	Read next record (secondary/manual)
PUT	PUT file	Write record to output file
OPEN	OPEN file	Open file explicitly when required
CLOSE	CLOSE file	Close file explicitly
READ	READ file	Read variant per release/access method

Control Flow Statements

Control flow
Statement	Syntax sketch	Purpose
IF / END-IF	IF cond ... END-IF	Conditional execution
ELSE	ELSE ...	Alternative branch
DO / END-DO	DO WHILE cond	Loop while true
PERFORM	PERFORM proc	Call PROC
GOTO	GOTO label	Branch to label—use sparingly
EXIT	EXIT	Leave PROC or loop
STOP	STOP	End program
SELECT / CASE	SELECT / WHEN	Multi-way branch per release

Data Movement and Calculation

Data statements
Statement	Purpose
MOVE	Copy between fields
ADD / SUBTRACT	Accumulate numeric fields
COMPUTE / assignment	Expression evaluation where supported
VALUE on DEFINE	Initialize working storage

Report Statements

Report activity and layout
Statement	Purpose
PRINT	Emit lines from named REPORT layout
TITLE	Page header lines inside REPORT
LINE	Detail or heading row columns
FOOTING	Page footer lines
SKIP	Vertical spacing lines
CONTROL	Field attribute for control breaks
BEFORE-LINE / AFTER-LINE	Report event PROC hooks
BEFORE-BREAK / AFTER-BREAK	Control break PROC hooks

Sort and Environment

Sort and utility
Statement	Purpose
SORT	Order records by keys ascending/descending
SORT control fields	DUPLICATES, DYNALLOC per syntax
DISPLAY	Debug output to listing or log
CALL	Invoke external program
LOOKUP	Table search patterns per release

Screen Statements (Online)

Screen family
Statement	Purpose
SCREEN	Online activity block
BEFORE-SCREEN	Pre-display PROC
AFTER-SCREEN	Post-input PROC
INITIATION / TERMINATION	SCREEN start/end hooks

Minimal Batch Skeleton

text

1
2
3
4
5
6
7
8
PARM LIST FILE
FILE INFILE ...
REPORT RPT1 ...
JOB INPUT INFILE
  IF condition
     PRINT RPT1
  END-IF
STOP

Statement Selection Guide

Need record layout? → FILE (+ macro if shared).
Need scratch field? → DEFINE.
Need read all records batch? → JOB INPUT.
Need filter? → IF.
Need printed columns? → REPORT + PRINT.
Need subtotals? → CONTROL on REPORT field + break PROCs.
Need order by key? → SORT.
Need reuse logic? → PROC + PERFORM.

Common Statement Mistakes

PRINT before REPORT defined.
JOB INPUT without matching FILE and DD.
Missing END-IF, END-PROC, END-DO terminators.
REPORT name typo versus PRINT name.
GET without EOF handling.

Explain It Like I'm Five

Statements are action cards. FILE card describes the box of records. JOB card says read every record. IF card says only do the next cards when a rule matches. REPORT card draws the paper template; PRINT card actually puts words on paper for this record. The cheat sheet is all action cards sorted by type so you pick the right card fast.

Exercises

Classify ten statements into Library versus Activity.
Write skeleton for read-all print-one-report program.
Add SORT and CONTROL to skeleton on paper—where do they go?
Match I/O statements to scenario: secondary file read.
Find one screen-only statement and explain batch alternative.

Quiz

Test Your Knowledge

1. FILE belongs in:

Library section
JCL only
SYSPRINT
Load module

2. JOB INPUT primarily:

Drives batch read loop on named file
Defines report titles only
Links COBOL
Compiles macros

3. REPORT versus PRINT:

REPORT defines layout; PRINT selects layout during activity
Same statement
PRINT defines FILE
REPORT opens JCL

4. PROC END-PROC wraps:

Named reusable procedure code
JCL procedures only
DD statements
Sort cards

5. SORT statement:

Orders records by keys
Opens SYSPRINT
Defines SCREEN
Replaces FILE