Inspect Manual

High-Level Inspect Commands
Inspect Manual429164-006
6-21
BREAK
WRITE READ
specifies that a break event should occur on both read and write access of
the data item.
ABEND
specifies a break on ABEND is a break on the event for the process being
debugged, not the system procedure.
The ABEND clause is invalid for PATHWAY requester programs.
STOP
specifies a break on STOP is a break on the event for the process being
debugged, not the system procedure.
The STOP clause is invalid for PATHWAY requester programs.
brk-condition
specifies whether encountering the break location should trigger a break event.
Inspect provides two brk-condition clauses, EVERY and IF; you can use these
clauses separately or together. When they are used together, the EVERY clause is
evaluated before the IF clause.
EVERY integer
specifies that the breakpoint should trigger a break event every integer times
the break location is encountered.
The maximum value of integer is 32767.
IF expression
specifies that the breakpoint should trigger a break event only if expression
evaluates to TRUE (that is, a nonzero value). Because Inspect performs this
test when the break location is encountered, all unqualified variable references
in expression inherit the scope path of the scope unit containing the break
location. Syntax and semantic checking are not done until the breakpoint has
been triggered.
brk-action
specifies what actions are to occur automatically when the breakpoint generates a
break event. Inspect provides two brk-action clauses, TEMP and THEN; you
can use these clauses separately or together.
TEMP [ integer ]
directs Inspect to clear the breakpoint after it triggers a break event integer
times. If you omit integer, Inspect assumes the integer value 1.