After a breakpoint is encountered, you can run a specified number of statements
of a program object, then stop the program again and return to the Display
Module Source display. You do this by using the step function of the ILE source
. The program object resumes running on the next statement of the module object
in which the program stopped. Typically, a breakpoint is used to stop the
program object.
Breakpoints can be set before the program is called and while you are stepping
through the program. Breakpoints can also be automatically generated for input
and output specifications if the default OPTION(*DEBUGIO) is specified. If
this option is selected, a STEP on a READ statement will stop at the input
specification. You can choose not to generate breakpoints for input and output
specifications with OPTION(*NODEBUGIO).
You can step into an OPM program if it has debug data available and if
the debug session accepts OPM programs for debugging.
You can step through a program object by using:
- F10 (Step) or F22 (Step into) on the Display Module Source display
- The STEP debug command
The simplest way to step through a program object one statement at a time
is to use F10 (Step) or F22 (Step into) on the Display Module Source display.
When you press F10 (Step) or F22 (Step into), then next statement of the module
object shown in the Display Module Source display is run, and the program
object is stopped again.
Note: You cannot specify the number of
statements to step through when you use F10 (Step) or F22 (Step into). Pressing
F10 (Step) or F22 (Step into) performs a single step.
Another way to step through a program object is to use the STEP debug command.
The STEP debug command allows you to run more than one statement in a single
step. The default number of statements to run, using the STEP debug command,
is one. To step through a program object using the STEP debug command, type:
STEP number-of-statements
on the debug command line. The variable
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. For example, if you
type
STEP 5
on the debug command line, the next five statements
of your program object are run, then the program object is stopped again and
the Display Module Source display is shown.
When a call statement to another program or procedure is encountered in
a debug session, you can:
- Step over the call statement, or
- Step into the call statement.
A call statement for
ILE RPG includes any of the following operations:
- CALL
- CALLB
- CALLP
- Any operation where there is an expression in the extended-factor 2 field,
and the expression contains a call to a procedure.
If you choose to step over the call statement, then
you will stay inside the current procedure. The call statement is processed
as a single step and the cursor moves to the next step after the call. Step
over is the default step mode.
If you choose to
step into the call statement, then
each statement inside the call statement is run as a single step. Depending
on the number of steps specified, the step command may end inside the call
statement, in which case the source for the call statement is shown in the
Display Module Source display.
Note: You cannot step over or step
into RPG subroutines. You can, however, step over and into subprocedures.