B TELL, NETWORKING, Executes DCL Commands on Remote Nodes via DECnet  ?  This command procedure will execute commands on a remote node.   "  The command syntax for tell is :->  @TELL[/output=filename] NODENAME[,...] DCL-COMMAND [&] [|...]      P1 - NODENAME: M     More than one nodename can be specified, each being seperated by a comma.      Nodename can be a symbol  I     Nodename can be a file containing a list of nodes (one node per line) F       specified by an @ prefix (@file). The default extension is .dat.*       Comments should start with a ! or #.D     A double colon (::) after the nodename is optional and specifies       decnet transport. D     A single colon (:) after the nodename specifies tcpip transport.2     "0" can be used to specify the local nodename.H     If you do not have proxy access then you can specify access control M       information as part of the nodename specification (node"user password") A     You can force a routing path by specifiy nodename of the from        nodename::nodename::G     If in command mode and two or more nodenames are specified then on  L       completion TELL displays a summary listing of unreachable nodes. This G       feature can be disabled by defining the logical name as follows:- 6       $ DEFINE/PROCESS/NOLOG TELL_INHIBIT_SUMMARY TRUEG     If node not specified then the symbol tell_default_nodes is used if        defined.      P2 to P8 - DCL COMMAND:     INTERACTIVE MODE: J       If no DCL command is specified then you will be in interactive mode.L       At that point you will have a DCL session in the context of the remoteK         node. The standard EXIT command will return you to your local node. L       If a decnet nodename is specified then the tell decnet object will be 7         used to process the command on the remote node. E       If a tcpip nodename is specified then an rlogin command is used F         used to process the command on the remote node. A password can*         be specified but will not be used.     COMMAND MODE: H       Here the DCL commands are specified in P2 to P8 and are separated K         by a vertical bar "|". Quotes are optional and are only required to *         reduce the number of P parameters.L       If a decnet nodename is specified then the tell decnet object will be 7         used to process the command on the remote node. B       If a tcpip nodename is specified then an rsh command is used8         used to process the command on the remote node.      DETACHED MODE:A       Jobs can be run in the background as a detached process by  ?       suffixing the & (unix background command) to any command. ?       This can be done from either Interactive or Command Mode.   L     Note that you cannot issue commands that require terminal input such as L     EDIT etc. This is a restriction of the DECnet task-task software and notK     of TELL itself. Some of these restrictions can be overcome by defining  N     the verb as a foreign command. This allows many commands to be entered on      a single line.&         eg. $ AUTHORIZE :== $AUTHORIZE&             $ AUTHORIZE SHOW KINGSMILL           QUALIFIERS:;     /Output can be used to direct the output to a filename.         EXAMPLES:  #    $ TELL :== @SYS$MANAGER:TELL.COM J         All the following examples assume that the tell symbol is defined.%         Place this in your login.com.       $ TELL MVAX,UNIXA"geoffk": C         This command will allow you to interactively enter commands C         on both MVAX and UVAX. Default proxy access is used to MVAX ? 	  and the geoffk account will be used on UNIXA (unix machine).       $ TELL MVAX SHOW ERROR 5         This command relies on proxy access to MVAX.  2         It does a remote $show error on node MVAX.      $ TELL UNIXA: "date" 6         This command relies on proxy access to UNIXA. -         It does an "$RSH UNIXA date" command.   !    $ TELL_DEFAULT_NODES == "MVAX"     $ TELL "" SHOW ERROR E         This command uses the symbol tell_default_nodes to obtain the 5 	  nodename and relies on proxy access to node MVAX.  2         It does a remote $show error on node MVAX.  3    $ TELL/OUTPUT=SYS$LOGIN:TELL.OUT MVAX SHOW ERROR 5         This command relies on proxy access to MVAX.  A         It does a remote $show error on node MVAX with the output 2            directed to the file sys$login:tell.out  /    $ TELL MVAX"KINGSMILL PASSWORD":: SHOW ERROR J         this command supplies access control to accounts that do not have          proxy access  &    $ TELL MVAX"KINGSMILL":: SHOW ERRORM         Under VMS V5.x you can have a number of different proxy users pointed M         to one account. This example show how to gain access to a non-default I         proxy account. Note that only the username needs to be specified.   #    $ TELL MVAX,TVAX,SVAX SHOW ERROR A         this command will do a show error on MVAX, TVAX and SVAX.   $    $ DECA_CLUSTER :== MVAX,TVAX,SVAX#    $ TELL 'DECA_CLUSTER' SHOW ERROR A         this command will do a show error on MVAX, TVAX and SVAX.       $ TYPE DECA_CLUSTER.DAT    MVAX     TVAX     SVAX "    $ TELL @DECA_CLUSTER SHOW ERRORA         this command will do a show error on MVAX, TVAX and SVAX.   ,    $ TELL MVAX,UVAX: "SHOW ERROR"|"SHOW NET"A         this command will do both a show error and a show net on  9         MVAX (using DECnet) and UVAX (using TCPIP [RSH]).   F    $ TELL MVAX,TVAX "SET DISPLAY/CREATE/NODE=MAXPS1" | "CREATE/TERM &"I         this command will create a detached decterm on both MVAX and TVAX       $ TELL MVAX    MVAX_KINGSMILL>> SHOW ERROR&    MVAX_KINGSMILL>> SET PROC/PRIV=OPER%    MVAX_KINGSMILL>> MCR NCP SHOW EXEC     MVAX_KINGSMILL>> EXIT    $J         This is an example of an interactive session. The prompt indicatesD         the remote nodename and username, whilst the ">>" is used to8         distinguish between a local and remote session.      #    $ TELL MVAX TELL TVAX SHOW ERROR !    $ TELL MVAX::TVAX:: SHOW ERROR :         Both of these commands perform the same function. I         The first performs a nested TELL, ie. TELL node MVAX to TELL node E           TVAX to do a $ show error. Only command mode is valid with  I           this syntax and you must specify the command as TELL not @tell. H         The second example show how to do the same thing using Poor MansJ           Routing (PMR). This is far more efficent than the first examples=           and it supports both command and interactive modes.       CONFIGURATION SETUPS:O      This file needs to exist on the local node and the remote node if a decnet O      nodename is specified. It requires the user to either specify node access  O      control or for the remote account to be set up for proxy access. TELL can  P      simply reside in sys$login on the remote node, which requires each user to P      have their own copy -or- TELL can be defined as a DECnet object, requiring '      each system to have only one copy.      L      To install TELL as a network object the system manager should enter the      following commands:    DECnet/IV      $ MCR NCPJ      NCP> DEFINE OBJECT TELL NUMBER 0 FILE SYS$MANAGER:TELL.COM PROXY BOTH      NCP> SET OBJECT TELL ALL       NCP> EXIT      $
    DECnet/OSI :      $@sys$startup:net$configure application_add tell "" -G      "{name=tell}||sys$manager:tell.com|true|true|true|true|true||||1"    P     If TELL is not installed as a network object then by default no other setupsP     are required. However if the DECnet object task has been modified to disableM     proxy access then tell will fail. In this case the system manager should  >     enter the following ncp command or equivalent ncl command.      $ MCR NCP'      NCP> DEFINE OBJECT TASK PROXY BOTH       NCP> SET OBJECT TASK ALL       NCP> EXIT      $  I      PROXY accounts allow one user direct access to another users account 6      without having to specify username and password. 	    DECNET O      The system manager can set up proxy account access from within AUTHORIZE.        Example:  $ MCR AUTHORIZE> ?                UAF> ADD/PROXY MVAX::KINGSMILL KINGSMILL/DEFAULT 4                UAF> ADD/PROXY MVAX::OLSENK KINGSMILL                UAF> EXIT	    TCPIP: K      To prevent the need to use passwords on the RSH command proxies can be I      set up to authorize remote user access. To set up remote user access L      on a UNIX machine, or TCPWARE/MULTINET under VMS you specify the remoteJ      node and username in the .rhosts file which resides in the users home=      directory. With UCX you use the "UCX> ADD PROXY command" "       Example:  [TCPWARE/MULTINET])                  $type sys$login:.rhosts                    mvax kingsmill                   mvax olsenk                  $                [UNIX]                   #more .rhosts                    mvax kingsmill                   mvax olsenk                [UCX]I                  UCX> ADD PROXY KINGSMILL/HOST=MVAX/REMOTE_USER=KINGSMILL F                  UCX> ADD PROXY KINGSMILL/HOST=MVAX/REMOTE_USER=OLSENK  G      This examples allows remote user KINGSMILL and OLSENK on node MVAX H      into the local KINGSMILL account. The default switch enables you to:      specify just the nodename when addressing this node:-        eg. $ DIRECTORY TVAX:: E      If Default access is not specified then you need to specify the  6      nodename and username when addressing this node:-(        eg. $ DIRECTORY TVAX"KINGSMILL"::D      If you do not have proxy access then you need to specify the   D      nodename, username and password when addressing a remote node:-1        eg. $ DIRECTORY TVAX"KINGSMILL password"::   L      The following logicals can be used to alter the default TELL behaviour.=      TELL_INHIBIT_SUMMARY to disable the statistics printout. K      SYS$SCRATCH - temporary files are written to sys$scratch. If you don't M        want the temporary files written to sys$login then define sys$scratch.       TROUBLESHOOTING: B      The following logicals can be used to aid in troubleshooting.J      TELL_VERBOSE to display the progress of both local and remote events.M        This can also be enabled by setting the version prefix from "V" to "X" /      TELL_VERIFY to turn on verify and verbose. F      Netserver.log on the remote node may also aid in troubleshooting.I      TELL_'pid'_*.TMP temporary file on the remote node shows the created 8        command file if detached qualifier was specified.M      TELL_'pid'_*.LOG temporary file on on the remote node showing the output         from tell_'pid'_*.tmp  