HP TCP/IP Services for OpenVMS Version 5.6

HP TCP/IP Services for OpenVMS Version 5.6 SPD 46.46.21
Application Programming Interfaces (APIs)
• libpcap for IPv4 and IPv6
The TCP/IP Services for OpenVMS product provides the
following APIs for programmers to develop customized
applications:
• Berkeley Sockets and Sockets Library provide UNIX
like access for TCP, UDP, and raw IP to applications
written in the C programming language. The library
includes support for:
— Both IPv4 and IPv6 basic socket interface exten-
sions for IPv6 (RFC 2553 and IETF updates)
— Advanced sockets API for IPv6 (RFC 2292 and
IETF updates)
• The $QIO interface extends the OpenVMS system
services for socket communications, providing ac-
cess to TCP, UDP, and IP for applications written in
supported programming languages.
• The SRI $QIO interface translates older, incompati-
ble SRI $QIO interfaces into $QIO interfaces.
• ONC RPC provides an industry-standard, portable
API for programmers who do not have an in-depth
knowledge of networking protocols. This is an ef-
ficient alternative to application development using
sockets.
• Extensible Simple Network Management Protocol
(eSNMP) provides routines for building SNMP sub-
agents.
PATHWORKS, Advanced Server, and DECnet over
TCP/IP
The TCP/IP Services for OpenVMS product includes the
PATHWORKS IP (PWIP) driver and the PWIP ancillary
control process (PWIP_ACP) for improved Advanced
Server and TCP/IP integration.
The PWIP driver allows communication between
OpenVMS systems running either Advanced Server for
OpenVMS or PATHWORKS, and TCP/IP Services soft-
ware, as well as personal computers running PATH-
WORKS 32 client software. It also enables the DECnet-
over-TCP/IP feature, which is included with the DECnet-
Plus for OpenVMS software. (For more information, see
the DECnet-Plus for OpenVMS documentation.)
INSTALLATION AND CONFIGURATION
System managers install the TCP/IP Services for
OpenVMS product using the POLYCENTER Software
Installation utility. A menu-driven configuration proce-
dure makes it easy to enable either all components and
services or only those needed.
HARDWARE REQUIREMENTS
Supported Processors
The TCP/IP Services for OpenVMS product supports
central processing units (CPUs) running OpenVMS.
TCP/IP Services for OpenVMS Version 5.6 is supported
on Integrity Servers and Alpha servers that are listed in
the OpenVMS Version 8.2-1 SPD (SPD 82.35.02) and
in the OpenVMS Version 8.3 SPD (SPD 82.35.08). (For
VAX systems, use Version 5.3 of the TCP/IP Services
for OpenVMS product.)
For a complete list of hardware products, see the
Software Product Description (SPD) for the specific
OpenVMS operating system release.
Required Network Controllers
The TCP/IP Services for OpenVMS software supports
all network devices listed in the OpenVMS Operating
System SPD.
The TCP/IP Services for OpenVMS software can share
an Ethernet interface with other HP networking products
such as DECnet-Plus for OpenVMS.
Memory Requirements
The minimum amount of memory required for the
TCP/IP Services for OpenVMS product is the same as
the requirement for OpenVMS Version 8.2 and Version
8.2-1. Refer to SPD 82.35.01.
Disk Space Requirements
The approximate amount of space required on the sys-
tem disk to support the TCP/IP for OpenVMS software
under the client or server license is 150,000 blocks. Ac-
tual sizes may vary depending on the system environ-
ment, configuration, and software options.
CLUSTER SUPPORT
The TCP/IP Services for OpenVMS product is fully
supported when installed on any valid and licensed
OpenVMS Cluster configuration.
6