CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.3+)

Remove a Comm Server process●
Manage a NSots transaction manager in a process pool●
To change the script:
Give write permission to the script file nsdstart by using the chmod command.1.
Edit the script, making the desired changes. You can use the vi editor under OSS.2.
Save the changes.3.
Changing the Process Priority
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
2.
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)
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).
2.
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
1.
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
2.