TCP/IP (Parallel Library) Configuration and Management Manual

Introduction

HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual—522271-006

2-11

TCPMON

The monitor object (TCPMON) provides the Parallel Library TCP/IP environment in

each processor; one TCPMON exists in each configured processor. TCPMONs are

controlled by the TCPMAN process.

TCPMONs are named automatically. The naming convention for TCPMON is

$ZZTCP.#ZPTMn where n is the processor number in which the TCPMON resides.

The format for this processor number is hexadecimal (0-F). The TCPMON object has a

MASTER attribute. The MASTER TCPMON receives and processes inbound frames that

do not match any filter. The MASTER TCPMON also replies to all ICMP echo requests.

TCPSAM

The socket access method (TCPSAM) is a process pair provided for

backward-compatibility for socket applications. TCPSAM provides applications with a

name for a socket transport-service provider. By specifying the TCPSAM process as

the name of the socket transport-service provider, the application programmer can

access Parallel Library TCP/IP and gain the Parallel Library TCP/IP performance

improvement without having to reconfigure the application.

TCPSAM is provided for backward-compatibility only; no data passes through

TCPSAM. See Figure 2-3 on page 2-10 for an illustration of the data path for Parallel

Library TCP/IP.

Any number of instances of TCPSAM can run in a system. The recommended naming

convention for TCPSAM is $ZSAMx. The standard naming convention, $ZBnnn where

nnn represents the LIF associated with the process, does not work in Parallel Library

TCP/IP because the TCPSAM process, unlike the conventional TCP/IP process, is not

associated with a specific LIF. Note that the Expand application expects a TCP/IP

process name to start with Z, so you may want to ensure that at least one TCPSAM

process starts with a Z.

SRL

Parallel Library TCP/IP places most of the protocol stack in a private shared runtime

library (SRL) rather than in a process. Users of ZTCPSRL transparently use QIO

functions without having to explicitly issue calls to initialize the QIO segment. This

architecture allows TCP/IP to retain its context during processing and shortens the

path-length. This library is dynamically loaded into the application’s process space as

soon as the application issues a TCP/IP socket request. Figure 2-3 on page 2-10

shows the application laid over the TCP/IP library. Since the application invokes the