|
|
|
Using NS 3000/iX Network Services: HP 3000 MPE/iX Computer Systems > Chapter 1 Introduction to NS 3000/iX
Network Names |
|
When each computer system is configured as part of an NS 3000/iX network, it is assigned a unique node name. You use this node name to log on to each computer system. Node names can be in either NS node name syntax or ARPA domain name syntax as explained in the following sections. For people using NS node name syntax, the NS names work the same as in the versions prior to MPE/iX 4.0. Refer to the HP 3000/iX Network Planning and Configuration Guide for instructions on configuring node names (both NS and ARPA domain types) and for configuring aliases. 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 “Opening Several Remote NS 3000/iX Sessions” shows that a user on node TOM has four remote environments on node HARRY, one of which was given the default name HARRY. 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.SJ.CA, the node name is EMPIRE, the domain is SJ, and the organization is CA. 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 NS 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. Following is the syntax for using ARPA domain names within DSLINE and REMOTE commands: label[.label][...] The labels must follow the rules for ARPANET host name. They must start with a letter, end with a letter or digit, and have as interior characters only letters, digits, hyphens (-), or underscores (_). Although underscores are not specified as part of ARPANET syntax, HP allows them for compatibility with the NS-style node names. The first part of each name (the first label) must not exceed 50 characters, and the total length of a domain name may not exceed 50 characters. If you wish to use an ARPA domain name that is greater than 50 characters, you must use the domain name's alias. Refer to the HP 3000/iX Network Planning and Configuration Guide for instructions on configuring aliases. HP recommends using fully qualified names when using ARPA domain name syntax. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
![[Opening Several Remote NS 3000/iX Sessions]](img/gfx2.gif)