CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.7+)

set server env NSDOM_CFG_DBM=$NSDOM_CFG_DBM

set server define =_SRL_01, class map, file $NSD_SRL_SUBVOL.NSDSRL

set server createdelay 0 secs

set server deletedelay 0 secs

set server TIMEOUT 0 SECS

set server MAXLINKS 16

set server LINKDEPTH 1

+ set server maxservers 3

+ set server numstatic 3

- [set server process \$$COM_SERVER1

* set server arglist "$COM_SERVER1"

* set server process \$cs1 (CPUs 1)

* set server process \$cs2 (CPUs 2)

* set server process \$cs3 (CPUs 3)

set server AUTORESTART 10

add server CS

start server CS

Configuring Additional Parallel Library TCP/IP Comm Servers

Additional Parallel Library TCP/IP Comm Servers can be configured by adding a Comm Server SERVERCLASS

under Pathway, and adding a Comm Server entity in the config database.

To add a second Comm Server SERVERCLASS, duplicate the entire section of nsdstart that configures the

default Comm Server. Also, make sure the MAXSERVERCLASSES attribute of the PATHMON configuration

accounts for this extra SERVERCLASS.

The following names must be unique:

SERVERCLASS name. The default Comm Server SERVERCLASS name is CS. A second Parallel Library

TCP/IP Comm Server SERVERCLASS might have the name CS2. Using the example above as a

reference, the last two lines would be:

add server CS2

start server CS2

The SERVERCLASS name has no constraints beyond those required by TS/MP.

Process names. In the above example, we used the process names $cs1, $cs2, and $cs3. A second Comm

Server SERVERCLASS might use the following statements:

* set server process \$csb1 (CPUs 1)

* set server process \$csb2 (CPUs 2)

* set server process \$csb3 (CPUs 3)

Note that the '$' must be escaped with a '\' because nsdstart is a PATHCOM script embedded in an OSS

shell script.

Constraints