Pathway/iTS System Management Manual (G06.24+)

Terminal Control Process (TCP) Commands
HP NonStop Pathway/iTS System Management Manual—426748-002
9-42
STOP TCP Command
Consideration
When a TCP from one PATHMON environment requests a link to a server class in a
different PATHMON environment, the PATHMON process controlling the server class
considers the requesting TCP to be an external process. However, a STATUS TCP
command issued to the local PATHMON process (the one controlling the server class)
displays the names of both the external and local TCPs. The external TCP name is
generated by the PATHMON process at the time of the status request.
Example
The following example commands request status information for various TCPs using
different options:
STATUS TCP-1
STATUS/OUT STATFLE/TCP (TCP-2,TCP-3)
STATUS TCP TCP-4,DETAIL
STATUS TCP *, STATE RUNNING
STATUS/OUT STATFLE/TCP *
STATUS TCP E\CUPRTNO.$TCP1
STATUS TCP *, STATE NOT PENDING
STOP TCP Command
Use the STOP TCP command to stop a TCP. This command does not stop an external
TCP (a TCP that is controlled by another PATHMON process and is therefore outside
this PATHMON environment) that is linked to a local server process.
tcp-name
specifies the name of one or more previously defined and added TCPs. tcp-
name can be either a single TCP name or several TCP names separated by
commas and enclosed in parentheses.
WAIT
directs the PATHMON process to retry the command every second if the STOP
command is rejected with an invalid TCP-state error. You can abort the WAIT
option by pressing the Break key.
STOP { [ TCP ] tcp-name [ , WAIT ] }
{ [ TCP ] ( tcp-name [ , tcp-name ]... ) [ , WAIT ] }
{ TCP * [ , option [ , option ] ] }
option is:
STATE state-type
WAIT