NET/MASTER Network Control Language (NCL) Programmer's Guide

Starting a Single Debug Session
Debugging an NCL Process
106160 Tandem Computers Incorporated 9–17
Starting a Single
Debug Session
To start a single debug session, you must use the DEBUG START command. You
must execute the DEBUG START command before you can use any other DEBUG
command. When starting a debug session, you can target:
A single NCL process in any environment.
One or more NCL processes by execution state: currently executing, newly
executed, or both types.
NCL processes in a specific window, either a top-level environment or a primary
processing environment.
A specific user’s NCL processes, by user ID or terminal name.
One or more NCL processes in a background processing environment.
One or more NCL processes in a dependent processing environment.
Targeting a Single NCL
Process
Every NCL process has a unique NCL ID. You can target a single NCL process for
debugging by specifying its NCL ID using the ID operand of the DEBUG START
command. By specifying an NCL ID, you can target any NCL process for debugging,
regardless of owner, in any environment—providing you have the authority level to
do so. To target a single NCL process for debugging, follow these steps:
1. Execute one or more NCL procedures.
2. Use the SHOW NCL command to determine the unique NCL ID of the NCL
process to debug.
3. Use the DEBUG START ID=ncl-id command to simultaneously start the debug
session and set the current NCL process. The NCL process is suspended at the
statement it is currently executing.
Note The ID operand of the DEBUG START command has a default authority level of 2. You must have an
authority level of at least 2 to target a single NCL process for debugging, if you do not own the NCL
process.
You can subsequently use other DEBUG commands to debug the NCL process. The
debug session ends when the NCL process terminates execution, unless you use a
DEBUG STOP command to stop the debug session earlier.
See Section 8, “Executing NCL Procedures,” for more information on NCL IDs. See
Section 16, “Environments and Command Processing,” for more information on the
different types of NonStop NET/MASTER MS environments.