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

Stopping a Debug Session
Debugging an NCL Process
106160 Tandem Computers Incorporated 9–59
Stopping a Debug
Session
The DEBUG STOP command stops a debug session. You can stop debugging either
one or more specific NCL processes, or all NCL processes.
Stopping the Debugging of
a Specific NCL Process
To stop debugging one or more specific NCL processes, you must use the DEBUG
STOP ID=ncl-id command. The following example targets a single NCL process:
DEBUG STOP ID=12
The following example targets multiple NCL processes:
DEBUG STOP ID=34 ID=56 ID=78
If you originally targeted one or more NCL processes for debugging, all other NCL
processes execute normally after you stop debugging the single or multiple NCL
processes. (This applies when you originally used the DEBUG START ID=ncl-id
command to start a debug session and the single NCL process terminates execution, or
when you used the DEBUG START PROCS=CURRPROCS command to start a debug
session and all targeted NCL processes terminate execution.)
If you originally targeted an environment for debugging (by using any other DEBUG
START command), the environment is still targeted as being debugged if you stop the
debugging of one or more specific NCL processes in the environment. This means if
you execute another NCL procedure in the environment, the new NCL process is also
targeted for debugging.
Stopping the Debugging of
an Environment
To stop the debugging of all NCL processes in an environment, you must use the
DEBUG STOP ALL command:
DEBUG STOP ALL
NCL procedures that you execute after this command are not targeted for debugging
and execute normally.