Network Names [ Using NS3000/XL Network Services ] MPE/iX 5.0 Documentation
Using NS3000/XL Network Services
Network Names
When each computer system is configured as part of an NS3000/XL network,
it is assigned a unique node name. You use this node name to log on to
each computer system.
You can log on to a specific session within a node by employing a
user-defined name known as an environment ID. A default environment ID
is the node name itself. In order to designate a remote file or device,
you must include its remote environment ID in an extended file
designator, for example, FILEX:ENV1. You can maintain multiple remote
sessions on a single node by specifying a new environment ID for each
new session.
Figure 1-2 shows that a user on node TOM has four remote environments on
node HARRY, one of which was given the default name HARRY.
Figure 1-2. Opening Several Remote NS3000/XL Sessions
A node name or an environment ID may optionally be qualified with a
domain and organization. The domain and organization are arbitrary
labels that the network manager specifies when configuring each node into
the network. For example, in the name EMPIRE.DCL.IND, the node name is
EMPIRE, the domain is DCL, and the organization is IND.
You can find full details on node names, environment IDs, and remote
file designations in the chapters on "Virtual Terminal" and "Remote File
Access" in this manual. For convenient reference, the syntax for node
names and environment IDs is given here.
node[.domain[.organization]]
envname[.domain[.organization]]
If you do not qualify the node or envname in a user-level command or
intrinsic, the configured domain and organization of the local node are
assumed by default. Each node, envname, domain, or organization
specification can be up to 16 characters long, and can include
alphanumeric characters, the underscore ( _ ), and the hyphen (-). The
first character of each node, envname, domain, or organization name
must be alphabetic.
MPE/iX 5.0 Documentation