TS/MP System Management Manual (G06.24+, H06.03+)

Starting and Stopping SERVER Objects
NonStop TS/MP System Management Manual—541819-001
4-5
Stopping SERVER Objects
1. The PATHMON process notifies all link managers, such as LINKMON 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 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 executes 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.