page 2  (20 pages)
to previous section1
3to next section

Table 1: Nexus Availability

Computer Operating System Other Requirements

HP HPUX 9.x DCE threads
IBM RS6000 AIX 3.2.x DCE threads
IBM SP AIX 3.2.x DCE threads
IBM RS6000 AIX 4.1.x
Intel Paragon OSF/1
SGI IRIX 5.x Quick Threads
Sun SunOS 4.1.x FSU pthreads
Sun Solaris 2.x

contexts. The modules encapsulate behavior that is specific to the particular protocol or startup method. However, many of these modules have parameters that the user may wish to modify. Therefore in the following discussion, we will note where parameters are specific to a certain protocol or startup method, or are valid for the core Nexus architecture.

Nexus includes modules for numerous startup methods and protocols. Since different Nexus compilers prefer different methods, be sure to check compiler documentation for language-specific details.

2.1 Specification of resources and parameters

2.1.1 Resource Naming

A node identifier specifies uniquely a Nexus node and is of the following form.

node name#node number

The character string node name identifies a set of one or more resources, while the node number is an integer specifying a specific member of the resource set. The mapping of a node identifier to a physical computing resource does not have to be unique. Nexus is informed via the resource database (x 2.1.3) as to the number nodes that may be created on that resource. When this number exceeds the number of physical resources within the node, node numbers map cyclically to the available number of resources. As a shorthand method, multiple nodes may be referenced using the notation:

node name[#node number][,count]

Below, several node group specifiers are listed along with the associated nodes within that group.

pelican : pelican#0
pelican#0 : pelican#0
pelican#0,3 : pelican#0, pelican#1, pelican#2
pelican,2 : pelican#0, pelican#1
pelican#3,2 : pelican#3, pelican#4