Easytrieve ISPF Integration

Source Libraries and Member Naming

Easytrieve source lives in partitioned datasets such as DEV.EZT.SOURCE with members DAYRPT, MTHSUM, or GLEXT. Each member is one program. Naming conventions often encode application (GL), frequency (D=daily, M=monthly), and sequence. ISPF edit shows sequence numbers in columns 1–6 optionally; Easytrieve may ignore or use them per options—check site standards.

ISPF Workflow for Developers

1. ISPF 3.4 — locate source PDS and listing PDS datasets.
2. ISPF 2 — edit member; use FIND, COPY, MODEL for templates.
3. Save — validate columns and continuation rules per language reference.
4. Submit — invoke EZTCOMP or EZTGO proc via submit line or shop panel.
5. SDSF — review job output, SYSPRINT listing, return code.
6. Fix errors — return to ISPF edit using compiler line numbers from listing.

Shop Procs and Panels

Mature installations wrap Easytrieve in ISPF dialogs: enter member name, environment (DEV/TST/PROD), and optional PARM overrides; the dialog generates JCL from a skeleton. This reduces JCL errors and enforces STEPLIB and EZOPTBL standards. Ask your team for the panel name—often something like EZT001 or a generic compile panel shared with COBOL.

Listing and Debug Dataset Layout

Separate PDS for listings (DEV.EZT.LISTING) helps developers compare compiles without scrolling SDSF. Some shops auto-catalog listing members named by job name and date. ISPF browse or edit lets you search compiler messages (EZT####) quickly.

Modern Tooling Alongside ISPF

Broadcom 11.6 documents GUI Workbench and Visual Studio Code extension support. Hybrid workflow: edit in VS Code with syntax highlighting, push to Git, pipeline submits JCL to mainframe, developer views results in SDSF or email notification. ISPF remains fallback for quick fixes on the datacenter floor.

PF Keys and Productivity

• PF3 end — return from edit.
• SAVE — store changes before submit.
• SUBMIT — on command line with JCL in another screen or auto-generated.
• MODEL — insert standard FILE/REPORT skeleton from a model member.

Security in ISPF Context

RACF protects who can edit production source (usually read-only for most developers). Test libraries allow UPDATE; promotion to production may require change control tool (Endevor, Changeman) rather than direct ISPF save—Easytrieve source follows same SDLC as COBOL.

Explain It Like I'm Five

ISPF is the text editor on the mainframe computer. Easytrieve homework is saved in named folders (PDS). You open the file, write your report program, press a shop button to send it to the printer machine (batch job), and then read the result paper (SYSPRINT).

Exercises

1. Navigate to your dev Easytrieve source PDS with 3.4.
2. Identify your shop compile proc name and parameters.
3. Trace path from ISPF save to SDSF output viewing.
4. List advantages of VS Code + Git vs ISPF-only workflow.
5. Find one compiler message in a sample listing and locate line in ISPF edit.