The SCL Debugger

STEP

Executes statements one at a time in the active program

Abbreviation:

Syntax
Details
Example
See Also

Syntax

STEP <OVER|O>

OVER: specifies that if the next executable statement is a CALL DISPLAY, FSEDIT, or FSVIEW statement, the whole reference counts as a statement. By default, the STEP command suspends program execution at the first executable statement of the called program if that program was compiled with DEBUG ON.

Details

The STEP command executes one statement in the active program, starting with the suspended statement. When you issue a STEP command, the command

executes the next statement
displays the entry name and line number
returns control to the developer and displays the DEBUG> prompt.

By default, the STEP command suspends the execution at the first executable statement in the called program if the current statement is a CALL DISPLAY or CALL FSEDIT statement. The OVER option forces the debugger to count the call of the DISPLAY, FSEDIT, or FSVIEW routine as a statement, and program execution stops at the statement after the CALL statement. However, if the called program contains a display, execution is not suspended until you leave the display window.

When the STEP command is used to execute a SELECT statement, it jumps directly to the appropriate WHEN or OTHERWISE clause without stepping through any intervening WHEN statements.

Example

Suppose you are using the STEP command to execute the following program, which is stopped at line 15. If VAL contains 99, the STEP command goes to line 116 immediately.

line #
15    select (val);
16        when (1)
17             call display('a1');
18        when (2)
19             call display('a2');
...more SCL statements...
113        when (98)
114             call display('a98');
115        when (99)
116             call display('a99');
117        when (100)
118             call display('a100');
119        otherwise
120             call display('other');
121    end;