7 TELL, UTILITIES, Issues DCL commands on remote machines ? 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. N Nodename can also be a symbol and the double colon (::) after the nodename is optional. 2 "0" can be used to specify the local nodename.H If you do not have proxy access then you can specify access control 9 information as part of the nodename specification. A You can force a routing path by specifiy nodename of the from nodename::nodename::N If two or more nodenames are specified then on completion TELL displays a K summary listing of unreachable nodes. This feature can be disabled by , defining the logical name as follows:-6 $ DEFINE/PROCESS/NOLOG TELL_INHIBIT_SUMMARY TRUE 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. COMMAND MODE: H Here the DCL commands are specified in P2 to P8 and are separated I by a vertical bar "|". Quotes are optional and are only required to ( reduce the number of P parameters. 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 SHOW ERROR 5 This command relies on proxy access to 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. + $ TELL MVAX,TVAX "SHOW ERROR"|"SHOW NET" K this command will do both a show error and a show net on both MVAX and TVAX. 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:H TELL.COM needs to exist on both the local and remote nodes and requiresJ the user to either specify node access control or for the remote account J to be set up for proxy access. TELL can simply reside in sys$login on theG remote node, which requires each user to have their own copy -or- TELL K can be defined as a DECnet object, requiring each system to have only one copy. H To install TELL as a network object the system manager should enter the following commands: $ MCR NCP G NCP> DEFINE OBJECT TELL NUMBER 0 FILE SYS$MANAGER:TELL.COM PROXY BOTH NCP> SET OBJECT TELL ALL NCP> EXIT $ M If TELL is not installed as a network object then by default no other setups M are required. However if the DECnet object task has been modified to disable J proxy access then tell will fail. In this case the system manager should enter the following commands: $ MCR NCP $ NCP> DEFINE OBJECT TASK PROXY BOTH NCP> SET OBJECT TASK ALL NCP> EXIT $ E PROXY accounts allow one user direct access to another users account E without having to specify username and password. The system manager 9 can set up proxy account access from within AUTHORIZE. Example: $ MCR AUTHORIZE>< UAF> ADD/PROXY MVAX::KINGSMILL KINGSMILL/DEFAULT1 UAF> ADD/PROXY MVAX::OLSENK KINGSMILL UAF> EXIT
$ D This examples allows remote user KINGSMILL and OLSENK on node MVAXE into the local KINGSMILL account. The default switch enables you to 7 specify just the nodename when addressing this node:- eg. $ DIRECTORY TVAX::B If Default access is not specified then you need to specify the 3 nodename and username when addressing this node:- % eg. $ DIRECTORY TVAX"KINGSMILL":: > If you do not have proxy access then you need to specify theA nodename, username and password when addressing a remote node:- . eg. $ DIRECTORY TVAX"KINGSMILL password":: I The following logicals can be used to alter the default TELL behaviour. : TELL_INHIBIT_SUMMARY to disable the statistics printout. TROUBLESHOOTING: @ The following logicals can be used to aid in troubleshooting.H TELL_VERBOSE to display the progress of both local and remote events.K This can also be enabled by setting the version prefix from "V" to "X" - TELL_VERIFY to turn on verify and verbose. D NETSERVER.LOG on the remote node may also aid in troubleshooting.F TELL_'pid'*.COM temporary file on the remote node shows the created6 command file if detached qualifier was specified.C TELL.LOG temporary file on on the remote node showing the output from tell_'pid'.com
