TS/MP System Management Manual (H06.05+, J06.03+)

Starting and Stopping SERVER Objects
HP NonStop TS/MP System Management Manual—541819-007
4-5
Stopping SERVER Objects
server classes are in a FREEZE-PENDING state and the STOP command will not
work.) This command stops all instances of a server in server class CLASS-1:
= STOP SERVER CLASS-1
To stop all servers in your PATHMON configuration, first run:
= FREEZE SERVER *
Once the server classes are frozen, run this command:
= STOP SERVER *
After this, if the WAIT user option is specified, PATHMON waits until the WAIT time is
over. The PATHMON process then stops these servers using the Guardian procedure
call Process_Stop_.
When you enter a request to stop a server class:
1. The PATHMON process notifies all link managers, such as LINKMON processes or
ACS subsystem processes and TCPs as well as all external TCPs, to delink from
the server class.
2. The link managers 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, ACS subysystem
processes, or TCP, the PATHMON process calls the Guardian OPEN/CLOSE
procedure to try and trigger the server class to terminate.
5. The PATHMON performs required clean up 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.
To restart a stopped server process, you must first thaw the server process, then issue
the START command as shown in this example:
= THAW SERVER *
= START SERVER *
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 an OSS
server runs another process, the executed process is outside the PATHMON environment.
When the PATHMON process stops the OSS server, the executed process may become an
“orphan” process.