(Kept debugger only.) 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 that does not
    start the debugger. You can connect to a process created through
    a $CREPRC system service call only if you specify LOGINOUT.EXE as
    the executable image.

    Depending on the version of the debugger you are running on your
    system, you may be restricted to connection with processes you
    created, or you may be able to connect to processes created by
    any member of your user identification code (UIC) group. (In some
    cases, you may have to set the SYSGEN SECURITY_POLICY parameter
    to 8 before you create the process.)

    If debugger logicals (DEBUG, DEBUGSHR, DEBUGUISHR, DBGTBKMSG,
    DBG$PROCESS, DBG$HELP, DBG$UIHELP, DEBUGAPPCLASS, and
    VMSDEBUGUIL) exist, they must translate to the same definitions
    in both the debugger and the target process.

    The code in the image must be compiled with the /DEBUG qualifier
    and the image must be linked with either /DEBUG or /DSF. The
    image must not be linked with the /NOTRACEBACK qualifier.

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

    When you do not specify a process, 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 SET TRACE/ACTIVATING command.
    The process is then known to the debugger and can be identified
    in a SHOW PROCESS display.

    You cannot use the CONNECT command to connect to a subprocess
    of a process running under debugger control.Use the SET PROCESS
    command to connect to such a subprocess.

    Related commands:

       DISCONNECT
       Ctrl/Y
       (SET,SHOW,CANCEL) TRACE

    Using the CONNECT Command to Debug the OpenVMS Operating System
    (Alpha and Integrity servers only)

    You can use the CONNECT command to debug Alpha or Integrity
    servers operating system code with the OpenVMS System Code
    Debugger (SCD). This capability requires two systems, one called
    the host and the other called the target. The host and target
    must be running the same operating system (Alpha or Integrity
    servers). The host is configured as a standard OpenVMS system,
    from which you run the debugger using DEBUG/KEEP, then enter the
    CONNECT command. The target is a standalone system that is booted
    in a special way that enables SCD. Communication between the host
    and the target occurs over the Ethernet network.

    For complete information on using the OpenVMS System Code
    Debugger, see the VSI OpenVMS System Analysis Tools Manual.