CORBA 2.3.3 Administration Guide (NonStop CORBA 2.3.3+)

$Z02Y RUNNING 0 0
SERVER #RUNNING ERROR INFO
NS 1
PROCESS STATE ERROR INFO #LINKS WEIGHT
$AND0 RUNNING 5 15
SERVER #RUNNING ERROR INFO
OTSTM 1 1034
PROCESS STATE ERROR INFO #LINKS WEIGHT
$ANO0 RUNNING 9 17
=
Using the STATUS SERVER command can help you determine whether links are evenly allocated and balanced
among server processes in your NonStop CORBA application environment.
The #LINKS field shows the total number of current links to a given server process. The WEIGHT field indicates
how heavily the server process is used relative to how heavily other processes in the server pool are used. In the
example above, process $ANO0 has nine links and a weight of 17; thus it is the hardest working process in the
server pool at the moment.
Displaying Statistical Information
To display statistical information about a PATHMON process, type the following PATHCOM command:
= STATS PATHMON
Refer to the PATHMON manual for details about interpreting the output from this command.
Modifying Global Parameters Based on Changing Requirements
As your application needs change, requirements for your TS/MP configuration will change. If your application
grows, adjustments might be necessary to satisfy your transaction throughput and response-time requirements and
to update or expand the system to provide needed resources.
For example, you might need to increase the maximum number of application-server processes to satisfy a
growing demand for links to servers. In response to your changing requirements, you might need to specify not
just new attributes for your server pools but also new global limits and parameters for the TS/MP environment.
Caution
You cannot specify new global parameters while the PATHMON environment is running. You must first shut
down the entire configuration before you can install the new parameters.
Because a system shutdown can result in considerable downtime if your application is complex, when you first
configure your environment you should specify global limits that are high enough to allow for growth.
If you discover that you must reconfigure the global parameters, thereby forcing a shutdown, you must respecify
all limits, not just the ones you are changing. For this reason, you might find it more efficient to change global