Library /sys$common/syshlp/dbg$help.hlb DEBUG, CONNECT, Description  *Conan The Librarian (sorry for the slow response - running on an old VAX)

    (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 cannot connect to a process created
    through a $CREPRC system service call.

    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.) Restrictions on Process
    Creation, by Debugger Version Number lists the restrictions that
    apply to specific versions of the debugger.

    Table 1-1 Restrictions on Process Creation, by Debugger Version
              Number

                           Then you can
                           connect to
                           a process
                           started
    If you are running...  by...          With the SYSGEN Parameter?

    VAX Version 5.5-2,     You            No
    earlier
    Alpha Version 6.0,
    earlier
    VAX Version 6.0        You, Member    Yes
                           of UIC Group
    VAX Version 6.1,       You, Member    No
    later                  of UIC Group
    Alpha Version 6.1,
    later

    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 image modules must have been compiled and linked with the
    /DEBUG qualifier. The image cannot have been 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.

    Using the CONNECT Command to Debug the Alpha Operating System
    (Alpha only)

    You can use the CONNECT command to debug Alpha operating
    system code with the OpenVMS Alpha System-Code Debugger (SCD).
    Typically, you issue this command from a timesharing (host) Alpha
    machine (running SCD), and you connect to a standalone (target)
    Alpha machine (running the Alpha operating system). Communication
    between the two machines occurs over the Ethernet network.

                                   NOTE

       The port used for SCD on the target machine is not
       configured at all, and cannot be used for any other
       purpose, such as DECnet, LAT, user applications, and so on.
       Therefore, to be able to use DECnet or to be in a cluster
       while using SCD, you must have another Ethernet port for
       that traffic.

    In some cases, you may find that you need to use the alternative
    Delta/XDelta Debugger to debug operating system code. These cases
    include:

    o  When you have access to only one Alpha machine for debugging

    o  When you are debugging portions of code that generate Ethernet
       traffic on the target system and have only one ethernet port.

    Generally, however, the OpenVMS Alpha System-Code Debugger is
    preferred for debugging Alpha operating system code. For complete
    information on using this debugger, see the OpenVMS Alpha System
    Analysis Tools Manual.

    Related commands:

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