       $                               Compaq   Software Product  Description   C ___________________________________________________________________   L PRODUCT NAME:   DIGITAL TCP/IP Services for OpenVMS Version 4.2 SPD 46.46.08   DESCRIPTION   D The DIGITAL TCP/IP Services for OpenVMS software product (also knownE as UCX) is the OpenVMS implementation of the industry-standard TCP/IP F suite of communications protocols defined in the TCP/IP layered model.  C Based on the UNIX Berkeley Software Distribution (BSD) Version 4.3  E software, the DIGITAL TCP/IP Services for OpenVMS product is layered  E software that provides interoperability and resource sharing between  H OpenVMS systems, UNIX systems, and other systems that support the TCP/IPB protocol suite and the Network File System (NFS) product from Sun 
 Microsystems.   E The DIGITAL TCP/IP Services for OpenVMS product makes it possible for C OpenVMS users to connect to heterogeneous networks and accomplish a  variety of tasks:   @ o  Network file access - users can access files on remote hosts.  ? o  Electronic mail - users can exchange messages between hosts.   G o  Application development - application programmers can develop TCP/IP A    applications for communication between local and remote hosts.   G o  Download and file transfer - users can exchange files between hosts.   D o  User information - users can access information about other users(    logged onto the local or remote host.  F o  Remote management - system managers can monitor the UCX network and0    applications from remote management stations.  C                                                        October 1998   C                                                         AE-Q088H-TE        H o  Remote terminal access - users can access a remote system as if their1    terminal is connected directly to that system.   G o  Remote command execution - users can issue commands to remote hosts.   D o  Remote printing - users can send or receive print jobs to or from    remote printers.   G o  Remote file copy - users can copy files that reside on remote hosts.   : o  Remote booting - system managers can boot remote nodes.  @ Internetworking with TCP/IP hides the hardware details of each -G individual network and allows computers to communicate independently of F their physical network connections. Internetworking uses a uniform setC of protocols to define behavior on an internet for all nodes using  C supported network media. TCP/IP provides both a standard transport  G mechanism and full-duplex, reliable, stream communication services for   software applications.   Features  H The features of the DIGITAL TCP/IP Services for OpenVMS product include:  C o  A number of components based on Network Interface, Internet, and D    Transport layer protocols and services, which move and manage the$    flow of data around the internet.  C o  A number of components based on Application layer protocols and  D    services, such as electronic mail and remote file computing, that;    OpenVMS users require in open client/server environments   E o  Support for a number of network hardware configurations: Ethernet, H    Fiber Distributed Data Interface (FDDI), Token Ring, and asynchronous*    transfer mode (ATM; Alpha systems only)  G o  A Berkeley Internet Name Domain (BIND) resolver and name server that =    maintains and distributes information about internet hosts   4 o  Cluster load balancing and round-robin scheduling  "                                  2       A o  Easy, fast installation on an OpenVMS Alpha system (using the  F    POLYCENTER Software Installation utility) or an OpenVMS VAX system !    (using the VMSINSTAL facility)   A o  A flexible configuration process that includes an interactive      configuration procedure  B o  The UCX Management Control Program (UCP) command interface for H    configuring and managing the network connections and the UCX software  @ o  Command procedures for automatic startup and shutdown of UCX 
    components   G o  Logical names to help manage applications for local and remote users   F o  Application Programming Interfaces (APIs) for developing customizedB    applications: $QIO, SRI $QIO, standard C sockets and C sockets     library, SUN RPC, and eSNMP  D o  An auxiliary server, similar to the UNIX Internet daemon (inetd),F    that reduces the load on the system and provides security features,$    access control, and event logging  E o  Troubleshooting tools including error messages that display on the E    screen or print to log files; the Trace utility (TCPIPTRACE); BIND @    server load balancing and NSLOOKUP debugging; and management 4    commands to isolate problems and tune performance      "                                  3          Licenses  C Several DIGITAL TCP/IP Services for OpenVMS licenses are available:   C ___________________________________________________________________  License      DescriptionC ___________________________________________________________________   A Server       For customers who require the full product function- A              ality (server and client) of DIGITAL TCP/IP Services               for OpenVMS.   = Client       For customers who require the full functionality =              of the DIGITAL TCP/IP Services for OpenVMS prod- @              uct without the server components (NFS server, BIND?              server, PC-NFS server, remote BOOT server, and RMT               /RCD server).  = Client       For customers who purchased a client license and A upgrade      now require full DIGITAL TCP/IP Services for OpenVMS "              server functionality.C ___________________________________________________________________    Network Interface Layer Support   C With support for multiple network interfaces for each physical net- E work controller, the DIGITAL TCP/IP Services for OpenVMS software al- D lows OpenVMS systems to connect to individual host computers on dif- ferent types of networks:    o  Ethernet   * o  Fiber Distributed Data Interface (FDDI)  
 o  Token Ring   8 o  Asynchronous transfer mode (ATM) (Alpha systems only)  ? Individual host computers can also connect with other hosts or  F networks over serial communications lines using either the Serial LineF Internet Protocol (SLIP or CSLIP) or the Point-to-Point Protocol (PPP)! (OpenVMS Alpha Version 7.1 only).    Internet Layer Support  F The DIGITAL TCP/IP Services for OpenVMS product supports the following? internet layer protocols that work together to move data around 
 the internet:   D o  Internet Protocol (IP) - a connectionless packet delivery service  "                                  4       D o  Routing Information Protocol (RIP) - enables gateways to exchangeJ    current routing information about hosts and directly connected networks  B o  Internet Control Message Protocol (ICMP) - provides diagnostic 3    functions and handles error and control messages   E o  Address Resolution Protocol (ARP) - dynamically maps an IP address !    to a physical hardware address    Transport Layer Support   C To provide either connection-oriented or connectionless data trans- F mission between two hosts (either local or remote), the DIGITAL TCP/IPG Services for OpenVMS product supports both TCP and UDP protocols. These @ protocols form the bridge between the Application layer and the  Internet layer:   F o  Transmission Control Protocol (TCP) - provides connection-oriented,A    reliable, sequenced data transfers for applications that must  !    quarantee delivery of the data   D o  User Datagram Protocol (UCP) - provides fast, connectionless dataG    transfers for applications that do not require delivery confirmation    Application Layer Support   B The DIGITAL TCP/IP Services for OpenVMS product supports numerous 8 Application layer protocols that allow OpenVMS users to:  ! o  Run software on remote systems   7 o  Transfer data files between local and remote systems   H o  Share remote system resources such as disk storage space and printers@    as if they were directly connected to the user's local system  I o  Send and receive electronic mail messages locally or across the world-     wide Internet  "                                  5       F o  Provide consistent, reliable, and efficient network services to all    users on the internet   Remote Computing  F With TELNET, an OpenVMS user can log into remote hosts in the network. The TELNET features include:  ! o  Simultaneous multiple sessions   - o  IBM 3270 model terminal emulation (TN3270)   ; o  Support for both OpenVMS-style and UNIX-style interfaces   F The popular UNIX Remote commands, called R commands, let OpenVMS usersG work in accounts on remote internet hosts that are either UNIX or other B OpenVMS systems. The DIGITAL TCP/IP Services for OpenVMS software 6 supports the RLOGIN, RSH, REXEC, and RMT/RCD commands.  F The Finger utility enables users to obtain information about each userA on local or remote systems. This information includes user name,  2 account name, and the program the user is running.  
 File Transfer   J OpenVMS users transfer data files between local and remote systems through$ the use of the following components:  ? o  File Transfer Protocol (FTP) - transfers files between hosts   H o  Trivial File Transfer Protocol (TFTP) - downloads and transfers files  G o  The remote copy (rcp) command - copies files to or from remote hosts    Resource Sharing  B The DIGITAL TCP/IP Services for OpenVMS software provides network J printing through the line printer/line printer daemon (LPR/LPD) protocols.G LPD provides remote printing services for UNIX and OpenVMS client hosts D through local and remote print queues. Once the print queues are setD up by the system manager, OpenVMS client users issue the DCL command< PRINT and UNIX client users typically issue the lpr command.  "                                  6       @ The TELNET print symbiont (TELNETSYM) lets users print remotely H during a TELNET session. With TELNETSYM, the local OpenVMS system drives2 a remote printer as if it were directly connected.  E With the robust Network File System (NFS) server software, NFS client E users gain transparent access to remote file services. With NFS, when A a user accesses files and directories from a remote system, they  D appear to reside on the local system regardless of operating system,H hardware type, or architectural differences between the local and remoteC systems. The PC-NFS daemon allows the NFS client software to run on G a personal computer. The NFS server promotes data sharing among clients C through a central data storage facility for OpenVMS and UNIX files. D The NFS services are available where specific implementations of NFS, exist on both the client and server systems.   Electronic Mail   E With the Simple Mail Transfer Protocol (SMTP), OpenVMS users can send C and receive electronic mail to and from local and remote hosts. The D DIGITAL  TCP/IP Services for OpenVMS implementation of SMTP uses theC OpenVMS Mail facility, which automatically recognizes an SMTP host  ( address in the format smith@widgets.com.  C The SMTP server works with the Post Office Protocol (POP) server to D provide a reliable mail service. With POP as the mail repository, PCD clients are assured that mail is accepted even when the PC is turned off.   Network Services  B With the following DIGITAL TCP/IP Services for OpenVMS management I components, network and system managers can provide consistent, reliable, A and efficient services to their users, with minimal interruption:   B o  Simple Network Management Protocol (SNMP) - a master agent and E    subagents that allow the UCX system to be managed by a management      station on the network.  C o  Network Time Protocol (NTP) - an environment to synchronize time %    between hosts on a TCP/IP network.   "                                  7       A o  Berkeley Internet Name Domain (BIND) - a distributed database  G    system that distributes and manages host information so hosts do not D    need to know the address of every other host on the internet. TheF    BIND server translates the Domain Name System (DNS) host names intoE    IP addresses. This feature complements the BIND resolver, which is C    the client component of BIND that requests node-name-to-address  #    translations from a BIND server.   A o  Portmapper - a database system that allocates ports so system  E    managers do not need to preconfigure client applications with port     numbers for each service.  C o  Auxiliary server - a process that greatly simplifies application @    writing and manages overhead by reducing simultaneous server F    processes; eliminates high overhead surrounding services processes;G    provides system security through authentication of service requests; (    and supports event and error logging.  D o  The Bootstrap Protocol (BOOTP) - a process that answers bootstrap     requests from remote devices.   Management Control Program  A The DIGITAL TCP/IP Services for OpenVMS product provides the UCX  G Management Control Program (UCP), which is a comprehensive, easy-to-use F network management tool that includes over 100 OpenVMS-style commands.D These commands let system managers locally configure and monitor the UCX components.   $ Logical Names and Command Procedures  B Startup and shutdown command procedures are available for all the D components. In addition, logical names shorten the time it takes to J complete management tasks for various applications such as FTP, NFS, SMTP, and POP.          "                                  8       ) Application Programming Interfaces (APIs)   F The DIGITAL TCP/IP Services for OpenVMS product provides the following8 APIs for programmers to develop customized applications:  A o  Standard C Sockets and C Sockets Library - provides UNIX-like  C    access to TCP, UDP, and raw IP using the C programming language.   B o  $QIO - provides access to TCP, UDP, and IP by extending OpenVMSF    system services for socket communications. Supports any programming    language.  B o  SRI $QIO - translates older, non-UCX $QIO interfaces into $QIO     interfaces.  H o  Sun RPC - provides an industry-standard, portable API for programmersA    who do not have an in-depth knowledge of networking protocols. E    An efficient alternative to application development using sockets.   C o  Extensible Simple Network Management Protocol (eSNMP) - provides /    eSNMP routines for building eSNMP subagents.    PATHWORKS Integration   F The DIGITAL TCP/IP Services for OpenVMS product supports the PATHWORKS8 IP driver for improved PATHWORKS and TCP/IP integration.   INSTALLATION AND CONFIGURATION  @ System managers install the DIGITAL TCP/IP Services for OpenVMS D product using the VMSINSTAL utility (VAX systems) or the POLYCENTER . Software Installation utility (Alpha systems).  F A menu-driven configuration procedure makes it easy to enable the fullC range of components and services or only those needed. In addition, A management commands and logical names let you modify the default  F characteristics of the components and services to fit the needs of the network.    "                                  9        HARDWARE REQUIREMENTS    Supported Processors  A The DIGITAL TCP/IP Services for OpenVMS product supports central  G processing units (CPUs) running OpenVMS Versions 6.2, 7.0, and 7.1. For B a complete list of hardware products, see the SPD for the specific! OpenVMS operating system release.    Required Network Controllers  D The DIGITAL TCP/IP Services for OpenVMS software requires one of the following network controllers:  C ___________________________________________________________________  Controller    Description C ___________________________________________________________________   . Integral      Resident Ethernet communications Ethernet      system  A DEFTA         High-performance network adapter that connects TUR- @               BOchannel systems to ANSI FDDI local area networks  @ DEMFA         High-performance network adapter that connects XMI@               systems to ANSI FDDI local area networks; requires1               microcode revision of 1.4 or higher   @ DEMNA         High-performance network adapter that connects XMI@               systems to both Ethernet and IEEE 802.3 local area               networks  @ PMAD          Network adapter that connects TURBOchannel systemsA               to both Ethernet and IEEE 802.3 local area networks4  9 DETRA         Token ring adapter for the TURBOchannel busM  0 DW110         Token ring adapter for the ISA bus  1 DW300         Token ring adapter for the EISA busuC ___________________________________________________________________   F The DIGITAL TCP/IP Services for OpenVMS software can share an EthernetC interface with other Compaq networking products such as DECnet-Plus  for OpenVMS.  "                                 10 a  g   Memory Requirementst  E The minimum amount of memory required for the DIGITAL TCP/IP Servicesi: for OpenVMS product under the client or server license is:  C ___________________________________________________________________p System           Minimum MemorynC ___________________________________________________________________    OpenVMS VAX      24 MB   OpenVMS Alpha    32 MBC ___________________________________________________________________t  0 Disk Space Requirements (Block Cluster Size = 1)  C The approximate amount of space required on the system disk to sup- G port the DIGITAL TCP/IP for OpenVMS software under the client or server D license is as follows. Actual sizes may vary depending on the system1 environment, configuration, and software options.o  C ___________________________________________________________________n& Requirement                       SizeC ___________________________________________________________________   7 Disk space required for           40,000 blocks (Alpha) 5 installation                      19,000 blocks (VAX)   7 Disk space required for           32,000 blocks (Alpha)t5 permanent use                     18,000 blocks (VAX) C ___________________________________________________________________m   System Parameter Requirementst  G The DIGITAL TCP/IP Services for OpenVMS software requires the followingn/ additional system parameters (minimum amounts):l   o  65 global sectionsh   o  8100 global pagelets   ) o  350,000 bytes of nonpaged dynamic pooln  "                                 11 a  d   CLUSTER SUPPORTn  G The DIGITAL TCP/IP Services for OpenVMS product is fully supported wheniB installed on any valid and licensed OpenVMS Cluster configuration.   SOFTWARE REQUIREMENTSh  L To qualify for a software support contract, the DIGITAL TCP/IP Services for O OpenVMS product requires the OpenVMS operating system Version 6.2, 7.0, or 7.1.m  E Client access requires a system that supports the protocols specifiedrF by NFS Version 2.0 and all TCP/IP application protocols defined by the# TCP/IP Request for Comments (RFCs).I  E The NFS component of the DIGITAL TCP/IP Services for OpenVMS softwarehE has been tested for interoperability and connectivity with clients ofe the following systems:      Sun Microsystems SunOSa    Hewlett-Packard HP-UX
    IBM AIX
    Apple A/UX      Santa Cruz Operation SCO UNIX  = For Systems Using Terminals: OpenVMS Version 6.2, 7.0, or 7.1r  E For Workstations Running DECwindows: OpenVMS Version 6.2. 7.0, or 7.1b  * For Workstations Running DECwindows Motif:  #    OpenVMS Version 6.2, 7.0, or 7.1a6    DECwindows Motif for OpenVMS Version 1.1 (or later)   GROWTH CONSIDERATIONSv  E The minimum hardware and software requirements for any future version C of the DIGITAL TCP/IP Services for OpenVMS product may be different 6 from the minimum requirements for the current version.    "                                 12        DISTRIBUTION MEDIA  C Media and documentation for the DIGITAL TCP/IP Services for OpenVMS A product are available on the DIGITAL CD-ROM Software Library for iF OpenVMS (QA-03XAA-H8). You can order printed documentation separately.   ORDERING INFORMATION  ) DIGITAL TCP/IP Services for OpenVMS Alphah  !    Software Licenses: QL-0LXA*-**t&    Software Documentation: QA-0LXAA-GZ)    Software Product Services: QT-0LXA*-**e  0 DIGITAL TCP/IP Services for OpenVMS Alpha Client  !    Software Licenses: QL-0M2A*-**p&    Software Documentation: QA-0LXAA-GZ)    Software Product Services: QT-0M2A*-**$  8 DIGITAL TCP/IP Services for OpenVMS Alpha Client Upgrade       Software License: QL-0PHA*-**&    Software Documentation: QA-0LXAA-GZ)    Software Product Services: QT-0PHA*-**o  ' DIGITAL TCP/IP Services for OpenVMS VAX,  !    Software Licenses: QL-VHRA*-**g    Software Media: QA-VHRAA-H*&    Software Documentation: QA-VHRAA-GZ)    Software Product Services: QL-VHRA*-**a  . DIGITAL TCP/IP Services for OpenVMS VAX Client  !    Software Licenses: QL-GL7A*-**n&    Software Documentation: QA-VHRAA-GZ)    Software Product Services: QT-GL7A*-**     "                                 13    e  6 DIGITAL TCP/IP Services for OpenVMS VAX Client Upgrade       Software License: QL-OPJA*-**&    Software Documentation: QA-VHRAA-GZ)    Software Product Services: QT-OPJA*-**_  E *  Denotes variant fields. For additional information about availableFF    licenses, services, and media, refer to the appropriate price book.F    This ordering information was valid at the time of release. Contact=    your local Compaq office for current ordering information.n   SOFTWARE LICENSING  C This software is furnished under license only. For more informationoD about Compaq licensing terms and policies, contact your local Compaq office.   D The client license provide complete product functionality except forH the following server components: NFS server, BIND server, PC-NFS server,/ the remote BOOT server, and the RMT/RCD server.   # License Management Facility Support_  D The DIGITAL TCP/IP Services for OpenVMS product supports the OpenVMS" License Management Facility (LMF).  6 License units are allocated on an unlimited use basis.  F For information about the License Management Facility, see the OpenVMS? Operating System Software Product Description (SPD 41.87.xx) or  the OpenVMS documentation.   SOFTWARE WARRANTY   F This software is provided by Compaq with a 90-day conformance warrantyF in accordance with the Compaq warranty terms applicable to the license	 purchase.l            "                                 14 i  c   SOFTWARE PRODUCT SERVICESh  D A variety of service options are available from Compaq. For detailedH information about the service options, contact your local Compaq office.  E The product information in this SPD was valid at time of release. Forl> current product information, contact your local Compaq office.  = [R]    A/UX is a registered trademark of Apple Computer, Inc.i  = [R]    Hewlett-Packard and HP-UX are registered trademarks of         Hewlett-Packard Company.i  = [R]    IBM and AIX are registered trademarks of Internationali%        Business Machines Corporation.   D [R]    IEEE is a registered trademark of the Institute of Electrical&        and Electronics Engineers, Inc.  H [R]    Motif is a registered trademark of Open Software Foundation, Inc.  3 [TM]   NFS is a trademark of Sun Microsystems, Inc.   > [R]    UNIX is a registered trademark in the United States andI        other countries, licensed exclusively through X/Open Company, Ltd.e  8 [TM]   SCO is a trademark of Santa Cruz Operations, Inc.  > [R]    Sun is a registered trademark of Sun Microsystems, Inc.  5 [TM]   SunOS is a trademark of Sun Microsystems, Inc.e  > [TM]   COMPAQ, DEC, DECnet, DECwindows, DIGITAL, DIGITAL UNIX,=        OpenVMS, PATHWORKS, POLYCENTER, TURBOchannel, VAX, VT, =        and the DIGITAL logo are trademarks of Compaq Computer         Corporation.o  ; (c) 1998. Compaq Computer Corporation. All rights reserved.r  "                                 15