TCP/IPv6 Migration Guide

HP NonStop TCP/IPv6 Migration Guide—524524-004
2-1
2
Transport-Service Provider
Differences for NonStop TCP/IPv6
This section describes the transport-service provider, TCP Socket Access Method
(TCP6SAM). If you are migrating NonStop TCP/IP socket applications to NonStop
TCP/IPv6, you should read this section to familiarize yourself with how to access and
manage TCP6SAM. In addition, this section describes fault-tolerant behavioral
differences between TCP6SAM and the NonStop TCP/IP process that you should be
aware of when using NonStop TCP/IPv6 for your socket applications.
TCP6SAM is a process pair provided for backward compatibility with NonStop TCP/IP
socket applications. TCP6SAM is not in the data path but provides applications with a
name for a socket transport-service provider. By specifying the TCP6SAM process as
the name of the socket transport-service provider, the application programmer can
access NonStop TCP/IPv6 without having to reconfigure the application (unless you
want the application to use IPv6 sockets; see Migrating Your Application to NonStop
TCP/IPv6 on page 4-2).
No restriction exists on the number of instances of TCP6SAM processes running in a
system unless you have configured logical network partitioning (LNP). For LNP, you
can run an unlimited number of TCP6SAM processes in the default partition but only
two TCP6SAM processes in each of the configured partitions.
TCP6SAM names consist of any five alphanumeric characters.
This section covers the following topics:
•
Determining the Name of the Socket Access Method
•
Configuring Applications to Use NonStop TCP/IPv6 on page 2-5
•
Compatibility on page 2-6
•
SCF on page 2-8
Determining the Name of the Socket Access
Method
In NonStop TCP/IP, the transport-service provider was the name of the TCP/IP
process (usually $ZTC0). In NonStop TCP/IPv6, the transport-service provider is the
name of a TCP6SAM process. To use NonStop TCP/IPv6 for your socket applications,
you need to know the name of a TCP6SAM process and set that name to be the
transport-service provider.
Note. The Expand application expects a TCP/IP process name to start with Z.