Pathway/XM System Management Manual

Managing a Pathway/XM Environment
Compaq NonStop™ Pathway/XM System Management Manual—426761-001
7-16
Displaying Information About a Pathway/XM
Environment
The following command starts the server class named QUERIES:
>> START SERVER QUERIES
The following command starts all server classes in the Pathway/XM environment:
>> START SERVER *
When the START SERVER command is issued, the processes created for each server
class depend on the server-class type. For distributed server classes, one link control
service (LCS) process is created for each PATHMON process associated with the server
class, and one server process is created. (If NUMSTATIC is 0, nothing is started
automatically.) For direct and replicated server classes, the number of server processes
created is determined by the value of the NUMSTATIC attribute for the server class.
If you do not start a server class explicitly, it is started implicitly when a send request is
received for the server class. However, direct and replicated server classes do not
receive CPU assignments from the PB processes and thus do not participate in
Pathway/XM load balancing. (Distributed server classes always receive CPU
assignments from the PB processes, and therefore, do participate in load balancing.) For
this reason, it is recommended that you start all server classes explicitly.
For details about starting server classes, refer to Starting Server Classes
on page 9-1.
Displaying Information About a Pathway/XM
Environment
The SuperCTL file and the individual PATHCTL files associated with the PATHMON
processes maintain information about object configurations, object status, and operation
statistics. You can display this information using the following commands:
•
INFO, which shows the current configuration of a Pathway/XM environment and its
objects
•
STATUS, which indicates the state (such as running or suspended) of objects in the
Pathway/XM environment
•
STATS, which provides statistics for resources associated with NODE, TCP,
TERM, and SERVER objects
For all of these commands, you can direct the display output to a text file by using the
OUT command before issuing the INFO, STATUS, or STATS command. For example,
the following command directs all subsequent PXMCOM output to a text file named
$OPS.PXM.JUNE95:
>> OUT $OPS.PXM.JUNE95
This subsection describes in detail the global information displayed by using these
commands for the Pathway/XM environment, the NODE objects, and the PATHMON
processes. For descriptions of the information displayed for objects related to
requesters, refer to Displaying Information About Client and Requester Objects on
page 8-7. For descriptions of the information displayed for objects related to servers,
refer to Displaying Information About Servers
on page 9-6.