Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

3. The message is forwarded to $ZTA01 (the transport-agent process on processor 1 of
Node B, where Process 4 is running).
4. The message is delivered to Process 4 when that process is ready to accept the message.
For NonStop Parallel Library TCP/IP, Internet domain socket application processes exchange
data through their embedded library code; however, other processes not managed as part
of the OSS environment must be running. The NonStop Parallel Library TCP/IP component
TCPMON, which runs as a process with the name $ZPTMn (where n is its processor number),
must be running in a processor that runs an OSS sockets application program. See the TCP/IP
(Parallel Library) Configuration and Management Manual for more information on data flow
between sockets applications.
For NonStop TCP/IPv6, Internet domain socket application processes exchange data through
their embedded library code; however, other processes not managed as part of the OSS
environment must be running. The NonStop TCP/IPv6 component TCP6MON, which runs as
a process with the name $ZPTMn (where n is its processor number), must be running in a
processor that runs an OSS sockets application program. See the TCP/IPv6 Configuration
and Management Manual for more information on data flow between sockets applications.
AF_UNIX Sockets:
AF_UNIX sockets provide standards-based communications between processes within a system.
Unless otherwise indicated, discussions of AF_UNIX sockets apply to both AF_UNIX Release
1 sockets and AF_UNIX Release 2 sockets.
For AF_UNIX Release 1 sockets, the OSS sockets local server, $ZPLS, is the transport provider
process and $ZTAnn is the transport agent process. For AF_UNIX Release 2 sockets, the OSS
sockets local server 2 server, $ZLSnn (where nn is the processor number), are transport
provider processes. $ZTAnn is the transport agent process.
Both AF_UNIX Release 1 and AF_UNIX Release 2 sockets require an OSS name server to
provide addressing information.
Figure 6 (page 44) shows the OSS name server, OSS sockets local server, and OSS
transport-agent server for AF_UNIX Release 1. In this case, the OSS name server ($ZPNS) for
the root fileset provides the addressing information used by the OSS sockets local server for
an AF_UNIX socket when that socket is created by Process 3 in a directory that is part of the
root fileset.
In the figure, Processes 3 and 4 use AF_UNIX sockets to communicate, as do Processes 3
and 7. When Process 3 sends a message to Process 4, the message is forwarded to $ZTA01,
then to $ZPLS, then to $ZTA01, and then to Process 4. Similarly, when Process 3 sends a
message to Process 7, the message is forwarded to $ZTA01, then to $ZPLS, then to $ZTA02,
and then to Process 7.
Components to Be Managed 43