Pathway/XM System Management Manual

Managing Servers
Compaq NonStop™ Pathway/XM System Management Manual—426761-001
9-9
A System Management Scenario
For the syntax of the STATS SERVER command, refer to STATS SERVER on
page 11-67.
A System Management Scenario
The following scenario illustrates how to use the information provided by the STATUS
SERVER command to detect problems within your server environment and to determine
how to rectify these problems.
You know that users are encountering difficulties with some of their workstation client
applications, which access distributed servers in your Pathway/XM environment. The
applications will not come up. By asking a few questions, you determine that Compaq
NonStop
TM
Remote Server Call/MP (RSC/MP) is running. Investigation on the host
side reveals no telecommunications outages, so the problems must be in the
Pathway/XM environment.
1. You use the STATUS SERVER *, DETAIL command to determine which server
classes are currently running.
2. You notice that no server processes are running in the server class A-NAME-
SERVE. You know that this server class is required for all client applications.
You also know that all other server classes must be suspended before the A-NAME-
SERVE server class can be started.
3. You decide to suspend operation of all server classes, while allowing incoming
transactions to be queued, by using the SUSPEND SERVER * command.
4. You use the STATUS SERVER *, DETAIL command to confirm that all server
processes have stopped.
The STATUS command display reveals that servers in two server classes are still
running, presumably because the server processes are still completing long
transactions. These two server classes are named B-NAME-SERVE and C-NAME-
SERVE.
5. You then issue STATUS SERVER commands for these two server classes, followed
by the STATUS SERVER *, DETAIL command, repeating this command sequence
periodically until all server activity has stopped in all server classes.
6. You use the START SERVER command to start server class A-NAME-SERVE.
7. You use the RESUME SERVER * command to resume processing of transactions
by the other server classes, followed by another STATUS SERVER *, DETAIL
command to confirm that new server processes have started in these server classes
and that the server classes are again processing transactions.
Note. LINKMON processes do not report response-time information or frequency-distribution
information. Only TCPs collect this data.