Inspect Manual

High-Level Inspect Commands
Inspect Manual—429164-006
6-214
Usage Consideration for Accelerated Programs
Inspect command. When a debug event (such as a break event) interrupts the
sequence, a RETURN continues to mean “redo the STEP.”

Breakpoints in Called Scope Units
If you attempt to step over a call to a scope unit that contains a breakpoint, Inspect
terminates the STEP command and stops in the called scope unit.

Considerations when Using STEP IN

If you enter a STEP IN command and a procedure call is not within the range
of the step, the command executes as though you had not specified the IN
parameter.

If you enter a STEP IN command and step into the wrong procedure, enter a
STEP OUT to return to the calling procedure.

If you enter a STEP IN command, execution stops when a new procedure is
entered, regardless of the remaining range specified by the command.

Considerations when using STEP OUT

The SUBPROCS clause prevents stepping out of the containing procedure if
you issue a STEP OUT SUBPROC command and then repeat the command
by pressing the RETURN key.

If you use the SUBPROCS clause when you are not in a TAL subprocedure,
Inspect displays this warning message:

If your program modified the S register and you issue a STEP OUT command
when the current location is within a subprocedure, Inspect displays this warning
message:

When using STEP OUT, you cannot step out of the main scope unit (that is, the
scope unit controlling the program). If you attempt to step out, Inspect displays the
message:
Usage Consideration for Accelerated Programs
The STEP command can behave differently when stepping an accelerated program on
a TNS/R system because you will only be prompted at memory-exact points.
For more information, see Section 15, Using Inspect on a TNS/R System.
** Inspect warning 191 ** Current location is not a subproc
** Inspect warning 192 ** Unable to step subproc(s) due to 'S' register
modification
** Inspect error 173 ** STEP OUT is not allowed from main scope unit