CORBA 2.6 Administration Guide

Adding, removing, or modifying server pools and processes based on performance queues or changing
requirements.
●
Making changes based on performance considerations, including load-balancing issues.●
Using the PATHCOM Interface
The OSS scripts supplied with NonStop CORBA enable you to issue a single command to start (or stop) a TS/MP
configuration. Although these scripts are good for starting and stopping all NonStop CORBA system processes,
they lack the control you need to properly administer a running system.
The nsdstart script causes PATHMON to re-create the entire TS/MP configuration file, a potentially lengthy
process. If your global configuration parameters have not changed, you do not need to re-create this configuration
file.
By using PATHCOM, you can directly administer a PATHMON process without re-creating the existing TS/MP
system configuration.
Starting a PATHMON Process
To issue PATHCOM commands, you must first start a PATHCOM process to communicate with the PATHMON
process that controls your TS/MP environment. Type the following from the TACL prompt:
> PATHCOM $pmon
This command begins a PATHCOM session that uses the PATHMON process names in the $pmon parameter,
for example, $ZNDM. The system responds by returning the PATHCOM prompt:
=
Restarting a Previously Defined TS/MP Configuration
You can use the PATHCOM interface to restart a NonStop CORBA system process. To do so:
Start a PATHCOM process to communicate with the running PATHMON process.1.
Stop and restart a NonStop CORBA process.2.
Consider the following commands:
> PATHMON /NAME $ZNDM, NOWAIT/
> PATHCOM $ZNDM
= FREEZE NS
= STOP NS
= THAW NS
= START NS
Assume you want to restart the naming service processes. These processes are defined in the NS server class. The
freeze and stop commands cause PATHMON to stop the processes. The thaw and start commands restart
the processes.