NET/MASTER Management Services (MS) Command Reference Manual

DEBUG BREAKPOINT
NonStop NET/MASTER MS Commands
115412 Tandem Computers Incorporated 2–33
Each breakpoint set in an NCL process is allocated a unique number, starting from
1 and incrementing by 1 through to the maximum number of breakpoints you can
set in a single debug session: 65535. A breakpoint number is not reallocated if a
breakpoint is later cleared.
If you place a breakpoint on all or any procedures or functions, or all or any error
handler calls, NCL does not require the target NCL process to be a privately
loaded copy.
If you place a breakpoint on a specific statement, including the first statement of a
procedure, function, or error handler, NCL does require the target NCL process to
be a privately loaded copy. NCL displays an error if it is not a privately loaded
copy.
For related information, see the other DEBUG commands and the EXEC, FLUSH,
SHOW NCL, and START commands.
Examples
1. The following example sets a breakpoint at the entry to and the exit from every
procedure and function. The following screen displays the results.
DEBUG BREAKPOINT PROCEDURE=ENTRY
PROCEDURE=EXIT
PROCEDURE=EXTERNAL
(08:54) --------------------- OPERATOR CONTROL SERVICES ----------------------
START WORDS THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG
NNM1060 PROCEDURE WORDS NCLID 1534 PAUSED
DEBUG START ID=1534
NNM1901 NCL 001534 DEBUG SESSION INITIATED
NNM1902 NCL 001534 SUSPENDED AT WORDS.8 LINE 22
GO ID=1534 Y
DEBUG BREAKPOINT PROCEDURE=ENTRY PROCEDURE=EXIT PROCEDURE=EXTERNAL
NNM1909 NCL 001534 BREAKPOINT 1 CREATED
NNM1909 NCL 001534 BREAKPOINT 2 CREATED
NNM1909 NCL 001534 BREAKPOINT 3 CREATED
_____________________________________________________________________________
---------- ------------------ NonStop NET/MASTER D30 ---------------- --------
PM=>