Easytrieve EXECUTE Reserved Word

Definition and Purpose

The EXECUTE statement is an activity transfer mechanism. Where PERFORM runs a procedure within the same activity, EXECUTE runs a whole JOB, SORT, or SCREEN activity declared elsewhere in the source module. Purpose: structure large systems as multiple activities without duplicating Library definitions, route processing based on parms or screen input, and support online-to-batch handoff. The PROGRAM statement in 11.6 enhances this model by letting one PROGRAM super-activity orchestrate several JOB activities under one LE run unit when ENVIRONMENT(COBOL) is specified.

Statement Format

1
EXECUTE {job-name | sort-name | screen-name}

The operand is the NAME on a JOB, SORT, or SCREEN statement—not a procedure label and not a file name. Spelling must match the activity name exactly. EXECUTE has no inline parameter list; pass data through working storage fields, PARM fields, or files opened in both activities before the transfer.

Where EXECUTE Is Allowed

Control Flow After EXECUTE

Broadcom states that after the invoked activity executes, control returns to the next executable statement following EXECUTE. If the JOB activity hits STOP, FINISH processing runs before return. Plan working storage lifetime: fields with RESET may clear between activities depending on attributes; document which flags must survive the round trip. RETURN-CODE may reflect the nested activity on MVS when the child sets it before return.

Example: PROGRAM Routes Daily or Weekly JOB

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
PARM-FIELD  W  5  A
PROGRAM NAME SAMPLE-PROGRAM USING PARM-FIELD
  IF PARM-FIELD = 'DAILY'
    EXECUTE DAILY-JOB
  ELSE
    EXECUTE WEEKLY-JOB
  END-IF
 
JOB NAME DAILY-JOB
  ...
STOP
 
JOB NAME WEEKLY-JOB
  ...
STOP

The PROGRAM activity runs first on 11.6. PARM-FIELD might come from JCL PARM or an operator screen. Only one JOB executes per invocation; the other branch is skipped. Each JOB ends with STOP or implicitly when the next JOB would begin—here explicit STOP keeps the example clear for beginners.

SCREEN Nesting and Stacked Windows

EXECUTE from SCREEN can open another SCREEN activity—activity nesting. Each stacked window can EXIT back; when a stacked SCREEN terminates with EXIT, the product restores the prior full screen image from before the EXECUTE. EXIT from the primary screen does not restore a parent image because there is none. Design help screens and detail pop-ups as separate named SCREEN activities invoked with EXECUTE rather than duplicating hundreds of ROW statements in one map.

Recursion is forbidden: activity A may EXECUTE B, but B must not EXECUTE A. Broadcom warns recursion is not detected at compile time; runtime behavior is unpredictable. Code reviews should trace EXECUTE chains manually for cycles.

EXECUTE Versus PERFORM and CALL

STOP EXECUTE

STOP ends the current activity after optional FINISH procedure. STOP EXECUTE is stronger: it terminates the entire execute stream immediately without continuing to further activities. Use when fatal validation fails in a PROGRAM router or when an operator cancels a chained online-batch sequence. Do not confuse with EXIT from SCREEN, which returns from a nested screen to its caller when stacking is in play.

Reserved Word and Migration

EXECUTE appears on the 11.6 New Reserved Words list. Legacy DEFINE EXECUTE W 1 A flags are common in pre-migration code. Rename to WS-RUN-MODE, FL-EXEC-FLAG, or PARM-EXECUTE-YN with a prefix that cannot collide with statement vocabulary. Scan PROCEDURE DIVISION–style comment text separately—only actual DEFINE and FILE names matter to the compiler. Retest PROGRAM wrappers after rename because IF EXECUTE = 'Y' becomes a syntax error, not a field test.

Online EXECUTE JOB Pattern

AFTER-SCREEN may validate approval, MOVE operator ID and date into audit fields, then EXECUTE NIGHTLY-EXTRACT-JOB. Operators need a message that batch work was submitted—do not block the terminal for the entire JOB unless your site architecture requires synchronous batch under TSO. JCL for EXECUTE targets must be available at runtime per installation standards. Coordinate with operations on transaction IDs when CICS is involved.

Common EXECUTE Mistakes

• EXECUTE inside JOB or SORT—compile error.
• Misspelled activity NAME—runtime transfer failure.
• Recursive SCREEN A calls B calls A—unpredictable loops.
• Legacy field EXECUTE breaking 11.6 compile.
• Expecting PERFORM semantics—EXECUTE switches activities entirely.
• Forgetting working storage setup before EXECUTE JOB.

Explain It Like I'm Five

EXECUTE is telling the Easytrieve robot to pause this chore and go do a different named chore—like switching from homework to setting the table when Mom calls. When the other chore finishes, you come back to the next line of what you were doing. You cannot use the word EXECUTE as a label on your toy box anymore because it is the robot's command word. And you cannot ask chore A to start chore B if chore B tries to start chore A again—that makes the robot dizzy.

Exercises

1. Write a PROGRAM that EXECUTE one of two JOB activities based on a PARM value.
2. List three contexts where EXECUTE is illegal.
3. Rename a legacy field EXECUTE and rewrite one IF that referenced it.
4. Explain stacked SCREEN restore behavior after nested EXIT.
5. Contrast STOP and STOP EXECUTE in one sentence each.