TCP/IP (Parallel Library) Configuration and Management Manual

Configuration Quick Start
HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual—522271-006
1-2
Key Differences Between Parallel Library TCP/IP
and Conventional (HP NonStop) TCP/IP
Key Differences Between Parallel Library
TCP/IP and Conventional (HP NonStop) TCP/IP
Parallel Library TCP/IP presents a new architectural paradigm that requires some
relearning for users who are familiar with the NonStop TCP/IP product. The later
sections of this manual as well as the TCP/IP (Parallel Library) Migration Guide explain
these differences in detail. This subsection highlights some of the major, conceptual
differences between the conventional TCP/IP and Parallel Library TCP/IP products.
Parallel Library TCP/IP doesn’t rely on processes in the same way that conventional
TCP/IP does. However, Parallel Library TCP/IP provides a process for backward
compatibility called the TCPSAM process. For applications that expect a TCP/IP
process, you create a TCPSAM process and use that name when defining a
TCPIP^PROCESS^NAME for application use.
You can create as many TCPSAM processes as you want, but only one TCPSAM
process is required for all the TCP/IP client applications in the system. So, for example,
to run LISTNER and TELSERV as shown in Example 1-1 on page 1-8, just add a
DEFINE/PARAM for a TCPSAM process name exactly as you would add a DEFINE for
a TCP/IP process name in conventional TCP/IP. You no longer have to use different
TCP/IP processes for different applications because you don’t use separate TCP/IP
processes to balance the loads created by the different applications. In Parallel Library
TCP/IP, all the applications can share one TCPSAM process without incurring an
interprocessor-hop cost and without associating themselves with specific, underlying
adapters. The TCPSAM process is not in the processing path for data transfer, it is a
dummy process for backwards compatibility with applications. Parallel Library TCP/IP
can distribute the load from all the TCP/IP-client applications across all the adapters
available in the system.
Another difference is that where conventional TCP/IP could have multiple TCP/IP
processes, each having one or more LIFs uniquely associated with it, Parallel Library
TCP/IP has one manager process ($ZZTCP) and all LIFs are associated with that
process. Since, in Parallel Library TCP/IP, the LIF (and IP address) is no longer
associated with the TCP/IP process used by the applications (TCPSAM), applications
using Parallel Library TCP/IP do not know which LIF or IP address they will get. If you
want to associate an application with a specific LIF (and IP address), you can still do
this by using subnet-level binding. For information about this technique, see Subnet-
Level Binding: How to Isolate Subnets in a Single-IP Environment on page 2-4.