CORBA 2.6 Administration Guide

Differences Between Using Scripts and Using the PATHCOM Interface

Scripts enable you to start or stop an entire configuration by executing a single command. Thus, if you need to

change the global parameters in your TS/MP configuration, you might edit them in the nsdstart file and then

execute the script. (If your NonStop CORBA system is running, you must execute the nsdstop script before

restarting the system with the nsdstart script.) The nsdstart script includes PATHCOM commands that

refer to server classes (server class is the TS/MP term for server pool). However, if you need to restart a TS/MP

configuration whose global configuration parameters have not changed, you can use PATHCOM, the interface to

the PATHMON process. Similarly, if you need to change the attributes of a single server pool or server process,

you do not need to shut down the entire TS/MP environment. You can modify one or more server processes more

efficiently by using the PATHCOM interface, as described in Using the PATHCOM Interface to Maintain TS/MP

Processes.

Customizing the nsdstart Script

By default, the configure script starts the following processes:

Servers Started (1 each) Default Process Names Process Priority

BSD System assigned 150

LSD System assigned 150

ILSD System assigned 150

Comm Server $ZNCA 150

Event Service System assigned 160

Naming Service $ZND0 170

Object Transaction Service $ZNO0 150

Interface Repository Daemon $ZNDI 160

OTS XID (if OTS static servers are greater than one) $ZNXI 150

You might want to customize the nsdstart script to your needs. You can:

Changing the process priority●

Changing the CPU in which a server runs●

Enabling tracing output for a server●

Adding a Comm Server process●

Removing 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