Easytrieve z/OS Setup

Configuration vs Installation

Installation puts product code on disk. Configuration tells Easytrieve how your site behaves: which options table to read, whether migrated 6.4 programs run in compatibility mode, and which global report defaults apply. Broadcom separates these into CBAAJCL jobs such as JOB06OP1 (create EZTINI / options table) and JOB06OP2 (set global options).

Options Table and EZTINI

On 11.x z/OS, the options table is a file—not the old 6.x load-module-only pattern. The EZTINI module in CBAALOAD holds the default options table dataset name. Effects:

• If EZTINI exists and JCL omits EZOPTBL, compiler and runtime use the INI default DSN.
• If JCL specifies EZOPTBL, it overrides the INI default for that step.
• If both are missing at execute time and EZTINI was not built, the program cannot run.

Creating EZTINI via JOB06OP1 is a Broadcom best practice because it simplifies standard developer JCL—fewer DD cards on every compile proc.

Key DD Names in z/OS Setup

Compatibility Mode for 6.4 Migration

Broadcom recommends running legacy 6.4 programs first in compatibility mode when moving to 11.6. Set PARM COMPAT (or options table flags documented in migration guides) so behavior matches expectations from the old release. Old load modules may also run in compatibility mode when executed under 11.6 runtime until recompiled in new-function mode.

After compatibility testing passes, migrate application groups to new-function mode incrementally—few programs at a time—with regression comparison of report output.

Global Options via JOB06OP2

Global options in the options table standardize:

• Default listing width and spacing behaviors.
• Site-wide compatibility and diagnostic levels.
• Standard file handling assumptions reducing per-program PARM lines.

Program-level PARM and REPORT statements can override globals when needed—override is intentional escape hatch, not failure of global config.

Sample Configuration JCL Pattern

After install, a minimal compile test (from Broadcom docs, names changed to placeholders):

1
2
3
4
5
6
7
8
9
//EZTTEST  EXEC PGM=EZTPA00,REGION=4M
//STEPLIB  DD DISP=SHR,DSN=your.easytrieve.r116.CBAALOAD
//EZOPTBL  DD DISP=SHR,DSN=your.easytrieve.r116.EZOPTBL
//EZTVFM   DD UNIT=SYSDA,SPACE=(CYL,(3,1))
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
PARM COMPILE
FILE TESTFILE ...
/*

REGION=4M gives the step enough virtual storage for compiler tables. EZTVFM SPACE=(CYL,(3,1)) allocates cylinder space for virtual files—adjust per site storage standards. PARM COMPILE requests compile-only; other PARM values control link, syntax check, and compatibility.

STEPLIB Concatenation Rules

When Easytrieve programs call Db2, IMS, or external subroutines, STEPLIB concatenates multiple libraries. Order matters: Broadcom documents that under DB2 or DLI batch, IMS RESLIB may need to appear before the DB2 library. Your shop proc encodes approved order; do not rearrange without systems programming review.

Security and Dataset Profiles

RACF (or equivalent) must grant developers READ on CBAALOAD, UPDATE on application load libraries if they compile, and appropriate access to source PDS members. EZOPTBL is often restricted to administrators because global option changes affect all programs using that table.

Explain It Like I'm Five

z/OS setup is choosing the default settings on the printing shop machines: paper size, margin rules, and which rulebook to follow. EZTINI remembers the main rulebook location. EZOPTBL lets one job use a different rulebook if needed. Compatibility mode is using old rules until you trust the new machines print the same way.

Exercises

1. Document your site EZOPTBL dataset name (or ask your team).
2. Explain when EZOPTBL overrides EZTINI.
3. List three DD names required for a compile-and-go test.
4. Describe compatibility mode in one paragraph for a new hire.
5. Find CBAAJCL on your system and locate JOB06OP1 purpose in comments.