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

Starting and Stopping a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
2-15
Specifying the ORDERLY Option
Specifying the ORDERLY Option
The ORDERLY option enables work in progress to complete before shutting down.
This command specifies an orderly shutdown:
= SHUTDOWN2, MODE ORDERLY
The ORDERLY option requires the most time to complete the shutdown operation,
because all transactions in progress are allowed to complete before objects (TCP,
TERM, and server objects) involved in the transaction are stopped. For example, a
TERM waiting for I/O to a server class to complete cannot be stopped until the I/O
completes.
Table 2-1. Effects of SHUTDOWN2 Options
ORDERLY ABORT IMMEDIATE
TERM objects Stopped Aborted Aborted
1
SERVER processes Closed Closed Stopped
2
TCPs (local) Stopped—after
stopping all TERM
objects under TCP’s
control and closing
all server processes
Stopped—after
aborting all TERM
objects under TCP’s
control and closing
all server processes
Stopped
2
TCPs (external) and
LINKMON processes
Notified of shutdown
request
3
Notified of shutdown
request
3
Notified of shutdown
request
3
PATHMON process Stopped—if
shutdown completes
without errors
Stopped—if
shutdown completes
without errors
Stopped—if
shutdown completes
without errors
Outstanding work All outstanding work
(
I/O and dialog
activity) is completed
For TCPs and server
classes, outstanding
work (I/O and dialog
activity) is
completed. For
transactions
involving an aborted
TERM, unknown.
4
Unknown
New work Not allowed Not allowed Not allowed
1. Because the TCP was stopped by a Guardian STOP procedure call, the terminals were aborted. Aborting a
TERM object means that transactions are not completed.
2. Indicates a potential Guardian STOP procedure call.
3. Once an external TCP or LINKMON processes notification of an impending PATHMON shutdown, that TCP
or LINKMON process no longer sends data or requests to server classes under the control of the PATHMON
process that is shutting down.
4. If the transaction is protected by the Transaction Management Facility (TMF), TMF aborts the transaction
and resets any data that was changed. If the transaction is not protected by TMF, the effects of the aborted
transaction are unknown.