VMS Help  —  CONNECT
    Connects your physical terminal to a virtual terminal that is
    connected to another process.

    You must connect to a virtual terminal that is connected to
    a process with your user identification code (UIC). No other
    physical terminals may be connected to the virtual terminal.

    Format

      CONNECT  virtual-terminal-name

1  –  Parameter

 virtual-terminal-name

    Specifies the name of the virtual terminal to which you are
    connecting. A virtual terminal name always begins with the
    letters VTA. To determine the name of the virtual terminal that
    is connected to a process, enter the SHOW USERS command.

2  –  Qualifiers

2.1    /CONTINUE

       /CONTINUE
       /NOCONTINUE (default)

    Controls whether the CONTINUE command is executed in the current
    process just before connecting to another process. This qualifier
    allows an interrupted image to continue processing after you
    connect to another process.

    The /CONTINUE qualifier is incompatible with the /LOGOUT
    qualifier.

2.2    /LOGOUT

       /LOGOUT (default)
       /NOLOGOUT

    Logs out your current process when you connect to another process
    using a virtual terminal.

    When you enter the CONNECT command from a process that is not
    connected to a virtual terminal, you must specify the /LOGOUT
    qualifier; otherwise, DCL displays an error message.

    The /LOGOUT qualifier is incompatible with the /CONTINUE
    qualifier.

3  –  Examples

    1.$ RUN AVERAGE
 <Ctrl/Y>

      $ CONNECT/CONTINUE VTA72

      In this example, you use the RUN command to execute the image
      AVERAGE.EXE. You enter this command from a terminal that is
      connected to a virtual terminal. Next, you press Ctrl/Y to
      interrupt the image. After you interrupt the image, enter the
      CONNECT command with the /CONTINUE qualifier. This operation
      issues the CONTINUE command, so the image continues to run and
      connects you to another virtual terminal. You can reconnect to
      the process later.

    2.$ SHOW USERS/FULL
           OpenVMS User Processes at 21-JUL-2009 14:11:56.91
         Total number of users = 51,  number of processes = 158

      Username    Node   Process Name       PID     Terminal
      KIDDER     BUKETT  KIDDER           29A0015E  FTA3:
      KIDDER     BUKETT  _FTA4:           29A0015F  FTA4:
      KIDDER     RACEY1  KIDDER           05800062  FTA5:
      KIDDER     RACEY1  DECW$MWM         0580005D  MBA44:   Disconnected
      KIDDER     RACEY1  DECW$SESSION     05800059
      KIDDER     RACEY1  VUE$KIDDER_2     0580005E  (subprocess of 05800059)
      KIDDER     RACEY1  VUE$KIDDER_3     0580005F  MBA51:   Disconnected
      KIDDER     RACEY1  VUE$KIDDER_4     05800060  MBA53:   Disconnected
      SMITH      BUKETT  SMITH            29A002C1  FTA7:
      SMITH      BUKETT  SMITH_1          29A006C2  (subprocess of 29A002C1)
      SMITH      BUKETT  SMITH_2          29A00244  (subprocess of 29A002C1)
      SMITH      HAMLET  SMITH            24800126  FTA6:
      SMITH      HAMLET  DECW$BANNER      24800155  (subprocess of 24800126)
      SMITH      HAMLET  DECW$MWM         2480011F  MBA170:  Disconnected
      SMITH      HAMLET  DECW$SESSION     2480011D  FTA5:
      .
      .
      .

      $ CONNECT VTA273
        SMITH         logged out at 22-DEC-2001 14:12:04.53
      $

      This example shows how to reconnect to your original process
      after you have lost the carrier signal. First, you must log
      in again and create a new process. After you log in, enter the
      SHOW USERS/FULL command to determine the virtual terminal name
      for your initial process. Then enter the CONNECT command to
      connect to the virtual terminal associated with your original
      process. The process from which you enter the CONNECT command
      is logged out because you have not specified any qualifiers.

      When you reconnect to the original process, you continue
      running the image that you were running when you lost the
      carrier signal. In this example, the user SMITH was at
      interactive level when the connection was broken.
Close Help