TCP/IPv6 Configuration and Management Manual (G06.24+)

SCF Reference for NonStop TCP/IPv6
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-008
8-4
MONITOR Object Type
MONITOR Object Type
The MONITOR object (TCP6MON) provides the NonStop TCP/IPv6 environment in a
processor. Only one TCP6MON can exist per processor. TCP6MON has the reserved
name of $ZPTMn where n is the processor number (hexadecimal) where TCP6MON
resides.
null Object Type
The null object is not an actual object type. The term “null” represents the lack of a
specified object. Any SCF command that supports the null object type is issued
without the specification of an object type. Commands support the null object type if
an object type is irrelevant (as for the VERSION command), or if they refer to a
collection of objects (as for with the NAMES command).
To issue an SCF command using the null object, specify the name of the SCF
command followed by a process name. The process name must be a valid NonStop
OS process name. Do not use the term “null” when you issue the command.
PROCESS Object Type
Two possible PROCESS objects can exist in the NonStop TCP/IPv6 subsystem:
TCP6SAM and TCP6MAN. TCP6SAM is the socket access method. TCP6MAN is the
manager process. Both TCP6MAN and TCP6SAM run as process pairs. TCP6MAN
provides management functions for the NonStop TCP/IPv6 subsystem and
communicates with the TCP6MONs in each processor. Only one TCP6MAN process
pair can exist in a system; however any number of TCP6SAM process pairs can run in
a system.
Both the TCP6MAN and TCP6SAM processes can be started by using RUN
commands. In addition, the TCP6MAN process can be started by using the persistence
manager.
Only one name is supported for the TCP6MAN process: $ZZTCP. You can assign any
name to the TCP6SAM process.
When you assign a name to a TCP6SAM process, HP recommends that you use a
name that conforms to the conventions for process names. The recommended form for
TCP6SAM process names is $ZTCx or $ZTCxx, where x is a letter or a numeric digit;
for example, $ZTC01. Most HP client and server programs expect the name of a
NonStop TCP/IPv6 process to take this form. This convention allows applications to
use a simple screening algorithm to locate NonStop TCP/IPv6 processes in a system.
However, because the conventional TCP/IP and NonStop TCP/IPv6 environments
coexist on the system, an application programmer wishing to select one or the other of
the two environments needs to either obtain the NonStop TCP/IPv6 process name
from the system administrator or use the SCF LISTDEV TCPIP command to determine
the names of the processes associated with each environment. The LISTDEV
command displays all the TCP/IP processes running on the system. The last field in