TS/MP System Management Manual (H06.05+, J06.03+)
Starting and Stopping a PATHMON Environment
HP NonStop TS/MP System Management Manual—541819-007
2-14
Shutting Down a PATHMON Environment
You can choose from these three options: ORDERLY, ABORT, and IMMEDIATE.
Each option provides a different level of shutdown, as described in Table 2-1 and in the
subsections that follow.
In an environment that includes the NonStop TS/MP product, the PATHMON process
automatically stops SERVER processes under its control, and then the PATHMON
process itself.
In an environment that includes both the NonStop TS/MP product and the
Pathway/iTS product, the PATHMON process automatically stops objects in this order:
TERM objects, TCP objects, SERVER processes under its control, and finally the
PATHMON process itself.
Once you specify a SHUTDOWN2 command:
•
All TCP objects begin shutdown (shutting down TERM objects and then
themselves) in parallel.
•
New work is disallowed. For example, all ADD, ALTER, and DELETE commands
are invalid. (For a complete list of commands that are disabled during shutdown,
see Section 11, PATHMON Environment Control Commands.)
•
The PATHMON process logs the start and completion of SHUTDOWN2; it does not
log status messages during shutdown.
(The PATHMON process supports two shutdown commands: SHUTDOWN and
SHUTDOWN2. It is recommended you use the newer, SHUTDOWN2 command for a
faster, more reliable shutdown operation. For compatibility reasons, however, the
SHUTDOWN command is still available. (For more information, see SHUTDOWN
Command (Old).)
Note. This manual provides information specific to commands dealing with objects managed
through the NonStop TS/MP product. PATHCOM commands dealing with requester objects,
such as TCP, TERM, and PROGRAM objects, which are controlled through the Pathway/iTS
product, are described in Pathway/iTS System Management Manual.
Note. For shutting down the PATHMON environment in TS/MP 2.3 or later version, PDMCOM
or PATHCOM can be used. However, it is recommended to use PDMCOM (instead of
PATHCOM) because it can communicate with multiple PATHMONs simultaneously. For more
information on PDMCOM, see the TS/MP Release Supplement
.










