Expand Configuration and Management Manual (H06.21+, J06.10+)

Managing the Network
Expand Configuration and Management Manual — 529522-013
18 - 4
Gaining Access to Remote Nodes
WHO Command
You can check your saved defaults using the WHO command, which shows you when
the current node, volume, or subvolume is different from your saved default.
In this example, the local node is \MEL and the current node is a remote node named
\STU.
Gaining Access to Remote Nodes
When Integrity NonStop NS-series servers form a network using the Expand
subsystem, access to a file can be restricted to users on the local node where the file
resides, or access can be allowed for users on any node in the network.
If a file is available only to local users, you must be logged onto the local node to
access it. To log onto a node other than the one where your current TACL process is
running, you must first start a remote TACL process on that node.
Starting and Quitting a Remote TACL Process
To start a TACL process on a remote node, enter a command that specifies the node,
followed by a period and the TACL program file name. For example, if your local node
Note. Changing the current default node does not log you onto the other node. To log onto a
node other than the one where your current TACL process is running, you must first start a
remote TACL process on that node. Logging on to a remote node is described in
Starting and
Quitting a Remote TACL Process on page 18-4.
15> WHO
Home terminal: $Stein
TACL process: \MEL.$Z103
Primary CPU: 4 (Cyclone) Backup CPU: 5 (TXP)
Default Segment File: $GERT.#6539
Pages allocated: 8 Pages Maximum: 1024
Bytes Used: 13364 (0%) Bytes Maximum: 1024
Current volume: $GERT.STEIN Current system: \STU
Saved volume: $WELL.RHALL
Userid: 6,66 Username: SUPPORT.STEIN Security: “NUNU”
Note. Safeguard can secure a file so that only specific individuals can access that file. For
more information on the Safeguard, see the Safeguard Administrator’s Manual.
Note. Before you can start a TACL process on any remote node, you must be established as a
user on
that node and have the same user ID and user name on both the local and remote
nodes. You must also have remote passwords set up between your local node and the remote
node. Establishing global user IDs and remote passwords is described in
Setting Up Network
Security on page 18-7.