This document describes DEC TCP/IP Services for OpenVMS VAX, Version 3.3 (formerly known as UCX), a layered software product designed to provide interoperability and resource sharing.
Core Functionality:
It enables communication and resource sharing between OpenVMS VAX systems, UNIX® systems, and other systems supporting the TCP/IP Protocol Suite and Sun® Microsystems NFSTM. Key services include:
- Network file access
- Remote terminal access
- Remote command execution
- Remote printing
- Electronic mail (SMTP)
- Application development
Key Features & Components:
- Protocols: Implements core 4.3 Berkeley Software Distribution protocols like TCP, IP, ICMP, ARP, UDP, and RIP.
- Network File System (NFS): Supports NFS V2.0 for transparent file access, including NFS Client VMS-to-VMS (mounting remote OpenVMS files), NFS server (sharing OpenVMS/UNIX files), Automount, and File Conversion On-The-Fly. It also includes PC-NFS Server for remote PC access.
- Remote Access: Provides TELNET (including TELNET 3270 for IBM systems) and Berkeley Remote Commands (rlogin, rsh, rexec).
- Networking Support: Includes FDDI (Fiber Distributed Data Interface) support, allowing OpenVMS VAX hosts to act as Internet gateways between FDDI and Ethernet networks.
- Service Management: Features the Auxiliary Server (inetd) for service dispatch, BIND Server for Domain Name System (DNS) resolution, and SNMP Agent for network management.
- System Management: Offers UCX Management with Command-Line Interface (DCL-style commands) and Security and Network Access Control.
New in Version 3.3:
- SLIP/CSLIP: Allows host-to-host connections over serial lines.
- Network Time Protocol (NTP): Synchronizes time stamps.
- Enhanced UCX$TRACE Utility.
APIs: Provides C socket, QIO, SRI QIO, and Sun RPC (with XDR and Portmapper) programming interfaces.
- Integration: Supports PATHWORKS IP driver for improved integration.
Installation & Configuration:
The product is installed using VMSINSTAL and offers a menu-driven configuration procedure to select specific services or configure all client components quickly.
System Requirements:
- Hardware: Supports a wide range of VAX, MicroVAX, VAXstation, and VAXserver models. Requires specific network controller interfaces (e.g., DEUNA, DEMNA).
- Disk Space: Approximately 18,000 blocks for installation and 17,000 blocks for permanent use.
- Software: Requires OpenVMS V6.0 or later for support. Client access needs a UNIX operating system supporting NFS V2.0 and relevant TCP/IP protocols.
- Environment: Fully supported in VAXcluster environments.
Interoperability:
NFS components have been tested with various systems including OpenVMS VAX/AXP, SunOS, HP-UX, AIX, A/UX, SCO UNIX, and DEC UNIX/OSF/ULTRIX.