CORBA 2.6.1 Administration Guide

If the default Comm Server's name is ZNCA, a second Comm Server's name must be ZNCB. There are two handy predefined Comm
Server name variables available in the
nsdstart script, COM_SERVER1 and COM_SERVER2.
2. The Comm Server entity name must have the following form:
csname@comm_server
where csname is the argument passed to processes in the associated Parallel Library TCP/IP Comm Server SERVERCLASS.
3. The Comm Server entity must specify:
a parallel library TCP/IP process for the tcp_process entry
a host_name entry that corresponds to the tcp_process entry
a unique value for the port_number entry
Nonconstraint
Processes from different Parallel Library TCP/IP SERVERCLASS objects may be configured in the same CPU.
Using the PATHCOM Interface to Maintain TS/MP Processes
You configure NonStop CORBA system server processes by using the services of TS/MP. Processes defined through TS/MP run under the
control of a TS/MP monitor, the PATHMON process.
PATHCOM provides the interface to the PATHMON process.
You begin a PATHCOM process from the TACL prompt in the Guardian environment. For detailed instructions about starting these processes,
and for complete syntax and descriptions for all PATHCOM commands, refer to the NonStop TS/MP System Management Manual.
This subsection gives an overview of how you can use PATHCOM to alter global and process-specific configuration parameters in the TS/MP
configuration.
Maintenance and fine-tuning tasks for NonStop CORBA system and application processes include the following:
Monitoring status and performance by using the PATHCOM interface to display information about the TS/MP environment and the server
pools.
Modifying global parameters based on changing requirements.
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:
1. Start a PATHCOM process to communicate with the running PATHMON process.
2. Stop and restart a NonStop CORBA process.
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