Easytrieve Runtime Errors Index

Compile Success Versus Runtime Failure

A clean compile proves source syntax and static semantics only. Runtime exercises real datasets, concurrent job schedules, empty GDGs, keys not found on VSAM READ, and numeric fields that contain spaces or LOW-VALUES from upstream extracts. Move mode versus locate mode file processing in 11.6 changes invalid reference symptoms—see migration notes when porting 6.4 programs. Always verify the run used the load module you just linked.

Runtime Message and Abend Anatomy

1
2
3
4
EZT nnnn message text on SYSPRINT
FILE-STATUS = 23  (VSAM not found example — verify against your FILE doc)
CEE3204S S0C7 Data exception during ADD
Last statement executed: 000412 per STATE listing correlation

Prefixes vary by release and environment. Correlate message text with abend code in job log. When STATE was enabled at compile via PARM DEBUG STATE, abend summaries reference statement numbers matching the compile listing—essential for macro-heavy programs.

File and I/O Error Family

System-defined FILE-STATUS, RECORD-COUNT, RECORD-LENGTH, and PATH-ID fields document runtime file state. Test FINISH procedures that DISPLAY status when any GET returns error—operations need plain language, not only abend codes.

Arithmetic and Data Exception Family

S0C7 data exception often traces to ADD or SUB on packed fields with invalid nibbles— spaces in zoned fields, HIGH-VALUES in amounts, or divide by zero when divisor never validated. Guard with IF NUMERIC and IF field NE ZERO before math. SQL nullable fields need indicator checks before arithmetic. FLDCHK compile option catches some invalid references early but does not replace data validation.

1
2
3
4
5
6
IF DIVISOR NUMERIC AND DIVISOR NE ZERO
   QUOTIENT = DIVIDEND / DIVISOR
ELSE
   MOVE ZERO TO QUOTIENT
   MOVE 'Y' TO ERR-FLAG
END-IF

SORT and Utility Runtime Failures

SORT activity invokes system sort. Wrong key length, unsupported format, insufficient work space, or missing SORTWK DD produce sort messages in SYSPRINT wrapped in Easytrieve step output. SORT(MSG(ALL)) on PARM surfaces detail during test. Keys must match defined file fields; binary keys need correct length in SORT statement. External presort jobs that omit sync with Easytrieve FILE layout cause silent wrong order—not always an error message.

Application RETURN-CODE Versus Abend

MOVE 8 TO RETURN-CODE in FINISH exits cleanly with RC 8—batch scheduler may still alert. Distinguish from S0C4 protection exception. Document intentional RETURN-CODE values in runbooks: 0 success, 4 warning, 8 business validation failure, 12 severe. DISPLAY explanatory text before STOP so logs show reason without dump reading.

Online and CICS Runtime Considerations

SCREEN activities may fail on map errors, missing terminal definitions, or EXECUTE nesting mistakes recursion cannot detect. CICS programs must remain conversational when CALL chains require it. Transaction dumps differ from batch CEEDUMP. AFTER-SCREEN validation should set message fields instead of abending when operator correctable.

Debugging Aids for Runtime

Triage Workflow

1. Identify failing step: compile, link, or run—this index is for run.
2. Read job log abend code and SYSPRINT last messages.
3. If S0C7, dump or listing STATE points to statement; inspect fields in DMAP.
4. If file status, log DD name, DSN, DISP, and key values (non-PII in tickets).
5. Reproduce with small test file; add DISPLAY guards.
6. Compare load module date to source; rule out stale bind.
7. Document fix: data cleanse, validation IF, JCL DD, or layout correction.

Common Runtime Mistakes

• Assuming compile clean means data clean.
• Leaving ABEXIT SNAP in production JCL.
• Ignoring FILE-STATUS after GET READ.
• No FINISH DISPLAY when RETURN-CODE non-zero.
• Chasing SORT without verifying key field offsets.
• Editing copybook without recompile and relink.

Explain It Like I'm Five

Runtime errors happen when the robot tries to do the homework on real papers, not practice sheets. Maybe a page is torn (bad data), the folder is empty (EOF), or the robot tries to divide cookies among zero friends (divide by zero). The compile step only checked spelling; runtime checks whether the world outside makes sense. The job log is the robot's cry for help—read what it says before opening every toolbox.

Exercises

1. Write FINISH DISPLAY for FILE-STATUS and RETURN-CODE.
2. List three differences between S0C7 and RETURN-CODE 8.
3. Describe when SORT(MSG(ALL)) helps versus hurts.
4. Plan DISPLAY trace points for one JOB INPUT loop.
5. Explain why wrong salary on report may not abend.