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

Starting and Stopping a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
2-19
Monitoring Shutdown Status
This are examples of situations in which shutdown cannot complete:
•
An external object (ASSOCIATIVE), such as a server process, cannot be stopped.
•
The network goes down and a locally controlled TCP is running on a remote
system in that network.
To see if objects are still running, you should specify a STATUS PATHWAY command.
If necessary, you can try to stop these objects by specifying a Guardian STOP
command at your TACL prompt.
Stopping the PATHMON Process
If shutdown cannot complete, you can stop the PATHMON primary and backup
processes by issuing this PATHCOM command:
= STOP PATHMON
This command stops the PATHMON primary and backup processes and writes a
termination message to the log file.
When stopping the PATHMON process, you must consider that processes started by
the PATHMON process are no longer under its control and might still be running. You
must find and stop these “orphan” processes. One way to stop orphan processes is to
use a TACL routine. Example 2-2 shows a TACL routine that, for a local system, first
stops all children of a given process ID and then stops the process ID. For more
information on using TACL routines, see the TACL Reference Manual and the TACL
Programming Guide .
Note. The STOP PATHMON command is valid only if you have already issued a
SHUTDOWN2 command.