The debugger can execute a series of statements up to the next breakpoint or the specified statement all at once, or it can execute it statement by statement for checking of the behavior of each statement in the execution path. However, if a breakpoint is detected during execution of the program, execution is halted at this breakpoint even when it has not reached any specified statement.
Note
If the path of the executable program to be debugged is not displayed for the selected tree element in the "Debug" view, the execution operation of the debugger is disabled. If the correct tree element has not been selected, select a tree element for which the path of an executable program is displayed, and run the debugger.
In unconditional execution, a program is executed without any halt statement specified. The program is executed until either the next breakpoint is reached or the program exits.
Use any of the following methods to perform unconditional execution:
Select the toolbar button of the "Debug" view.
Select "Resume" from the context menu of the "Debug" view.
Select "Run" > "Resume" from the menu bar.
Press the F8 shortcut key.
Step-into executes only one statement in a program. If the executed statement invokes another process such as a CALL statement, control jumps to the called process, and execution is halted.
Use any of the following methods to perform Step Into:
Select the toolbar button of the "Debug" view.
Select "Step Into" from the context menu of the "Debug" view.
Select "Run" > "Step Into" from the menu bar.
Press the F5 shortcut key.
Note
When Step Into is executed just before a COPY statement, execution is halted at the first statement in the COBOL Library.
Step-over executes only one statement in a program. If the executed statement invokes another process such as a CALL statement, execution is not halted in the called process. Instead, all of the called process is executed, and execution is halted at the next statement following the calling statement.
Use any of the following methods to perform Step Over:
Select the toolbar button of the "Debug" view.
Select "Step Over" from the context menu of the "Debug" view.
Select "Run" > "Step Over" from the menu bar.
Press the F6 shortcut key.
Note
When Step Over is executed just before a COPY statement, execution is halted at the first statement in the COBOL Library.
When execution has been halted within a subprogram or method, this function performs execution until control returns to the calling process.
Use any of the following methods to perform execution until control returns to the calling process:
Select the toolbar button of the "Debug" view.
Select "Step Return" from the context menu of the "Debug" view.
Select "Run" > "Step Return" from the menu bar.
Press the F7 shortcut key.
Note
When Step Return is executed in a COBOL library, the program is executed until returning to the call process of the program in which the COBOL library is specified.
The program is executed from the current halt statement to the statement at which the cursor is positioned in the COBOL editor.
To execute the program to the specified statement:
Select "Run to Line" from the context menu of the COBOL editor.
Note
Run to Line cannot be executed from a COBOL library. In order to execute to the specified statement, use one of the operations below.
Set the breakpoint to the target line and use Unconditional execution.
Repeat Step Into or Step Over until the control reaches the target line.