TCP/IP Programming Manual

CIP can coexist with NonStop TCP/IPv6 and conventional NonStop TCP/IP on the same system
but not with Parallel Library TCP/IP since Parallel Library TCP/IP is not supported on J-series RVUs.
CIP also supports IPv6.
CIP architecture differs from that of NonStop TCP/IPv6 and conventional NonStop TCP/IP; these
differences affect the sockets API. For details about the CIP architecture and application compatibility,
see the Cluster I/O Protocols (CIP) Configuration and Management Manual.
NOTE: Parallel Library TCP/IP is only available on NonStop S-series servers.
For information about transport-service provider names, see Process Names (page 43).
TCP/IP Programming Fundamentals
This subsection defines basic TCP/IP programming terms, concepts, and procedures:
• Using NonStop TCP/IP and NonStop TCP/IPv6 or Parallel Library TCP/IP
• Types of Service (page 25)
• The Socket Library Routines (page 25)
• Starting Clients and Servers (page 29)
• Port Numbers (page 31)
• Network and Host Order (page 32)
Using NonStop TCP/IP and NonStop TCP/IPv6 or Parallel Library TCP/IP
An application process can have sockets associated with the NonStop TCP/IP, NonStop TCP/IPv6,
and CIP environments; or the Parallel Library TCP/IP environment.
NOTE: Parallel Library TCP/IP is only available on G-series RVUs.
Using CIP
Applications that use the NonStop TCP/IP, Parallel Library TCP/IP, or TCP/IPv6 API might be
affected by behavioral differences in the CIP API. For details on these differences, see the Cluster
I/O Protocols Configuration and Management Manual. If you determine that these differences do
not cause serious problems for your application, you can use an error suppression feature to allow
the application to continue running if minor differences in the CIP environment are detected. This
feature is described in the following subsection.
Suppressing Compatibility Errors
If you run an application in CIP that contains features that CIP does not support, compatibility errors
result. To allow applications not expecting these errors to run without modification, CIP provides
a DEFINE to suppress errors caused by incompatibility:
ADD DEFINE =CIP^COMPAT^ERROR, FILE SUPPRESS
If this DEFINE is set when an application starts, socket calls that result in a behavior allowed in a
previous implementation, but not in CIP, return as if successful, even though the behavior did not
occur as expected. If the DEFINE is not set or if the file name is not SUPPRESS, behaviors that CIP
does not support cause socket calls to return an error.
24 Introduction to Programming to the Guardian Sockets Library