CL Programming

Stepping into Program Objects

You can step into program objects by using:

Using F22(Step Into)

You can use F22 (Step into) on the Display Module Source display to step into a called program object in a debug session. If the next statement to be run is a CALL statement to another program object, pressing F22 (Step into) causes the first statement in the called program object to be run. The called program object is then shown in the Display Module Source display.

Note:
The called program object must have debug data associated with it in order for it to be shown in the Display Module Source display.

Using the Step Into Debug Command

Alternatively, you can use the STEP INTO debug command to step into a called program object in a debug session. To use the STEP INTO debug command, type:

STEP number-of-statements INTO

on the debug command line. Number-of-statements is the number of statements of the program object that you want to run in the next step before the program object is halted again. If one of the statements that are run contains a CALL statement to another program object, the debugger steps into the called program object. Each statement in the called program object is counted in the step. If the step ends in the called program object then the called program object is shown in the Display Module Source display. For example, if you type

STEP 5 INTO

on the debug command line, the next five statements of the program object are run. If the third statement is a CALL statement to another program object, then two statements of the calling program object are run and the first three statements of the called program object are run.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]