TS/MP 2.5 System Management Manual

Example 1 SHUTDOWN2 Status Display
PATHWAY -- STATE = SHUTTING DOWN (IN PROGRESS) - STARTED 2:11:39
RUNNING
0LINKMONS
1PATHCOMS
0SPI
PENDINGFREEZE FROZENTHAWEDSTOPPEDRUNNING
00112SERVERCLASSES
PENDINGSTOPPEDRUNNING
018SERVERPROCESSES
042TCPS
*
SUSPENDEDPENDINGSTOPPEDRUNNING
0088TERMS
*
PATHWAY - STATE = SHUTTING DOWN (IN PROGRESS) - STARTED 2:11:39
RUNNING
0LINKMONS
1PATHCOMS
0SPI
PENDINGFREEZE FROZENTHAWEDSTOPPEDRUNNING
00130SERVERCLASSES
PENDINGSTOPPEDRUNNING
081SERVERPROCESSES
060TCPS
*
SUSPENDEDPENDINGSTOPPEDRUNNING
00160TERMS
*
*
Defined only if you have the Pathway/iTS product
If Shutdown Cannot Complete
If the PATHMON process encounters an error while shutting down, it terminates the shutdown
operation. PATHCOM returns the reason for the failure. In some cases, you might have to examine
the log file to determine why shutdown did not complete, fix the problem, and reissue the
SHUTDOWN2 command.
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 must specify a STATUS PATHWAY command. If necessary,
you can try to stop these objects by specifying a Guardian STOP command at your TACL prompt.
Shutting Down a PATHMON Environment 47