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

Starting Multiple Debug Sessions
Debugging an NCL Process
9–30 106160 Tandem Computers Incorporated
environment. The DEBUG STEP command shows that the default NCL ID is correctly
set to that of the current NCL process, ZEX0903N.
Targeting a Dependent
Processing Environment
This section has discussed debugging in top-level environments, current execution
environments, primary processing environments, and background processing
environments. You can also target NCL processes in a dependent processing
environment. You can do so in two ways:
By targeting both the current execution environment and all lower-level
dependent processing environments for debugging. To do so, use the ENV=ALL
operand of the DEBUG START command. For example:
DEBUG START ENV=ALL
By targeting all dependent processing environments below the current execution
environment for debugging. To do so, use the ENV=DEPENDENT operand of the
DEBUG START command. For example:
DEBUG START ENV=DEPENDENT
You can further qualify each specification by execution state, window, user ID, or
terminal using the PROCS, WINDOW, USER, or TERM operands, respectively, as
discussed earlier in this section.
For example, assume user ID NMTJN is logged on twice at terminal #8368419 and
#8368421. The following command targets newly executed NCL processes started in a
dependent processing environment in window 2:
DEBUG START USER=NMTJN TERM=#8536078 WINDOW=2 ENV=DEPENDENT
Starting Multiple
Debug Sessions
To start multiple debug sessions, you must issue multiple DEBUG START commands.
Starting multiple debug sessions allows you to target more than one NCL process and
more than one environment for debugging concurrently. After starting multiple
debug sessions, you must identify the specific NCL process to debug by using the
DEBUG SET ID=ncl-id command or another DEBUG command that specifies an NCL
ID to set an NCL process as the current NCL process.
You can start multiple debug sessions for any combination of the following:
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.