DBG$HELP.HLB  —  DEBUG  CONNECT
    (Kept debugger only.) Interrupts an image that is running without
    debugger control in another process and brings that process under
    debugger control. When used without a parameter, CONNECT brings
    any spawned process that is waiting to connect to the debugger
    under debugger control.

    On Alpha systems, the debugger command CONNECT can also be used
    to bring a target system running the Alpha operating system
    under the control of the OpenVMS Alpha System-Code Debugger.
    The OpenVMS Alpha System-Code Debugger is a kernel debugger that
    you activate through the OpenVMS Debugger.

    On Integrity servers, the debugger command CONNECT can also be
    used to bring a target system running the Integrity servers
    operating system under the control of the OpenVMS Integrity
    server System-Code Debugger. The OpenVMS Integrity server System-
    Code Debugger is a kernel debugger that you activate through the
    OpenVMS Debugger.

    If you are using the CONNECT command to debug the Alpha operating
    system, you must complete the instructions described in the
    System Code Debugger chapter of the VSI OpenVMS System Analysis
    Tools Manual before you issue the command. (These instructions
    include the creation of an Alpha device driver and the setup
    commands activating the OpenVMS Alpha System-Code Debugger.) You
    must also have started the OpenVMS Debugger with the DCL command
    DEBUG/KEEP.

    Format

      CONNECT  [process-spec]

      CONNECT  %NODE_NAME node-name

1  –  Parameters

 process-spec

    Specifies a process in which an image to be interrupted is
    running. The process must be in the same OpenVMS job as the
    process in which the debugger was started. Use any of the
    following forms:

    [%PROCESS_NAME] proc-    The OpenVMS process name, if that
    name                     name contains no space or lowercase
                             characters. The process name can include
                             the asterisk (*)  wildcard character.
    [%PROCESS_NAME] "proc-   The OpenVMS process name, if that name
    name"                    contains space or lowercase characters.
                             You can also use apostrophes (') instead
                             of quotation marks (").
    %PROCESS_PID proc-id     The OpenVMS process identifier (PID, a
                             hexadecimal number).

 node-name

    (Alpha or Integrity servers only) When you are debugging an Alpha
    or Integrity servers operating system, specifies the node name
    of the machine to which you are connecting (the target machine
    running the Alpha or Integrity servers operating system).

2  –  Qualifiers

2.1    /PASSWORD

       /PASSWORD="password"

    (Alpha or Integrity servers only) When you are debugging an Alpha
    or Integrity servers operating system, specifies the password
    for the machine to which you are connecting (the target machine
    running the Alpha or Integrity servers operating system). If
    a password has not been established for that machine, this
    qualifier can be omitted.

2.2    /IMAGE_PATH

       /IMAGE_PATH="image-path"

    (Alpha or Integrity servers only) When you are debugging an Alpha
    operating system, specifies the image-path for the machine from
    which you are connecting (the host machine running the debugger).
    The image-path is a logical name that points to the location of
    system images. The default logical name is DBGHK$IMAGE_PATH:.

3  –  Description

    (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.

4  –  Examples

    1.DBG_1> CONNECT

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

    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 UIC group as the process in which the
      debugger was started. Also, the image must not have been linked
      with the /NOTRACEBACK qualifier.

    3.DBG> CONNECT %NODE_NAME SCDTST /PASSWORD="eager_beaver"
      %DEBUG-I-NOLOCALS, image does not contain local symbols
      DBG>

      This CONNECT command brings the target system running the
      OpenVMS operating system under debugger control. This example
      specifies that the target system has a node name of SCDTST and
      a password of eager_beaver.
Close Help