Initially, the debugger may be entered in one of several ways:
* When you specify the "-d" option to the runtime; for example:
runcbl -d payroll
* Whenever a STOP statement executes that is not a STOP RUN.
* When you have started the program in debugging mode, and you press the abort key (such as Control-C). This method of starting the debugger does not work on all machines.
If you have already entered the debugger initially, you may reenter it in one of the following ways:
* When the program reaches a breakpoint. Breakpoints are set by the user through the debugger.
* When you are using the debugger to "step" through the program, and the step count has been reached.
* When you are monitoring a variable, and it changes. In this case, an automatic breakpoint is generated at the beginning of the next statement.
* When you have compiled the program with "-Za" along with "-Gd", and an array violation occurs. In this case, you automatically break to the debugger and see the line on which the array violation occurred.