Easytrieve Compiler Options Overview

Two Layers: Site Table and PARM

At install, Broadcom defines compiler and execution defaults in the options table. Each compiled program inherits those values unless PARM specifies overrides. PARM must be the first source statement when used. Operations owns table changes; developers own program PARM for exceptions. Document both in runbooks when troubleshooting different behavior between test and production LPARs.

PARM Major Parameter Groups

1
2
3
4
5
PARM ABEXIT(NO) +
     DEBUG(PMAP, DMAP, FLDCHK, STATE, XREF(LONG)) +
     FLOWSIZ(20) +
     LIST(FILE, PARM) +
     SORT(MSG(ALL))

ABEXIT controls abend dump behavior—SNAP for development, NO for production per best practices. DEBUG selects maps and checks during compile. LIST(FILE,PARM) prints file definitions and PARM summary in listing. SORT(MSG(ALL)) increases sort message detail during test runs. Each subparameter has NO-prefix negation forms documented on PARM statement reference.

Compiler Option Categories

Listing Control Statements

Beyond PARM DEBUG, source statements LIST ON, LIST OFF, LIST MACROS, LIST NOMACROS, NEWPAGE, SKIP n, PUSH, and POP format the physical listing. LIST OFF suppresses following source lines from listing—useful for large generated tables not worth printing. PUSH saves settings before macro expansion; POP restores after—keeps macro debug readable without changing permanent listing preferences.

Syntax and Migration Options

STRICTQU controls unqualified field references: N silent qualify, W warn which file was used, E error EZTC0644E. NEWFUNC enables 11.6 function mode semantics including new reserved words. FLDCHK validates unavailable field references to reduce runtime program checks. Together they define how painful migration from 6.4 will be—many sites enable NEWFUNC in test LPAR first.

Child Pages on This Site

• Optimization options — CPU, storage release, division rounding, block size defaults.
• Debugging options — DEBUG subparameters, ABEXIT, FLOW, STATE, SORTMSG.
• Listing options — DMAP PMAP CLIST XREF LISTUC LISTPRM.
• Cross-reference options — XREF LONG versus SHORT symbol tables.
• Diagnostic options — WARNCC WARNSYM ERORSYM STRICTQU message behavior.

Development Versus Production Profile

Broadcom recommends link-edit production execution and compile-and-go for quick tests only. Development profile often includes LIST ON MACROS, DEBUG(PMAP DMAP STATE XREF(LONG)), SORT(MSG(ALL)), and ABEXIT appropriate for dumps. Production profile strips DEBUG maps, sets ABEXIT NO, avoids FLOW trace, and uses site defaults for LISTFIL only when statistics needed. Mismatch between profiles explains works in test fails in prod when options differ—not logic change.

Common Compiler Options Mistakes

• Coding PARM after FILE statement—must be first.
• Leaving DEBUG DMAP in production nightly jobs—CPU cost.
• Assuming JCL overrides PARM without reading proc.
• Ignoring NEWFUNC in test while production enables function mode.
• LIST OFF hiding errors in macro sections during debug.

Explain It Like I'm Five

Compiler options are the rules for how the robot reads your homework. The school (options table) sets default rules for everyone. You can put a note at the top of your paper (PARM) asking for extra help—show my math steps (DEBUG maps) or check my spelling harder (STRICTQU). For the real test (production), use the normal rules so the robot works faster and does not print every pencil stroke.

Exercises

1. Write a development PARM line with DEBUG and LIST options.
2. List three categories from the options table.
3. Explain PARM versus EZOPTBL precedence.
4. Describe when LIST OFF is appropriate.
5. Name two syntax options that affect migration from 6.4.