Exiting Processing Blocks

The following statements are used for program-controlled exit from processing blocks: RETURN, EXIT, CHECK, REJECT, and STOP. These statements end the processing block immediately. Depending on which processing block the statement is executed in, the runtime environment normally behaves according to the following schema, although exceptions in the individual statements must be noted.

• Procedures are exited and the program returns to a point after the procedure call. The output parameters of the procedures are transferred to the assigned actual parameters.

• Dialog modules are exited and the program returns to a point after the calling point in the screen flow logic.

• Event blocks are exited and control is returned to the runtime environment. Except in the case of reporting event blocks GET, the runtime environment continues with executing the program as if the event block was terminated normally (as if its last statement was reached).

• Reporting event blocks GET are exited and nodes that are on a lower level in the hierarchy structure of the associated logical database are no longer processed. If the end of the hierarchy level has been reached, the logical database reads the next line of the current node, or the next highest node.

In addition to the statements described here, statements that call other units without returning to the caller after the call is made, also end their processing block. These are:

• LEAVE [TO] SCREEN

• LEAVE LIST-PROCESSING

• LEAVE TO TRANSACTION

• SUBMIT without AND RETURN

Messages and the triggering of exceptions can also end processing blocks.

Note

Leaving a procedure by pressing RETURN (or EXIT or CHECK) is the trouble-free way to end the procedure. Formal parameters for which the pass by value is defined are not passed to the assigned current parameters only if the procedure terminates after an error (an exception is triggered or a message is sent).