TS/MP System Management Manual (H06.05+, J06.03+)

SERVER Commands
HP NonStop TS/MP System Management Manual—541819-007
12-46
STOP SERVER Command
permits you to obtain original functionality of the STOP command after attempting
the new style OPEN/CLOSE method and waiting for the specified < scwait> time.
WAIT number
specifies the time after which the never-linked, non associative server processes of
the specified server class are to be stopped. This is meant for servers, which do
not follow the Guardian OPEN/CLOSE logic.
SERVER *
stops all servers in all server classes that are in the FROZEN state. The
PATHMON process does not report on servers it cannot stop.
Considerations
•
A STOP SERVER command completes with a REQUEST PENDING message
when all link managers have not yet returned their links to a stopped or abended
server, or when a server that no longer has links to a link manager has not
stopped.
•
A server should be programmed to stop itself (by calling the Guardian STOP
procedure) after receiving a CLOSE message from a link manager. But the never-
linked, non associative servers that do not follow Guardian OPEN/CLOSE logic,
will continue to run. If the WAIT option is specified, the PATHMON process stops
all the never-linked, non associative servers, using Guardian call Process_Stop_,
after the specified WAIT time. PATHMON cannot distinguish between the servers
that follow Guardian OPEN/CLOSE logic and that do not follow it. So, if WAIT time
is specified for never-linked, non associative servers that follow Guardian
OPEN/CLOSE logic, the WAIT time should be such that it will allow the servers to
do the cleanup. If WAIT time is 0 secs, all the servers stop immediately. In case of
duplicate STOP SERVER commands specified for the same server class with a
different WAIT time, the never-linked, non associative servers of the specified
server-class, will stop at the earliest timeout among the specified WAIT values.
•
If an OSS server process starts another process not under the PATHMON
process’s control, the second process is not stopped when the PATHMON process
stops the server class. For example, if an OSS server process runs another
process, the executed process is outside the Pathway environment. When the
PATHMON process stops the OSS server class, the executed process may
become an orphan process.
•
For information on stopping associative servers, see Maintaining Associative
Server Processes on page 5-33.
Note. If the <scwait> option from PATHCOM is specified with STOP SERVER
command, it will try to stop the server even if the server is in hung state.PATHCOM will
wait for the specified <scwait> time and will return a command prompt after timeout.