Inspect Manual

High-Level Inspect Commands
Inspect Manual—429164-006
6-26
BREAK
This illustrates how to set a data breakpoint on a local variable to avoid unrelated
data breakpoints being reported for the local variable when the procedure is no
longer active.

TAL P-Relative Arrays
Because TAL P-relative arrays are stored in the code space rather than the data
space, you must use the READ clause to set a data breakpoint at a P-relative
array.
Usage Consideration for Code Breakpoints

STOP and ABEND for Code Breakpoints
If you have a data item or a code label named STOP visible from the current scope
unit, the command BREAK STOP sets a breakpoint on the data item or the code
label. To set a breakpoint that is reported when the program stops, preface the
word STOP with a “#”, as in BREAK #STOP.
Conversely, if you have a scope unit in your program named STOP, and you issue
the command BREAK #STOP, a breakpoint is placed in your program. If you have
both a data item or a code label named STOP and a scope unit named STOP, you
cannot set a breakpoint at STOP. The same alternatives and restrictions apply for
setting a breakpoint at ABEND. To avoid restrictions on the use of STOP and
ABEND breakpoints, refrain from declaring data items, labels, or scopes named
STOP or ABEND.
Related Commands

CLEAR on page 6-27

FB on page 6-84

IF on page 6-103

LIST BREAKPOINT on page 6-131
#10 PROC X;
#11 BEGIN
#12 INT I;
#13
#14 CALL Y(i);
.
.
.
#42 END;
-PROGRAM-BREAK #X THEN "BREAK I;RESUME"
-PROGRAM-BREAK #X.#42 THEN "CLEAR I;RESUME"