Note:  This command applies  only  to  a  multiprocess  debugging
     configuration (when DBG$PROCESS has the value MULTIPROCESS).

     Interrupts an image that is running without debugger  control  in
     another  process  and brings that process under debugger control.
     When used without a parameter, brings any spawned process that is
     waiting to connect to the debugger under debugger control.

 Format:

       CONNECT [/qualifier] [process-spec[, . . . ]]

     When you specify a process, the CONNECT command  enables  you  to
     interrupt  an  image  that is running without debugger control in
     that process and bring the process under debugger  control.   The
     command  is  useful  if,  for example, you run a debuggable image
     with the DCL command RUN/NODEBUG or  if  your  program  issues  a
     LIB$SPAWN  run-time library call or a $CREPRC system service call
     that does not invoke the debugger.

     You can bring a process under debugger  control  in  this  manner
     only  if  that  process  is  in  the same job tree as the process
     running the debugging  session  (the  process  running  the  main
     debugger  image,  DEBUGSHR.EXE),  and  only  if the image was not
     linked with the /NOTRACEBACK  qualifier.   Also,  you  have  full
     symbolic  information  for  that  image  only if its modules were
     compiled and linked with the /DEBUG command qualifier.

     When the process is brought under debugger control, execution  of
     the image is suspended at the point at which it was interrupted.

     When used without a parameter, the  CONNECT  command  brings  any
     processes  that  are waiting to connect to your debugging session
     under debugger control.  If no process is waiting, you can  press
     CTRL/C to abort the CONNECT command.

     By default, a tracepoint is triggered when a process  is  brought
     under debugger control.  This predefined tracepoint is equivalent
     to that resulting from entering the command SET TRACE/ACTIVATING.
     The  process is then known to the debugger and is identified in a
     SHOW PROCESS display.

Additional information available:

ExamplesParameters

     1   DBG_1> CONNECT

     This command brings any processes that are waiting to
     be connected to the debugger under debugger control.

     2   DBG_1> CONNECT JONES_3

     This command interrupts the image running in process
     JONES_3 and brings the process under debugger control.
     Process JONES_3 must be in the same job tree as the
     process where the debugger was invoked. Also, the
     image must not have been linked with the /NOTRACEBACK qualifier.

 process-spec

     Specifies a process in  which  an  image  to  be  interrupted  is
     running.   The  process  must  be  in  the  same  job tree as the
     debugging session.  Use any of the following forms:

     [%PROCESS_NAME] process-name    The VMS process name, if that
                                     name contains no spaces or
                                     lowercase characters[1].

     [%PROCESS_NAME] "process-name"  The VMS process name, if that
                                     name contains spaces or lowercase
                                     characters. You can also use
                                     apostrophes (') instead of
                                     quotation marks (").

     %PROCESS_PID process_id         The VMS process identification
                                     number (PID, a hexadecimal number).
     _______________________________________________________
     [1]The process name can include the asterisk wildcard
     character (*)