Pathway/XM System Management Manual

Managing Servers
Compaq NonStop™ Pathway/XM System Management Manual—426761-001
9-10
Stopping Server Classes
Stopping Server Classes
Before you can stop a server class with the STOP SERVER command, you must disable
all communication from LINKMON processes and TCPs to the server by using the
FREEZE SERVER command.
For example, the following command freezes all server processes in the server class
CLASS-1:
>> FREEZE SERVER CLASS-1
After the server class is frozen, you can stop the server process by stopping the server
class to which it belongs. (Note that there is a short period of time during which the
server classes are in a FREEZE-PENDING state and the STOP command will not
work.) The following command stops all instances of a server in server class CLASS-1:
>> STOP SERVER CLASS-1
To stop all servers in the server classes in group XYZ, first execute the following:
>> FREEZE SERVER GROUP ABC
Once the server classes are frozen, execute the following command:
>> STOP SERVER GROUP ABC
When you enter a request to stop a server class, the following actions take place:
1. All PATHMON processes associated with the server class notify all LINKMON
processes and TCPs to delink from the server class.
2. The LINKMON processes and TCPs close all server processes.
3. The server processes respond by preparing for termination and then stopping
themselves.
4. For any server class that has never been linked to a LINKMON or TCP, the
PATHMON process calls the Guardian OPEN/CLOSE procedure to cause the server
processes to stop themselves.
5. The PATHMON performs required cleanup operations based on stop messages it
receives.
6. While the PATHMON process waits to be notified that all processes are stopped, it
returns a message indicating that close commands are still pending for the running
processes. When the close requests are complete, the server class goes to the
stopped state.
Note. A PATHMON process stops only servers under its control. If a server process starts
another process not under the control of a PATHMON process, the second process is not
stopped when the PATHMON process stops the first server process. For example, if a server
creates another process, the created process is outside the PATHMON environment. When
the PATHMON process stops the server, the created process can become an “orphan”
process.