Releases a process from debugger control without terminating the
process (kept debugger only).
Format
DISCONNECT process-spec
1 – Parameters
process-spec
Specifies a process currently under debugger control. Use any of
the following forms:
[%PROCESS_NAME] process- The process name, if that name does not
name contain spaces or lowercase characters.
The process name can include the
asterisk (*) wildcard character.
[%PROCESS_NAME] The process name, if that name contains
"process-name " spaces or lowercase characters. You
can also use apostrophes (') instead of
quotation marks (").
%PROCESS_PID process_id The process identifier (PID, a
hexadecimal number).
[%PROCESS_NUMBER] The number assigned to a process when
process-number it comes under debugger control. A
(or %PROC process- new number is assigned sequentially,
number) starting with 1, to each process. If
a process is terminated with the EXIT
or QUIT command, the number can be
assigned again during the debugging
session. Process numbers appear in a
SHOW PROCESS display. Processes are
ordered in a circular list so they can
be indexed with the built-in symbols
%PREVIOUS_PROCESS and %NEXT_PROCESS.
process-set-name A symbol defined with the
DEFINE/PROCESS_SET command to represent
a group of processes.
%NEXT_PROCESS The next process after the visible
process in the debugger's circular
process list.
%PREVIOUS_PROCESS The process previous to the visible
process in the debugger's circular
process list.
%VISIBLE_PROCESS The process whose stack, register set,
and images are the current context for
looking up symbols, register values,
routine calls, breakpoints, and so on.
2 – Description
(Kept debugger only.) The DISCONNECT command releases a specified
process from debugger control without terminating the process.
This is useful if, for example, you have brought a running
program under debugger control with a CONNECT command and you now
want to release it without terminating the image. (In contrast,
when you specify a process with the EXIT or QUIT command, the
process is terminated.)
CAUTION
The debugger kernel runs in the same process as the image
being debugged. If you issue the DISCONNECT command for this
process, you release your process, but the kernel remains
activated.
This activation continues until the program image finishes
running.
If you install a new version of the debugger while one or
more disconnected but activated kernels inhabit user program
space, you can experience problems with debugger behavior if
you try to reconnect to one of those kernels.
Related commands:
EXIT
QUIT
CONNECT
3 – Example
DBG> DISCONNECT JONES
This command releases process JONES from debugger control
without terminating the process.