Configuring Logon Information |
 |
NetCI establishes multiple remote sessions on one or more
nodes when executing a particular command or running a program.
Before remote logon sessions can be established, system and logon
information for each node must be stored in the NetCI internal data
structure.
To configure each node, use the following commands:
NEWNODE to configure
each node and its logon sessions.
ALTNODE to change the node's
logon information.
PURGENODE to delete a node from
configuration
You can then use the SHOWNODE command to
list all the nodes and logon sessions that you configured, and to
check whether you correctly changed a node's logon information
or deleted a node. Refer to the commands on the following pages
for more specific details.
Each node in the network is identified by its NS 3000
node name. Any node may be added to the NetCI configuration and
identified in NetCI by a unique NetCI node name. The NetCI node
name may be the NS 3000 node name or another NetCI name
you want to assign to the node. Each NetCI node name is associated
with a logon session on a node. You can have several logon sessions
established on one node but each session must have an individual
NetCI node name.
Using our sample LAN, we will configure all the nodes in NET3
from one location, node K.
In order to configure node K,
use the NEWNODE command:
NetCI>NEWNODE K OPERATOR.SYS/NET3K |
NetCI will now have in its configuration a node called K.
The logon session for K will be
OPERATOR.SYS/NET3K.
For our example, we will configure the remaining nodes on
the LAN in NET3 using their NS 3000
node names:
NetCI>NEWNODE Y OPERATOR.SYS/NET3Y |
NetCI>NEWNODE I OPERATOR.SYS/NET3I |
NetCI>NEWNODE J OPERATOR.SYS/NET3J |
NetCI>NEWNODE L OPERATOR.SYS/NET3L |
NetCI>NEWNODE H OPERATOR.SYS/NET3H |
You can reassign each node a unique NetCI name instead of
using the NS 3000 node name. For example, you can assign
a session on node Y the NetCI name,
BURGUNDY. NetCI will then recognize
the logon session (OPERATOR.SYS)
on node Y as BURGUNDY.
To assign a unique NetCI name to a node and logon session, you use
the NEWNODE command with the ;dsline= NS nodename
option. For example, you enter
NetCI>NEWNODE BURGUNDY OPERATOR.SYS/NET3Y;DSLINE=Y |
After configuring your network, you may then assign the nodes
with their associated sessions to different lists and assign an
identifier to each list. If four nodes are assigned to a list, a
session will be initiated on each of the four nodes when the command
is executed on each node. Refer to "Configuring for Command
Broadcast" for more information.
When you reassign an NS node a NetCI name, you need to only
specify the NetCI name instead of the fully-qualified NS node name
to perform an operation on the node. For example, to assign a NetCI
name, you enter
NetCI>NEWNODE PORT OPERATOR.SYS/NET1A,;DSLINE=A.NET1.BND |
to configure node A with its logon session in NET1 as PORT.
If the NS 3000 node name is not a unique node name in the
internetwork, the node name following ;dsline=NS nodename
option must be a fully-qualified node name, nodename.domain.organization.
Whenever you want to establish a session on node A in NET1,
you simply need to specify PORT
instead of the fully-qualified NS 3000 node name.
![[Sample Internetwork]](img/gfx18.gif)