CORBA 2.6 Administration Guide

Locate the section of the script that defines the server you want to change.1.

Change the process priority number in the line that looks like this:

set server pri 150

Changing the CPU in Which a Server Runs

Locate the section of the script that defines the server you want to change.1.

Add a line similar to the following (which specifies that the servers should run in CPUs 1 and 2):

set server cpus (1,2)

Enabling Trace Output for a Server

Locate the section in the script for the server you want to change.1.

Find the lines that enable tracing. These lines are initially commented out (the left bracket comment

character "[" appears in front of each line).

Remove the comment character from each trace line.3.

After you restart the server, trace output appears in the log file.4.

For log file information, see Appendix D.

Adding a Comm Server Process

Assume that the currently running NonStop CORBA system includes a Comm Server named $ZNCA and that you

want to add a second one named $ZNCB.

Note:

The examples in this section assume that you have set MY_PREFIX in the env.sh script equal to

the value Z.

If NonStop CORBA system processes are running, stop them by executing the nsdstop script from OSS:

> nsdstop

Locate the Comm Server specification section in the nsdstart script. The following example shows the

section of nsdstart that configures the Comm Server process:

Configuring a Comm Server

#...

COM_SERVER1="$MY_PREFIX"NCA

COM_SERVER2="$MY_PREFIX"NCB

#...

set server maxservers 1

set server numstatic 1

set server process \$$COM_SERVER1

set server AUTORESTART 10

add server CS

start server CS