NET/MASTER Management Services (MS) Command Reference Manual

DEBUG BREAKPOINT
NonStop NET/MASTER MS Commands
2–28 115412 Tandem Computers Incorporated
DEBUG BREAKPOINT The DEBUG BREAKPOINT command sets a breakpoint in an NCL process at the
specified code position. When NCL encounters a breakpoint, it suspends execution of
the NCL process and displays a message in the roll-delete message display area of
your OCS window. The default message reports the number of the statement at which
execution is suspended, as part of the data. If you use the ON operand with the
DEBUG SOURCE command, the decompiled source code is displayed in addition to
the line number (see the DEBUG SOURCE command for further information). You
can use other DEBUG commands to gather information about the NCL process at the
point at which execution is suspended.
You can use any of the operands to this command in any order and any number of
times. If you type the command at the OCS command input line, you are restricted by
the length of the line. You can use the EQUATE command to assign a lengthy
command to a symbol to overcome this restriction.
DEBUG BREAKPOINT [ ID= ncl-id ] code-position
[ code-position … ]
code-position :
ERROR[ = error-handler ]
PROCEDURE={ ENTRY | EXIT | EXTERNAL }
SCOPE={ 0 | nesting-level }
STMT= stmt-position
TERMINATION
{ VAR | VBL }= variable-name
[ TYPE={ ACCESS | READ | WRITE } ]
stmt-position :
file-name [.{ proc-name | func-name } … ][ . stmt-number ] ]
stmt-number
ID= ncl-id
specifies the NCL process identifier (NCL ID) of an NCL process and sets the
current NCL process. If you do not specify an NCL ID, the default NCL ID is
assumed (see the DEBUG START command for further information about the
default NCL ID).
code-position
specifies a code position. NCL sets a breakpoint at the specified code position.
ERROR
sets a breakpoint at an error handler.
If an error is raised, NCL suspends execution just before the NCL process
executes the first statement of the error handler (the ON core statement).