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

SERVER Commands
NonStop TS/MP System Management Manual—541819-001
12-45
STOP SERVER Command
This commands display status information about the specified frozen server classes,
and include various options:
STATUS /OUT STATFLE/SERVER CLASS-1,FREEZE
STATUS SERVER CLASS-2,FREEZE
STATUS CLASS-3,FREEZE
This command displays the names of terminals that have not yet accepted the freeze
condition for all server classes:
STATUS SERVER *, FREEZE
This command displays the names of all server classes that are in a FROZEN or
FREEZE-PENDING state:
STATUS FREEZE
STOP SERVER Command
Use the STOP SERVER command to make all link managers, such as LINKMON
processes and TCPs, return their links to a server class. The server class must be
frozen before you issue this command.
server-class
specifies the name of a previously defined and added server class.
SERVER *
stops all servers in all server classes that are in the FROZEN state. The
PATHMON process does not report on the servers that 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. The
PATHMON process calls the STOP procedure for servers that are running, are not
associative, and have never been linked.
•
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 executes another
process, the executed process is outside the Pathway environment. When the
STOP { [ SERVER ] server-class }
{ [ SERVER ] ( server-class [ , server-class ]... ) }
{ SERVER * }