TCP/IPv6 Configuration and Management Manual (G06.29+, H06.03+, J06.03+)

SCF Reference for NonStop TCP/IPv6
HP NonStop TCP/IPv6 Configuration and Management Manual524523-012
8-194
STOP Command
Considerations
A pound sign (#) precedes the SUBNET name for backward compatibility with
applications that expect this naming convention for SUBNETs. See Supported
Commands and Object Types on page 8-10.
STOP Command
The STOP command terminates the operation of the specified NonStop TCP/IPv6
object. You can stop processes, SUBNETs, and routes. When the operation is
complete, the object(s) is in the STOPPED summary state. If the specified objects are
in use, the STOP command is not completed. If you attempt to stop an object that is in
use or is already in the STOPPED summary state, the NonStop TCP/IPv6 subsystem
returns a warning.
This is a sensitive command.
STOP MON Command for TCP6MAN
The STOP MON command terminates the activity on a given TCP6MON or on all
configured TCP6MONs in a normal, orderly manner. The STOP command cannot be
used if open sockets exist; (use ABORT MON instead). This command does not delete
the MON object from the system configuration database.
Command Syntax
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file.
MON $ZZTCP.#ZPTMn
is the name of the TCP6MON object. If you omit the object name, SCF uses the
assumed object name. You can substitute the wild card (*) for the TCP6MON
name; doing so stops all TCP6MONs. For information about the ASSUME
command, see the SCF Reference Manual for G-Series RVUs or the SCF
Reference Manual for H-Series RVUs.
Examples
To terminate the operation of all TCP6MONs:
SCF> STOP MON $ZZTCP.*
STOP [ /OUT file-spec/ ] MON $ZZTCP.#ZPTMn