CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.3+)

Pathctl File in Use
If the Pathway control file is in use, you see an error similar to this:
$Z1XY: ERROR - *1017* PATHCTL FILE (012)
To remedy this error, define an alternate location for the pathway control file by entering the following command
at the OSS command prompt:
add_define =_DEFAULTS class=DEFAULTS volume=\$VOL.SUBVOL
Substitute the desired volume name for VOL and the desired subvolume name for SUBVOL. After executing this
command, executing the nsdstart script causes the Pathway control file to be created in the specified location.
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 serverclasses (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 System assigned 160
OTS XID (if OTS static servers are greater than one) System assigned 150
You might want to customize the nsdstart script to your needs. You can:
Change the process priority●
Change the CPU in which a server runs●
Enable tracing output for a server●
Add a Comm Server process●