NET/MASTER Management Services (MS) Operator's Guide

Logging On to Multiple Remote Systems
Communicating With Remote Systems
8–6 106379 Tandem Computers Incorporated
If a link is reset (see the discussion on “Resetting a Link,” later in this section), you are
notified that the connection will not be restarted. You must log on again if a new
connection is required.
Automatically Logging On
to a Remote System
If you send a ROUTE command to a remote system without explicitly logging on to it,
the ROUTE command logs you on automatically with your local password, by issuing
an implicit SIGNON command. This means that your password at both the local and
remote system must be the same.
Caution If you have a password with lowercase letters at your local NonStop NET/MASTER MS system, you
cannot implicitly log on to a remote SOLVE management services or NetView system because the
SOLVE management services and NetView systems require uppercase passwords.
If the link is not active, the ROUTE command is rejected. Using the SIGNON
command frees you from having to wait for the link to become active.
Note If you implicitly log on to a remote system with the ROUTE command, you cannot override the default
message identifier, color, or highlighting attributes associated with the link.
Logging On to Multiple
Remote Systems
You can log on to multiple remote systems from each OCS window you own.
If you are always required to log on to a number of remote systems, you should
consider including the necessary SIGNON commands in the NCL procedure that is
automatically executed when you enter OCS (the value in the Initial OCS field in your
user ID definition record).
Sending Commands
Directly to a Remote
System
To route commands to a remote NonStop NET/MASTER MS system, SOLVE
management services system, or NetView system, issue a ROUTE linkname command,
followed by the command text to be executed at the remote system. For example:
ROUTE BOSTON SHOW USERS
ROUTE NM11 OPSYS STOP ORL-SNAX, SUBONLY
Note If you are entering commands from the Command Entry facility, enter the name of the link connecting the
remote system in the SYSTEM field. It is not necessary to issue the ROUTE command from Command
Entry unless you are routing a command through one or more intermediate links when you need to send a
ROUTE command to an intermediate system.
The contents of the command string are not validated before transmission; invalid
commands are rejected by the remote system. You can concatenate multiple
commands if command concatenation is enabled on the remote system.