TCPware v5.4 Release Notes Table of Contents Chapter 1 Introduction 1.1 Typographical Conventions.............................1 1.2 Obtaining Technical Support...........................1 1.2.1 Before Contacting Technical Support.........2 1.2.2 Sending Electronic Mail.....................2 1.2.3 Calling Technical Support...................2 1.2.4 Contacting Technical Support by Fax.........3 1.3 Obtaining Online Help.................................3 1.4 TCPware Frequently Asked Questions List...............3 1.5 Accessing the TCPware Public Mailing List.............3 1.6 Process Software Corporation World Wide Web Server....4 1.7 Obtaining Software Patches Over the Internet..........4 1.8 Documentation Comments................................5 1.9 CD-ROM Contents.......................................5 1.9.1 Online Documentation........................5 1.9.1.1 PDF Format................................5 1.9.1.1.1 Using Acrobat Reader....................6 1.9.1.1.2 Using XPDF..............................6 1.9.1.2 HTML Format...............................7 1.9.1.3 PostScript Format.........................9 Chapter 2 Changes and Enhancements 2.1 New Features and Major Enhancements...................9 2.1.1 OpenVMS Support.............................9 2.1.2 DHCP.......................................10 2.1.3 DNS........................................10 2.1.4 FTP........................................10 2.1.5 SMTP.......................................12 2.1.6 IP AddressWorks(R).........................12 2.1.7 Netscape FasTrack Server...................12 2.1.8 Systems with Multiple Interfaces on a Common Ethernet Cable....................12 2.1.9 New DCL Command............................13 2.2 Changes in this Release..............................13 2.2.1 Unsupported Products......................13 2.2.2 Product Restriction.......................14 2.2.3 New Product Kit...........................14 Problems Fixed Since v5.3................14 2.2.4 ACECLIENT.................................15 2.2.5 DRIVERS...................................15 IPDRIVER.................................15 PWIP.....................................15 NTDriver.................................15 INET.....................................16 BGDRIVER.................................16 TCPDRIVER................................16 2.2.6 LOGICALS..................................16 Mailbox..................................16 2.2.7 NETCU.....................................16 i 2.2.8 SERVERS...................................17 DNS......................................17 IMAP.....................................17 NFS......................................17 LPD......................................17 POP3.....................................19 TFTP.....................................19 REXEC and RSHELL.........................19 RCD......................................19 TALK.....................................19 TELNET...................................19 NTP......................................19 FTP......................................20 2.2.9 CLIENTS..................................20 NFS......................................20 ACL......................................20 NFSMOUNT.................................21 2.2.10 SYMBIONTS................................21 TSSYM....................................21 VMSLPR...................................21 LPS......................................21 2.2.11 Socket Library............................22 2.2.12 TCPDUMP...................................22 2.2.13 TCPWARE_REMOVE............................22 2.2.14 Devices...................................22 2.2.15 Network Testing Tools.....................22 2.3 Upgrading to the New Features.....................22 2.3.1 DNS........................................23 2.3.2 SMTP.......................................24 2.3.3 DHCP.......................................24 Chapter 3 Documentation Updates 3.1 TCPware V5.3-3.......................................25 3.2 TCPware NETCU Command Reference......................25 3.3 TCPware Management Guide.............................29 3.4 TCPware Programmer's Guide...........................37 3.5 TCPware User's Guide.................................38 3.6 TCPware Installation and Configuration Guide.........38 ii TCPware v5.4 RELEASE NOTES Chapter 1 Introduction These Release Notes describe the changes and enhancements made to TCPware for OpenVMS for Version 5.4. This chapter describes conventions used in these Release Notes and the various methods to contact and receive technical support. For information about product changes and enhancements in the TCPware V5.4 Consolidated Distribution, refer to Chapter 2. For information about changes to the documentation set, refer to Chapter 3. 1.1 Typographical Conventions ============================= Examples in these release notes use the following conventions: Convention Example Meaning ======================================= Angle brackets Represents a key on your keyboard. Angle brackets with a slash Indicates that you hold down the key labeled or while simultaneously pressing another key; in this example, the "A" key. Square brackets [FULL] Indicates optional choices; you can enter none of the choices, or as many as you like. When shown as part of an example, square brackets are actual characters you should type. Underscore or file_name Between words in commands, indicates the item hyphen or is a single element. file-name 1.2 Obtaining Technical Support ================================ Process Software provides technical support if you have a current Maintenance Service Agreement. If you obtained TCPware from an authorized distributor or partner, you receive your technical support directly from them. You can contact Process Software's Technical Support by: Sending electronic mail (Section 1.2.2) Calling Technical Support (Section 1.2.3) Faxing a description of your problem to the Technical Support Group (Section 1.2.4) 1 1.2.1 Before Contacting Technical Support ========================================== Before you call, or send e-mail or a fax, please: 1. Verify that your Maintenance Service Agreement is current. 2. Read the Release Notes completely. 3. Have the following information available: -Your name -Your company name -Your e-mail address -Your voice and fax telephone numbers -Your Maintenance Agreement Number -OpenVMS architecture -OpenVMS version -TCPware layered products and versions 4. Have complete information about your configuration, error messages that appeared, and problem specifics. 5. Be prepared to let a Development engineer connect to your system either with TELNET or by dialing in using a modem. Be prepared to give the Engineer access to a privileged account to diagnose your problem. You can obtain information about your OpenVMS architecture, OpenVMS version, TCPware version, and layered products with the NETCU SHOW VERSION /ALL command. Execute the following command on a fully loaded system and email the output to support@process.com: $ NETCU SHOW VERSION /ALL 1.2.2 Sending Electronic Mail ============================= For many questions, electronic mail is the preferred communication method. Technical support via electronic mail is available to customers with a current support contract. Send electronic mail to support@process.com. At the beginning of your mail message, include the information listed in Section 1.2.1. Continue with the description of your situation and problem specifics. Include all relevant information to help your Technical Support Specialist process and track your electronic support request. Electronic mail is answered within the desired goal of two hours, during our normal business hours, Monday through Friday from 8:30 a.m. to 5:00 p.m. United States Eastern Time. 1.2.3 Calling Technical Support ================================= For regular support issues, call 800-394-8700 or 508-628-5074 for support Monday through Friday from 8:30 a.m. to 7:00 p.m., United States Eastern Time. For our customers in North America with critical problems, an option for support 7 days per week, 24 hours per day is available at an additional charge. Please contact your account representative for further details. 2 1.2.3 Calling Technical Support (cont'd) ========================================== Before calling, have available the information described in Before Contacting Technical Support. When you call, you will be connected to a Technical Support Specialist. Be prepared to discuss problem specifics with your Technical Support Specialist and to let that person connect to your system. If a Specialist is not immediately available, your call will be returned as soon as possible. 1.2.4 Contacting Technical Support by Fax =========================================== You can send fax transmissions directly to Technical Support at 508-879-0042. Before faxing comments or questions, complete the steps in Section 1.2.1 and include all your system information at the beginning of your fax message. Continue with the description of your situation and problem specifics. Include all relevant information to help your Technical Support Specialist process and track your fax support request. Faxed questions are answered Monday through Thursday from 8:30 a.m. to 7:00 p.m., and on Friday from 8:30 a.m. to 5:00 p.m. United States Eastern Time. 1.3 Obtaining Online Help ========================== Extensive information about TCPware is provided in the TCPware help library. For more information, enter the following command: $ HELP TCPWARE 1.4 TCPware Frequently Asked Questions List ============================================= You can obtain an updated list of frequently asked questions (FAQs) and answers about TCPware products from the Process Software home page located at http://www.process.com. Choose the "Tech Support" link to access useful information on FAQs and patch ECOs. 1.5 Accessing the TCPware Public Mailing List =============================================== Process Software Corporation maintains two public mailing lists for TCPware customers: --Info-TCPware@process.com --TCPware-Announce@process.com The Info-TCPware@process.com mailing list is a forum for discussion among TCPware System Managers and Programmers. Questions and problems regarding TCPware can be posted for a response by any of the subscribers. To subscribe to Info-TCPware, send a mail message with the word "SUBSCRIBE" in the body to Info-TCPware-request@process.com. The information exchanged over Info-TCPware is also available via the USENET newsgroup vmsnet.networks.tcp-ip.tcpware. 3 1.5 Accessing the TCPware Public Mailing List (cont'd) ======================================================= The TCPware-Announce@process.com mailing list is a one-way communication (from Process Software to you) used to post announcements relating to TCPware (patch releases, product releases, etc.). To subscribe to TCPware-Announce, send a mail message with the word "SUBSCRIBE" in the body to TCPware-Announce-request@process.com. 1.6 Process Software Corporation World Wide Web Server ====================================================== Electronic support is provided through the Process Software Corporation World Wide Web server, which you can access with any World Wide Web browser; the URL is http://www.process.com (select Tech Support). 1.7 Obtaining Software Patches Over the Internet ================================================ Process Software Corporation provides software patches in save set and ZIP format on its anonymous FTP server, ftp.tcpware.process.com. For the location of software patches, read the .WELCOME file in the top-level anonymous directory. This file refers you to the directories containing software patches. To retrieve a software patch, enter the following command: $ FTP FTP.PROCESS.COM After the welcoming screen, enter the user name of ANONYMOUS. The password is your email address in the standard user@host format. A message welcoming you to the Process Software FTP directory appears next followed by the FTP prompt. Enter the following at the FTP> prompt: FTP>CD [.SUPPORT] Change to the directory that represents your version of TCPware. For example, if you have TCPware v5.4, change the directory to 54. FTP>CD 54 Process Software also supplies UNZIP utilities for OpenVMS VAX and Alpha for decompressing ZIP archives in the [PUB.SUPPORT] directory. To use ZIP format kits, you need a copy of the UNZIP utility. The following example shows how to use the UNZIP utility, assuming you have copied the appropriate version of UNZIP.EXE to your current default directory. $ UNZIP := $SYS$DISK:[]UNZIP.EXE $ UNZIP filename.ZIP Use VMSINSTAL to upgrade your TCPware system with the software patch. Patches can be found on our website at www.process.com. Choose "Tech Support" and then the desired product to search for the patches and the Read Me files. 4 1.8 Documentation Comments ========================== Your comments about the information in these release notes can help us improve the documentation. If you have corrections or suggestions for improvement, please let us know. Be as specific as possible about your comments: include the exact title of the document, version, date, and page references as appropriate. You can send your comments by e-mail to: techpubs@process.com or mail them to: Process Software Corporation 959 Concord Street Framingham, MA 01701-4682 Attention: Documentation Manager You can also fax your comments to us at 508-879-0042. Your comments about our documentation are appreciated. 1.9 CD-ROM Contents ==================== The directory structure on the CD is as follows: [TCPWARE054] TCPware Kit [Documentation] HTML format (.htm) PDF format (.pdf) PostScript format (.ps) TEXT format (.txt) Release Notes TEXT format (.txt) [ECOs] [INFO-TCPWARE] [RFCs] [BIND-DOC] [XPDF] [XPDF.AXP] for Alpha images [XPDF.VAX] for VAX images [LYNX] [LYNX.AXP] for Alpha images [LYNX.VAX] for VAX images 1.9.1 Online Documentation ========================== The TCPware documentation set is available in PDF format on the CD. Installation and Configuration INSTALL.PDF Management Guide MANAGE.PDF Programmer's Reference PROGRAM.PDF User's Guide USER.PDF Network Control Utility (NETCU) NETCU.PDF 1.9.1.1 PDF Format ================== The PDF format is readable from a PC, a VAX, or an Alpha system. There is a PDF reader on the CD for each platform. 5 1.9.1.1 PDF Format (cont'd) =========================== o Use Acrobat Reader (found in the [i386] directory) to read the PDF files from a PC. Your PC must have 386 architecture or newer to use Acrobat Reader. You should copy Acrobat Reader from the CD to your system. o Use the XPDF Reader (found in the [XPDF] directory) to read the PDF files from a VAX or Alpha system. The [XPDF.AXP] directory contains the Alpha architecture reader XPDF_AXP.EXE. The [XPDF.VAX] directory contains the VAX architecture reader XPDF_VAX.EXE. You should copy the XPDF Reader from the CD to your system. NOTE: The XPDF Reader does not work on a PC. PCs running the Windows or NT operating system cannot read Process Software's CD. You cannot load files from the TCPware CD directly to a PC. Load them to your VAX or Alpha machine, then transfer them to your PC. We suggest using FTP to transfer all the PDF files. The following is an example using MS-DOS: C:> ftp node ftp> binary ftp> get cd:*.pdf 1.9.1.1.1 Using Acrobat Reader ============================== To read the PDF files using Acrobat Reader: 1. Double click Acrobat Exchange. 2. Choose Open from the File menu. 3. Select the .pdf file you want to open. 4. Use the menu bar at the top of the screen to navigate the document or click a Table of Contents entry (on the left) to go directly to that information. Hints: The binocular icon opens search functions. The magnifying glass icon enlarges the text and illustrations. 1.9.1.1.2 Using XPDF ==================== Thanks to Derek B. Noonburg for letting us download his XPDF application. NOTE: You need a three-button mouse to use XPDF. At the DCL prompt from the directory in which you have copied the XPDF_VAX.EXE or XPDF_AXP.EXE files, do the following: 1. Type RUN XPDF_VAX.EXE or RUN XPDF_AXP.EXE. The XPDF screen appears. 2. Position the arrow on any of the icons (except the ? icon) on the bottom of the screen. 6 1.9.1.1.2 Using XPDF (cont'd) ============================= 3. Press the right mouse button to display choices. 4. Select OPEN to display the list of PDF files. 5. Select the PDF file you want and click OPEN to read the file. 6. Use the icons on the bottom of the screen to search for the information you want. To view the online help for XPDF: 1. Position the cursor on the icon with a question mark (?). 2. Press the left mouse button to open the online help. 1.9.1.2 HTML Format =================== Online documentation is available as HTML files you can use with either a PC browser or a character cell browser. The documentation files and their contents are listed next. Document Directory HTML File Contents Title Names =========================================================================== Installation and Configuration INSTALLATION CH01.HTM Before You Begin CH02.HTM Installing TCPware CH03.HTM Configuring the TCP/IP Core Environment CH04.HTM Configuring the TCP/IP Services CH05.HTM Configuring the NetWare Services CH06.HTM Starting and Testing TCPware APPA.HTM Sample Installation APPB.HTM Sample Configuration APPC.HTM Installed Files User's Guide USER_GUIDE CH01.HTM Introducing TCPware for OpenVMS CH02.HTM Functional Overview CH03.HTM FTP: Transferring Files CH04.HTM Kerberos User Commands CH05.HTM Network Printing CH06.HTM RCD and RMT: Remote CD-ROMS and Tapes CH07.HTM RCP: Copying Files CH08.HTM RLOGIN: Logging In to a Remote Host CH09.HTM RSH: Issuing Commands on a Remote Host CH10.HTM SMTP: Transferring Mail CH11.HTM TALK: Exchanging Terminal Messages CH12.HTM TELNET: Connecting to Remote Terminals 7 User' Guide USER_GUIDE CH13.HTM TFTP: Trivial File Transfers (cont'd) CH14.HTM Token Authentication: Protecting Logins CH15.HTM WHOIS: Username Directory Services APPA.HTM References Glossary.HTM Glossary of Terms Network Control Utility NETCU Command NETCU CH01.HTM Using NETCU CH02.HTM NETCU Commands CH03.HTM MAIL-CONFIG Commands Programmer's Guide PROGRAMMER CH01.HTM Network Programming Overview CH02.HTM UCX Compatibility Services CH03.HTM TCPDRIVER Services CH04.HTM UDPDRIVER Services CH05.HTM IPDRIVER Services CH06.HTM INETDRIVER Services CH07.HTM FTP Library CH08.HTM Socket Library CH09.HTM TELNET Library CH10.HTM SNMP Extendible Agent API Routines CH11.HTM Token Authentication API Functions CH12.HTM ONC RPC Fundamentals CH13.HTM Building Distributed Applications with RPC CH14.HTM RPCGEN Compiler CH15.HTM ONC RPC RTL Management Routines CH16.HTM ONC RPC RTL Client Routines CH17.HTM ONC RPC RTL Port Mapper Routines CH18.HTM ONC RPC RTL Server Routines CH19.HTM ONC RPC RTL XDR Routines CH20.HTM ONC RPC Sample Programs APPA.HTM TCPware Socket Library Management MANAGEMENT CH01.HTM Domain Name Services Guide CH02.HTM DHCP/BOOTP Server CH03.HTM Common Interfaces CH04.HTM Serial Link Interfaces: PPP and SLIP CH05.HTM Cluster Alias Failover CH06.HTM Managing SNMP Services CH07.HTM X.25 Interface CH08.HTM Routing and GateD CH09.HTM Network Time Protocol (NTP) CH10.HTM TIMED CH11.HTM Managing FTP-OpenVMS CH12.HTM Managing NFS-OpenVMS Client CH13.HTM Managing NFS-OpenVMS Server CH14.HTM Managing Print Services CH15.HTM Managing R Commands CH16.HTM Managing Mail Services CH17.HTM Managing TELNET-OpenVMS Server 8 Management MANAGEMENT CH18.HTM Managing TCPware Security Guide (cont'd) CH19.HTM Access Restrictions CH20.HTM Packet Filtering CH21.HTM Managing Token Authentication CH22.HTM Managing Kerberos CH23.HTM IP Security Option CH24.HTM PATHWORKS Support CH25.HTM Tunneling DECnet over IP CH26.HTM X Display Manager Server CH27.HTM DECwindows Transport Interface CH28.HTM Network Testing Tools APPA.HTM NFS-to-OpenVMS Filename Mapping APPB.HTM Data Network Indentification Codes 1.9.1.3 PostScript Format ========================= Online documentation is available as PostScript files. These files are listed next. Document Directory PostScript Title File Names ================================================================== Installation and Configuration INSTALL-CONFIG_DOCS INSTALL.PS Management Guide MANAGEMENT_DOCS MANAGE.PS Programmer's Reference PROGRAMMER_DOCS PROGRAM.PS User's Guide USER_DOCS USER.PS Network Control Utility (NETCU) NETCU_REF_DOCS NETCU.PS Chapter 2 Changes and Enhancements This chapter describes the changes and enhancements made for TCPware V5.4. 2.1 New Features and Major Enhancements ======================================= This section describes the new features and major enhancements made in this release. 2.1.1 OpenVMS Support ===================== TCPware supports OpenVMS v5.5-2 through v7.2-1 on VAX systems and OpenVMS v6.1 through 7.2 on Alpha systems. TCPware v5.4 ensures full TCP/IP functionality on your existing network. Support has been added for the PCI-based Token Ring Adapter (SN-PBXNP-AC). VMS supports this as the IWA0: device and can be configured in CNFNET by selecting the TRW-n device. (D/E 4048) Support has been added for using the Galaxy LAN shared memory transport. Consult the Alpha Galaxy Guide for information on loading the Galaxy LAN shared memory driver, EBDRIVER. 9 2.1.2 DHCP ========== A new DHCP server based on the Internet Software Consortium's (ISC) DHCP server technology is provided with the tools to help you migrate from your current configuration file and lease database. This new, high-performance server offers a more user-friendly configuration file format. It supports Dynamic DNS (DDNS) and, therefore, can update DNS to reflect active leases and includes Safe-failover support. Safe- failover allows for two servers (primary and secondary) to share a configuration and service clients using the same address pool. Leasing information is exchanged between the two servers. The Safe-failover protocol guards against duplication of address assignments during net- work failures, even if the network is partitioned so the primary and the secondary servers cannot communicate and are independently leasing addresses. The Safe-failover protocol is an Internet Draft, co-authored by Process Software Corporation. This draft is part of the IETF DHC working group charter. Also, this version of the DHCP server now can run on multi-homed hosts. 2.1.3 DNS ========= The DNS server with TCPware v5.4 has been updated to BIND v8.1.2. This release has new features that include Dynamic DNS (DDNS) updates (RFC 2136), DNS notify support (RFC 1996), and enhanced control. DNS notify support means that when zone changes occur on the primary server, the primary server notifies the secondary servers, which can then immedi- ately initiate zone transfers rather than waiting for the polling interval to expire. Thus, zone changes propagate much faster through the servers. BIND v8.1.2 also provides more granularity in controlling which servers are allowed to do zone transfers, DDNS updates, queries, etc. Control is available on a zone-by-zone basis, not just on the entire server. DDNS updates allow applications (such as DHCP) to dynam- ically modify resource records. 2.1.4 FTP ========= NOTES o The FTP server has been replaced. While adding new features we have attempted to keep the behavior the same as the old server, but there may be a few differences in the output text. o If you implemented captive FTP server accounts by running the command TCPWARE:FTPD_DTP from their LOGIN.COM file, this no longer works. The account should now be set to /NOINTERACTIVE from AUTHORIZE and the LOGIN.COM file should be modified so that it does NOT run TCPWARE:FTPD_DTP or LOGOUT at the end. o The mechanism used to start the FTP server has changed. If you have FTP commands in SERVERS.COM they no longer apply to the FTP server. You will get error messages if you use the commands in SERVERS.COM for the FTP server. The ACCESS_LIST qualifier was inadvertently over- looked in the new implementation of FTP. ACCESS_LISTs can be used to allow or deny incoming connections from specified IP addresses. You can use Packet Filtering the same way you use ACCESS_LIST. Packet Filtering does not support the error messages that ACCESS_LISTs can provide. See the TCPware for OpenVMS Management Guide, Chapter 20, for information on Packet Filtering. 10 2.1.4 FTP (cont'd) ================== NOTES o Another option for applying access list style filtering is to modify the file TCPWARE:FTPSERVER_DTP.COM. In the space between where TCPWARE_FTP_GET_REMOTE_INFO is defined and deassigned the FTP_SERVER program is run and defines the following logical names: TCPWARE_FTP_ADDRESS - the IP address of the remote node TCPWARE_FTP_HOSTNAME - the name of the remote node TCPWARE_FTP_LOCAL_ADDRESS - the IP address of the node that the FTP server is running on. DCL code can be added at this point to check the IP address and the command file logs out if it is one that should not be allowed in. This check is at a later point than the ACCESS_LIST would have been made, but it should be easier to get the desired effect than using Packet Filtering. The FTP server now supports OpenVMS v7.2 Extended File System (EFS) file naming on ODS-5 disks. EFS offers the ability to store long file names that may include mixed-case characters or spaces in OpenVMS systems. This means file names can be more easily mapped between the OpenVMS and the Windows NT operating systems. When the logical TCPWARE_FTP_LOGFILE is defined, all actions from anonymous users are recorded to the log file. You can now see which lines pertain to which users. If the logical TCPWARE_FTP_LOG_ALL_USERS is also defined, then all addresses from all users are logged. Defining the logical TCPWARE_FTP_RECODE_NONVMS_FILENAMES allows invalid filenames to be converted to valid ones. UNIX-style filenames are recoded so that case can be preserved and characters not allowed in VMS (ODS-2) filenames can be used and displayed as the user typed the filename. The server FTP no longer allows multiple listening processes to handle incoming connections. The following logical names have been added: TCPWARE_FTP_ALL_VERSIONS TCPWARE_FTP_DISALLOW_UNIX_STYLE TCPWARE_FTP_EXTENSION_QUANTITY TCPWARE_FTP_LOG_ALL_USERS TCPWARE_FTP_MAX_SERVERS TCPWARE_FTP_ONLY_BREAK_ON_CRLF TCPWARE_FTP_RECEIVE_THRESHOLD TCPWARE_FTP_RECODE_NONVMS_FILE_NAMES TCPWARE_FTP_SEMANTICS_FIXED_IGNORE_CC TCPWARE_FTP_SERVER_DATA_PORT_RANGE TCPWARE_FTP_SERVER_LOG_LIMIT TCPWARE_FTP_SERVER_RELAXED_PORT_COMMAND TCPWARE_FTP_STRIP_VERSION TCPWARE_FTP_SYST_BANNER TCPWARE_FTP_UNIX_STYLE_BY_DEFAULT TCPWARE_FTP_UNIX_STYLE_CASE_INSENSITIVE 11 2.1.5 SMTP ========== The TCPware SMTP component has been replaced with a new implementation so you can now: o Implement mail rejection rules, necessary for blocking mail relaying and adding anti-spamming capabilities to TCPware. o Deliver files as base64-encoded MIME messages via VMS Mail. If you have implemented virtual domains (that is, your system receives mail for multiple domain names), you must do the following: o Create the file TCPWARE:SMTP_HOST_ALIASES and specify, one per line, all the virtual domains for which this node serves as mail processor. o Define the logical TCPWARE_SMTP_ALLOW_VIRTUAL_DOMAIN as a system-wide, executive-mode logical. The file TCPWARE:SMTP_LOCAL_LOGICALS.COM can be created to define all local SMTP-related logicals. It executes each time SMTP starts. 2.1.6 IP AddressWorks(R) ======================== The new DNS and DHCP servers shipped with TCPware v5.4 are fully com- patible with IP AddressWorks. If you want a powerful, easy-to-use IP address management solution that works with your existing OpenVMS systems, try Process Software's IP AddressWorks. From the IP AddressWorks Management Interface, you can easily and quickly view your network domains, nodes, and services, make changes without knowing zone file or DHCP server configuration file syntax, and have them applied to your TCPware DNS and DHCP servers. 2.1.7 Netscape FasTrack Server ============================== Support has been added for the Netscape FasTrack server. 2.1.8 Systems with Multiple Interfaces on a Common Ethernet Cable ================================================================= TCPware v5.4 has been enhanced to include support for systems that have multiple interfaces on a common Ethernet, FDDI, or Token Ring cable. Configure this support using the following new NETCU SET command: $ NETCU SET INTERFACE line-id/COMMON_LINK=(line-id,line-id,...) With this command TCPware adds ARP entries for each device into the other device's ARP caches and internally links the interfaces together. A performance benefit of this linking occurs if data is to be transmitted on an interface that happens to be busy; TCPware assigns the data to the least busy linked interface for transmission. This linking also provides a level of redundancy. If a linked interface is shut down using NETCU STOP/IP or if a fatal error is detected with the interface and an automatic restart cannot be attempted, then any routing table entries or pseudo devices associated with the shut down interface will be failed over to one of the common link interfaces. 12 2.1.8 Systems with Multiple Interfaces on a Common Ethernet Cable (cont'd) ========================================================================== Note: If failover does occur, the interface is removed from the list of interfaces on the common link. If the interface is restarted, you must re-issue the NETCU SET INTERFACE/COMMON_LINK command. Restrictions: - The joined interfaces must be connected to the same cable. - The joined interfaces must have the same MTU. - The NETCU DEBUG/IP command shows the interface to which a write is queued. However, with linked interfaces, the datagram might actually be transmitted from a linked interface. - If an interface on the common link is shut down and restarted using the NETCU START/IP command, you must re-issue the NETCU SET INTERFACE/COMMON_LINK command to rejoin the interfaces. It is also possible that when the interface is restarted some ARP entries for the interface may remain in other interfaces' ARP caches leading to a "Duplicate IP address!" message on the console. If the address reported is for another interface on the same machine, you can ignore this warning. 2.1.9 New DCL Command ===================== A new DCL command, TCPWARE, has been added that you use to invoke the SMTP configuration utility, MAIL-CONFIG. You enter: $ TCPWARE CONFIGURE/MAIL You should use this command to invoke the SMTP configuration utility, MAIL-CONFIG. NOTE! If you have a 'tcpware' symbol, it will interfere with the use of the SMTP configuration utility (including use of @TCPWARE:CNFNET SMTP). Before invoking MAIL-CONFIG or @CNFNET SMTP, make sure you do not have 'tcpware' defined as a symbol. 2.2 Changes in this Release =========================== This section describes the changes made in this release. 2.2.1 Unsupported Products ========================== WebCNF WebCNF is no longer supported in TCPware. All references to WebCNF have been removed from the TCPware documentation. NetWare NetWare is no longer supported in TCPware. Because it is still in the code, the only reference to NetWare is in the Installation Guide. You can use NetWare if it is already installed on your system. 13 2.2.2 Product Restriction ========================= NobleNet RPC If your RPC application uses NobleNet, modify it not to use NobleNet if you want to use the new RPC library and DEC C. 2.2.3 New Product Kit ===================== TCPware v5.4 is compatible with Process Software's IP AddressWorks product. If you are using IP AddressWorks with TCPware v5.4 on OpenVMS version 5.5-2, you need to install the DEC C/C++ Run-Time Components kit. This kit is available in two places: o at http://ftp.service.digital.com Click the folders (in the order listed here) to access the kit: patches public vms vax v5.5-2 decc 6.0 o on the TCPware v5.4 CD in the directory [VAX55_DECC_RTL]. Read the release notes in the DEC C/C++ Run-Time Components kit to find out if you would be adversely affected by installing this kit. Note: If your version of OpenVMS is later than 5.5-2 or if you are not using IP AddressWorks, you do not need to install the DEC C/C++ Run-Time Components kit. Problems Fixed Since v5.3 ========================= The installation process for TCPware versions 5.3 and 5.4 was enhanced to better support non-system disk installations. This enhancement re- quires that the TCPWARE_ROOT logical for system-disk installations be defined differently starting with TCPware v5.3. This change in logical definition coupled with a fairly common problem with the DEC C Run-Time Library chdir() function and search-listed logicals in OpenVMS v6.2 can cause a few problems with TCPware v5.3 and v5.4. To avoid these problems, change: $ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_ROOT - _$ TCPWARE_SPECIFIC:,TCPWARE_COMMON: to: $ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_ROOT SYS$SYSROOT: Then, rerun TCPWARE_LOGICALS.COM 14 Problems Fixed Since v5.3 (cont'd) ================================== or, install the following patch kit from Compaq: The ECO kits ALPACRT02_062 and VAXCRTL11_062.A exist for the DEC C RTL on OpenVMS Alpha V6.2 through V6.2-1H3, and address the following problem: On FT2 and FT3 of OpenVMS AXP V6.2 and VMS V6.2, the DEC C RTL routine chdir() fails when passed a logical search list. You can get the patch kits from the following location: ftp://ftp.service.digital.com/patches/public/vms/vax/v6.2/ALPACRT02_062 ftp://ftp.service.digital.com/patches/public/vms/vax/v6.2/VAXCRTL11_062.A Note: This is possible for installations only when TCPWARE_SPECIFIC is SYS$SPECIFIC and TCPWARE_COMMON is SYS$COMMON. 2.2.4 ACECLIENT =============== An ACECLIENT security problem has been fixed. (D/E 2198) 2.2.5 DRIVERS ============= IPDRIVER The Maximum Segment Size (MSS) option is now set based on the physical interface of the machine with the largest Maximum Transmission Unit (MTU) value. (D/E 2213) On Alpha systems only: TCPware no longer hangs on start up if the Ethernet card is configured for twisted pair but has no cable connected to it. (D/E 2453) PWIP There is no longer a system crash in PWIPDRIVER when the non-paged pool is exhausted and a pool allocation request fails. (D/E 2273) NTDriver o Under certain circumstances a permanent NTA created using CLOSE_DASSGN could not be deleted. This has been fixed. (D/E 1537) o There was a problem with permanent NTA devices created with the CLOSE_DASSGN keyword. During periods of high CPU use, even when all channels to the NTA device were deassigned, the underlying TCP device would have data left in its receive queue and thus would remain in a CLOSED state. Thus, the NTA device could not be reused. This has been fixed. If needed, additional cleanup of the TCP device can be done using the SHUT_ABORT keyword when creating a permanent NTA device. (D/E 3330) o The permanent NTA device was designed to automatically reconnect 2 seconds after a broken connection is detected (if the RETRIES keyword is NOT 0). If the reconnect failed, an OPCOM message was sent. Also, an OPCOM message was sent if there was a successful reconnect after an initial failure or if all reconnect attempts failed. 15 NTDriver (cont'd) Since this can cause excessive messages when NTA devices are inten- tionally closing and reconnecting, the following TELNET/CREATE key- word was added to prevent these messages: NOOPCOM The optional NOOPCOM keyword specifies that no OPCOM messages are used when a permanent NTA device fails to reconnect or reconnects after an initial failure. By default, OPCOM messages are sent. (D/E 2916) INET The system no longer crashes when the INETDRIVER interface is used and invalid arguments are passed to the IO$_SETSOCKOPT function. (D/E 3448) BGDRIVER TCPware's UCX emulation has been enhanced to allow DCL and Perl scripts to work properly with the Netscape FasTrack web server. (D/E 3509) TCPware now treats the call code INETACP$C_TRANS for the subfunction code INETACP_FUNC$C_GETHOSTBYADDR as an input specifier rather than an output specifier to match the actual behavior of Compaq's TCP/IP Services for OpenVMS and Process Software's MultiNet. (D/E 983) TCPDRIVER A change was made to this driver to prevent successive incoming RSH/RLOGIN connections from hanging. (D/E 3872) 2.2.6 LOGICALS ============== Mailbox TCPware now starts up properly even when a permanent mailbox logical table such as LNM$PERMANENT_MAILBOX is created separately from LNM$SYSTEM_TABLE. (D/E 603) 2.2.7 NETCU =========== Note All SMTP-related commands and qualifiers have been replaced by MAIL-CONFIG commands and qualifers. The command NETCU SHOW CONNECTIONS would display the text "???" after 512 TCP connections were made and also after 256 UDP connections were made. NETCU SHOW CONNECTIONS now displays 1024 TCP connections and 512 UDP connections before displaying the "???" text. The "???" text still means there are more connections than can be displayed. (D/E 1671) A problem handling cluster alias addresses has been corrected. This problem could have caused a node not to fail-over to the cluster address and entering the command NETCU REMOVE SECONDARY would have returned an IVLOCKID error status. (D/E 3709) The NETCU MODIFY SERVICE command no longer causes problems for UDP servers by zeroing out the active server count. This caused a second server to be started by NETCP. (D/E 759) In the list of new NETCU commands for the new DHCP server, there is the command $ NETCU SHOW DHCP/IP_ADDRESS=. This displays the current lease binding details for the given IP address (dynamically-assigned IP addresses only). (D/E 815) 16 2.2.8 Servers ============= DNS A problem with the memory management of the TCPware_DNS process that could have potentially caused a system crash or memory corruption has been corrected. (D/E 2587) IMAP The IMAP server no longer terminates with an access violation when using the IMAP APPEND command to move mail from the IMAP client to the IMAP server. (D/E 1106) The IMAP server no longer terminates with an access violation when accessing a large mail file. It returns an error status to the client. (D/E 1062) When using Microsoft Outlook or Outlook Express as an IMAP client, the IMAP server processes are left in LEF state, and have to be manually terminated, after Outlook terminates. To correct this, install the IMAP patch kit revision 2.0. (D/E 3789) To update the last non-interactive login time you must define the logical TCPWARE_xxxx_UPDATE_LOGIN_TIME, replacing the "xxxx" with either IMAP or POP3. (D/E 817) NFS File corruption no longer occurs when converting files that have more than 65535 records. (D/E 1597) LPD o Parsing errors no longer occur when the string read from the options logical is not terminated properly. (D/E 1420) o The LPD server no longer accepts host names in the LPD_USERS.DAT file as wildcards if they begin with partial wildcards ('*.process.com'). If users have problems printing when they did not have problems before, check to see if there are any partial wildcards for remote host names. (D/E 4232) o The LPD server continues to scan the LPD_USERS.DAT file after encount- ering wildcard entries. It is recommended you place wildcard entries later in the file, after the more specific non-wildcard entries, as the first acceptable mapping will be used. o The capability to map remote users to local users, with failover to a default username has been added. The following shows an access file that provides a specific mapping for a remote user, gertrude. It al- lows access to all users with matching names on both systems, and pro- vides a default mapping for all other users on the node daisy. (D/E 777) !vms-username remote-host remote-user !------------------------------------------ rose daisy gertrude * daisy * daisy_default daisy * 17 LPD (cont'd) o The capability to specifically deny access to print services has been added. Service is disallowed by specifying a hyphen ('-') for the local/VMS username. The following example specifies denial of print services to user thorn on node daisy: - daisy thorn Example: Allowing only specific remote hosts line printer access: ! local user remote system remote user * shiva.tantra.net * * shakti.tantra.net * - * * In this example: - The first line allows access by all users on node shiva.tantra.net. - The second line allows access by all users on node shakti.tantra.net. - The third and final line disallows access by users on any other system (except the local system, which is governed by standard VMS privileges). (D/E 4245) LPQ access: Control of access to line printer services by LPQ clients (which are used to find information about remote print queues and jobs submitted) is not as refined as LPR access (which is used to submit jobs for printing). The LPQ protocol does not include the requestor's username, so this access cannot be controlled on a per-user basis. A user is granted LPQ access if any line in the access file allows access from the remote system being used; that is, if any line other than a 'disallow' (lines beginning with '-' for the local user) refers to the remote system being used. Note: If users have problems printing when they did not have problems before, check to see if there are any partial wildcards for remote host names. If there are partial wildcards for remote host names, there are two possible actions: 1) Change the partial wildcard to a complete wildcard, '*'. This will behave as it did previously with what you intended as a partial wildcard. If this does not work for you, go to action 2. 2) Replace the partial wildcard line with multiple lines, enumerating each system that you want to have access. So, if you previously had a line referring to *.tantra.net, you may now need multiple lines for shiva.tantra.net, shakti.tantra.net, nadi.tantra.net, etc. 18 POP3 The POP3 server now denies access to expired accounts. (D/E 380) You can disable this feature using the logical: $ DEFINE/SYSTEM/EXEC TCPWARE_POP3_ALLOW_EXPIRED TRUE To update the last non-interactive login time you must define the logical TCPWARE_xxxx_UPDATE_LOGIN_TIME, where "xxxx" is either IMAP or POP3. (D/E 817) TFTP The TFTP server now supports netascii mode. You can set the default to be netascii by defining the following logical on the TFTP server: (D/E 1009) $ DEFINE/SYSTEM/EXEC TCPWARE_TFTP_DEFAULT_NETASCII 1 REXEC and RSHELL You can use the REXEC and the RSHELL servers to set up a DECwindows display to the client's IP address if the TCP/IP transport is loaded. (D/E 1336) To enable this functionality, define the following logical: $ DEF/SYS/EXEC TCPWARE_RCMD_ENABLE_DISPLAY TRUE RCD RCD now works. TALK The TALK server returns an error status to the client if the user has PHONE broadcast class disabled. (D/E 456) TELNET User-written applications using the Telnet library and compiled with DEC C on the VAX no longer get three undefined symbols at link time. (D/E 962) A problem that occasionally a TELNET connection was not closed by the TCPware server after the client logged out has been fixed. (D/E 1361) A problem when issuing $ REPLY/ENABLE on an NTA device produced OPCOM messages for the next process to use the same NTA device. For example: if TELNET assigned you NTA10: and you issued the command $ REPLY/ENABLE, you received OPCOM messages. If the next person assigned to NTA10: issued $ REPLY/ENABLE, they would receive your OPCOM messages. The workaround is to issue $ REPLY/ENABLE/TEMPORARY. This TEMPORARY status is automatically done by VMS since TELNET server NTA devices are now set up to be MOUNTED and FOREIGN. (D/E 1095) NTP When a clock change occurs due to a daylight savings time change, and slewalways is enabled, the TCPWARE_TIMEZONE logical is updated to the new timezone at the start of the slewing cycle. (D/E 1904) 19 FTP The new FTP server has caused a new command parsing method. (D/E 3399) For VAX systems only: Intrusion records are no longer logged with a source of SYSTEM, but with user names. (D/E 524) If the logical TCPWARE_FTPD_ALLOW_PRIV_PORT is defined, a privileged port can be specified when using the PORT command. (D/E 686) FTP no longer gives a filwrterr error when a user with a username in excess of 13 characters enters a dir (entering ls and DIR work fine now). (D/E 867) The FTP server converts invalid filenames to valid filenames if the logical TCPWARE_FTP_RECODE_NONVMS_FILE_NAMES is defined. (D/E 323) FTP no longer fails if it does not have delete access to files it created. (D/E 844) The FTP client now properly handles quoted strings, passing the comment character (!) along with the parameters. (D/E 4051) The DECW FTP client now defaults to the VMS file structure for file transfers when the remote system is a VMS system. This corrects some problems with transfering binary files. This action matches that of the command-line client. (D/E 320) The FTP command-line client now prompts with the name of the opened node (for example, foo.bar.com) if the logical TCPWARE_FTP_PROMPT_NODENAME is defined. (D/E 483) The commands COPY /APPEND and GET /APPEND no longer fail when the local file is the destination. The maximum size for the /IMAGE qualifier is 32768. The STATUS command now displays the record size to be used with the /IMAGE qualifier. The /VARIABLE qualifier has meaning only if the /IMAGE qualifier is present. The logical TCPWARE_FTP_MAX_SERVERS allows the maximum number of servers to be set. The default is 10000. The logical TCPWARE_FTP_GETHOST_MAX_TIME takes a value in VMS delta time format (D hh:mm:ss.dd). It controls how long the FTP server will wait while looking up the client's host name with gethostbyaddr. The default value to wait is 10 seconds. (D/E 4448) The FTP server now shows extensions for directories. (D/E 1054) 2.2.9 Clients ============= NFS Wildcard directory usage no longer returns "no such file" on the first attempt. (D/E 3947) ACL ACL propagation no longer fails while creating new files on the TCPware NFS server for directory non-owners. (D/E 3170) 20 NFSMOUNT When the user-id in the command NFSMOUNT/SHOW/QUOTA/USER=[user-id] was unknown, it caused the I/O call to terminate incorrectly. Unknown user ids are no longer a problem in this instance. (D/E 959) 2.2.10 Symbionts ================ TSSYM The TSSYM symbiont no longer performs a DNS query when it is configured with the IP address of a remote printer. (D/E 329) VMSLPR o By default, the VMSLPR symbiont creates the flag page by generating it locally using the VMS print symbiont. At the same time it suppresses the banner page generated by the LPD server. The VMSLPR symbiont can now be configured to generate the banner page. (D/E 758) To enable this functionality on a specific queue, define the following logical: $ DEFINE/SYS/EXEC - _$ TCPWARE_VMSLPRSMB__REMOTE_BANNER TRUE To enable this functionality on all the VMSLPR queues, define the following logical: $ DEFINE/SYS/EXEC TCPWARE_VMSLRPSMB_*_REMOTE_BANNER TRUE o Issues with the last few characters of a print job being truncated have been resolved. Support has also been added for a new logical: $ DEFINE/SYS/EXEC - _$ TCPWARE_VMSLPRSMB__TRIMTAIL In this command, is the specific number of characters to remove from the end of each print job. The default value is 2. (D/E 930) o Some printers would timeout when large print jobs were submitted because the VMSLPR symbiont would open the connection to the printer before processing the file. This has been changed. Now the connection is made after processing the file. (D/E 3396) If you want to "grab and hold" the printer connection while processing, enable the old functionality using the logical TCPWARE_VMSLPRSMB__PRECONN (preconnect). To enable the old functionality on all VMSLPR queues, define: $ DEFINE/SYSTEM/EXEC TCPWARE_VMSLPRSMB_*_PRECONN "TRUE" LPS o Systems with LPS queues no longer wait a long time for startup. (D/E 1476) o Sometimes when the LPS component started up from batch mode it would print a batch log file. This has been fixed by adding /NOPRINT /NOLOG to the LPS_CONTROL.COM's SUBMIT command. The consequence is that no log file is created or printed. (D/E 2221) 21 2.2.11 Socket Library ===================== When the TCPware Socket Library select() function was passed a time-out interval and a list of read descriptors, if the timer expired, select() would return 0 as well as the original list of read descriptors passed in. The function now returns 0, with a cleared list of read descriptors. 2.2.12 TCPDUMP ============== TCPDUMP supports the following new option/qualifier, enabling more detailed decoding of RPC-based services. (D/E 660) R_RPC -"R" all|tcp|udp /RPC [=ALL|TCP|UDP] Note: The UNIX-style option R must be in uppercase and enclosed in quotation marks. You must specify one of the following option/qualifier values: ALL Decode both TCP and UDP (default) TCP Decode only TCP UDP Decode only UDP These eight RPC protocols are decoded: mount NFS version 2 net status PCNFS version 1 network lock manager version 1 PCNFS version 2 network lock manager version 3 portmapper 2.2.13 TCPWARE_REMOVE ===================== TCPWARE_REMOVE.COM now removes SYS$STARTUP:SYS$NET_SERVICES_TCPWARE.COM. (D/E 1241) @TCPWARE:TCPWARE_REMOVE RPC now removes RPC. (D/E 955) 2.2.14 Devices ============== Errors were corrected in opening and closing CD devices. (D/E 4290) 2.2.15 Network Testing Tools ============================ TCPware limits PINGs to about 64,512 bytes. 2.3 Upgrading to the New Features ================================= This section contains instructions on how to upgrade to the new features presented in section 2.1 New Features and Major Enhancements. 22 2.3.1 DNS ========= At nameserver startup, the TCPWARE_NAMED_ROOT:NAMED.BOOT file is converted to a BIND v8 format configuration, TCPWARE_NAMED_ROOT:NAMED.CONF. If you do not have a BIND v4 configuration, BIND v8 default configuration files for a caching server will be put into place at nameserver startup. Note: If your bootfile is set to be something other than TCPWARE_NAMED_ROOT:NAMED.BOOT, you need to copy it to the default location before you start TCPware or reconfigure DNS if you want it converted. In previous versions of TCPware, the cluster load balancing names were configured by the "cluster" directive in the NAMED.BOOT file. With this version of TCPware, the cluster load balancing names are no longer stored in the DNS configuration file. They are communicated to the server by the TCPWARE_CLUSTER_SERVICE_NAMES logical, and can be configured by entering @TCPWARE:CNFNET DNS. Support for the following logicals was removed: TCPWARE_DNS_DEBUG TCPWARE_NAMED_LOGFILE_SEVERITY TCPWARE_NAMED_OPCOM_SEVERITY Also, the command NETCU SET NAMED NODEBUG has been replaced by the the command NETCU SET NAMED DEBUG 0. In previous versions of TCPware, the default OPCOM logging was at and above the level of warning, and NAMESERVER.LOG was at and above the information level. To regain this default, use the following in the logging {} section of the NAMED.CONF file. /* ** The following logging section sets the nameserver to do the ** same logging levels to OPCOM and NAMESERVER.LOG as previous ** versions of TCPware. */ logging { channel file_info { file "SYS$OUTPUT"; severity info; print-time yes; print-category yes; print-severity yes; }; channel syslog_warning { syslog daemon; severity warning; print-category yes; print-severity yes; }; category default { syslog_warning; file_info; }; }; 23 2.3.1 DNS (cont'd) ================== TCPware's nameserver now round robins answers that are not load balanced addresses. (D/E 336) 2.3.2 SMTP ========== You configure the new SMTP component with the command: TCPWARE CONFIGURE/MAIL TCPWARE is now a DCL command. You can set various parameters, all described in the TCPware for OpenVMS Management Guide, to control the delivery of outgoing and incoming SMTP mail. VMS batch queues are now used to send all SMTP mail, so familiarity with VMS batch queues will help in managing TCPware SMTP. Convert your existing SMTP configuration to the new format using the TCPWARE:SMTP_CONFIG_CVT.COM procedure. This procedure runs automatic- ally when the new SMTP starts, or you can run it manually before start- ing SMTP. The conversion works like this: SMTP_CONFIG_CVT.COM reads your SMTP settings from TCPWARE:TCPWARE_CONFIGURE.COM and applies those settings using TCPWARE CONFIGURE/MAIL. SMTP_CONFIG_CVT.COM reads your incoming and outgoing alias files and converts them to the new file formats: TCPWARE:SMTP_ALIASES. and TCPWARE:SMTP_OUTGOING_ALIASES. SMTP_CONFIG_CVT.COM converts your TCPware mailing list files to the new format (it converts the "!" comment character to "#") in a [.MLISTS] subdirectory of your existing mailing list directory. If you have mail waiting for delivery in the TCPware queue, you can requeue those messages to the new batch queues by running the program TCPWARE:TCPWARE_SMTP_REQUEUE_OLD_MAIL.EXE. We recommend you do not run this program until after you have verified that your SMTP mail is properly configured and working. 2.3.3 DHCP ========== Use the DHCP_CONVERSION_TOOL to change from the DHCP server in TCPware v5.3 and earlier to the DHCP server in TCPware v5.4. This tool converts the configuration file and lease file from the format of the earlier DHCP server to the format of the configuration and lease files of the v5.4 DHCP server. It is run automatically by the command procedure that starts the DHCP server, TCPWARE:DHCP_CONTROL.COM. For more details about the conversion tool, see the TCPware Management Guide. 24 Chapter 3 Documentation Changes ===================================== This chapter contains a summary of changes to the documentation for TCPware v5.4. 3.1 TCPware V5.3-3 ================== All document changes and all new and changed features found in the TCPware V5.3-3 release notes have been incorporated into the TCPware documentation set. Replaced the phrase Digital Equipment Corporation and the name Digital with the phrase Compaq Computer and the name Compaq, respectively. 3.2 TCPware NETCU Command Reference =================================== Chapter 1 The following were added to Table 1-2: NETCU Dynamic Host Configuration Commands: RELEASE DHCP SET DHCP SHOW DHCP STOP/DHCP A "MAIL-CONFIG Commands" section was added. Chapter 2 The following has been added to the definition of ADD ACCESS LIST: The access list should be defined in SERVERS.COM. The following have been added to the DEBUG/IP, DEBUG/TCP, DEBUG/UDP qualifiers: /DECODE Shows all IP packets in TCPDUMP output format. You can combine /DECODE with any other qualifiers except /OCTAL and /DECIMAL, since TCPDUMP output is in hex format. The following new NETCU commands have been added: DEFINE TIMEZONE RELEASE DHCP SET DHCP SET INET SET NAMED MAXIMUM-TTL SET NAMED MINIMUM-TTL SHOW DHCP SHOW NAMED VERSION STOP/DHCP STOP/NAMED The following note has been added to the REMOVE ARP command: Removing nonexistent entries does not produce an error message. 25 Chapter 2 (cont'd) SET NAMED DEBUG command: Command Description SET NAMED DEBUG n Sets the debug level. The larger the value of n, the more verbose the output. When the server is busy, NETCU sends a message stating that your request has been queued, and it will be acted upon when it is the next one in the queue to be serviced. When the server is not busy, it performs your request while NETCU waits (except for the case of REREAD). For example: NETCU> dump named stats Dumping Nameserver Statistics Domain-Name-Server Busy, Request Queued Eliminated the SET NAMED NODEBUG command. To disable debugging, use the SET NAMED DEBUG level to zero; for example: SET NAMED DEBUG 0. The /COMMON_LINK qualifier has been added to the SET INTERFACE command. The following parameters have been added to the SHOW command for INET devices: INET_TCP {DROP_TIMER | PROBE_TIMER} (See the SET INET_ commands in the documentation for details on these parameters.) The following information has been added to the SM[_BAK] parameter: SHOW SM and SHOW SM_BAK truncate host names at the 120th character. Limit names to less than 120 characters when adding hosts to the table. The following has been added to the SHOW CONNECTIONS command description: NETCU SHOW CONNECTIONS displays 1024 TCP connections and 512 UDP connections before displaying "???". The question marks mean there are more connections than NETCU SHOW CONNECTIONS can print. 26 Chapter 2 (cont'd) The following have been added to the SHOW CONNECTIONS command qualifiers: /LOCAL Includes the address and port number for incoming and outgoing connections. /REMOTE Includes the address and port number for incoming and outgoing connections. Eliminated the /OUTPUT qualifier in the NETCU SHOW TIMEZONE command. This qualifier is not supported in TCPware. The following has been added to the SHOW STATISTICS command description: Appends the statistics to the TCPWARE:NAMED.STATS file and appends the memory statistics to the TCPWARE:NAMED.MEMSTATS file. A section explaining Pseudo devices has been added. This section explains what a pseudo device is, how to add a device, the characteristics of a device, and when to use pseudo devices, secondary addresses, and interface routes. Eliminated the following NETCU commands because of redundancy with the new MAIL-CONFIG commands: ANALYZE MAIL REMOVE MAIL SEND MAIL SHOW MAIL SET CONFIGURATION SMTP SHOW CONFIGURATION SMTP CREATE ALIAS_DATABASE ADD ALIAS REMOVE ALIAS SHOW ALIAS START/SMTP STOP/SMTP 27 Chapter 2 (cont'd) The following has been added to the TCPDUMP command: R_RPC -"R" all|udp|tcp /RPC [=ALL|UDP|TCP] For UNIX-style options the R must be uppercase and in quotation marks. The option/qualifier values are: Option/Qualifier Decode... ========================================= ALL (default) both UDP and TCP UDP UDP only TCP TCP only For options, you must specify one of the values above. The following RPC protocols are decoded: NFS net status portmapper mount network lock manager version 1 PCNFS version 1 network lock manager version 3 PCNFS version 2 Chapter 3 Added a new chapter containing the following MAIL-CONFIG commands and their descriptions: ADD GATEWAY ADD LOCAL-DOMAIN ADD QUEUE-GROUP ATTACH CLEAR DELETE GATEWAY DELETE LOCAL-DOMAIN DELETE QUEUE-GROUP ERASE EXIT GET HELP PUSH QUIT REMOVE GATEWAY REMOVE QUEUE-GROUP SAVE SET ALIAS-FILE SET DECNET-DOMAIN SET DELIVERY-RECEIPTS SET DISABLE-PSIMAIL SET DISALLOW-USER-REPLY-TO SET FORWARDER SET FORWARD-LOCAL-MAIL SET FORWARD-REMOTE-MAIL 28 Chapter 3 (cont'd) SET HEADER-CONTROL SET HOST-ALIAS-FILE SET LOCAL-MAIL-FORWARDER SET POSTMASTER SET QUEUE-COUNT SET REPLY-CONTROL SET RESENT-HEADERS SET RETRY-INTERVAL SET RETURN-INTERVAL SET SEND-BROADCAST-CLASS SET SMTP-HOST-NAMES SET START-QUEUE-MANAGER SHOW SPAWN STATUS USE VERSION WRITE 3.3 TCPware Management Guide ============================ Chapter 1 Updated the Domain Name Services chapter to reflect the latest NAMED implementation. NAMED is compatible with Process Software's IP AddressWorks product. Made changes to the "Domain Name Server" section. Eliminated the "NAMED.BOOT File" section with "The TCPWARE_NAMED_ROOT:NAMED.CONF File" section. The following have been added to the Fields section of Resource Records: You can specify the following in the time-to-live fields: Note! Each of these is equivalent to one week. o 604800 (seconds) o lw o 7d o 168h o 10080m o or any combination of these values For example: sigma 2h45m40s IN A 192.1.1.97 This loads the TTL as: ttl = 10000 (2 hours 45 mins 40 secs) If you leave this field blank, DNS uses the TTL designated in the SOA (Start Of Authority) record minimum field. The minimum field value is the "default" TTL. Removed all but the first two paragraphs in the "Troubleshooting Domain Name Services" section. 29 Chapter 1 (cont'd) Changed the following sections by removing specific file names and changing the examples to reflect the new Domain Name Services (DNS): Straightforward Clusters Overlapping Clusters Subzone Clusters The functionality of the following logicals is done with the new logging section (page 1-12). Therefore, these logicals were removed: TCPWARE_DNS_DEBUG TCPWARE_NAMED_LOGFILE_SEVERITY TCPWARE_NAMED_OPCOM_SEVERITY Chapter 2 Updated the DHCP/BOOTP Server chapter to reflect the latest Internet Software Consortium (ISC) DHCP-based server information. Removed the "DHCP Cluster Support" section. Expanded the "DHCP Administration" section with more NETCU commands. These are the new topics for the DHCP section. DHCP Process DHCP Conversion Tool Introducing the Configuration File Checking the DHCP Configuration Reloading the DHCP Configuration Dynamic DNS Updates Within DHCP Host Name Generation Configuration File Declarations and Parameters DHCP Statements DHCP Options DHCP Lease Format Address Lease States in DHCP Dump Files DHCP Address Lease States Sample DHCPD.CONF File DHCP Safe-failover Introduction Configuring Safe-failover Boot File for Safe-failover State File for DHCP Safe-failover DHCP Safe-failover Lease File Statements DHCP Safe-failover Configuration File Statements Transitioning to DHCP Safe-failover Partner Down State Chapter 3 Added a "Pseudo Devices" section that explains what a pseudo device is, how to add a device, the characteristics of a device, and when to use pseudo devices, secondary addresses, and interface routes. Chapter 4 Corrected a typo in the "PPPD" section. In the explanation of the -IP option the file name is TCPWARE:PPPOPTIONS.DAT not TCPWARE:PPPDOPTIONS.DAT. 30 Chapter 9 Added the following commands to the "NTPQ, XNTPDC, NTPDATE, and NTPTRACE Utilities" section: ntpq Internal Commands: debug exit passwd version Control Message Commands: addvars authenticate cl clearvars clocklist cv delay keyid keytype lassociations lopeers lpassociations lpeers mreadlist/mrl mreadvar/mrv ntpversion opeers passociations poll readlist/rl rmvars showvars writelist writevar Command Line Format: -d -i -p 31 xntpdc Internal Commands: debug exit keytype version Control Message Commands: addrefclock addtrap clkbug clockstat clrtrap controlkey ctlstats dmpeers fudge iostats kerninfo leapinfo loopinfo memstats monlist preset pstats requestkey reslist showpeer sysinfo timerstats traps Command Line Arguments: -d -i -p -l -s Command Line Options: -d -e -q -v ntptrace Command Line Options: -d -o Chapter 11 The following sentence in the "ANONYMOUS Support" section was in error. The sentence is now: FTP users have automatic read access through ANONYMOUS accounts. 32 Chapter 11 (cont'd) Added new FTP logicals. See these release notes Section 2.1.4 FTP for the list. The following has been added to the "Special Messages" section: The FTP client command line parser interprets the exclamation point (!) as the start of a comment. To send an exclamation point to the server it must be enclosed in quotes ("). The quote character (") must be doubled up in the string if it is to be sent to the server. For example: FTP> dir "! send this string to the server." This sends the whole line, including the exclamation point, the text, and the period to the server. The FTP client command line parser/interpreter prompts with the name of the opened node when the TCPWARE_FTP_PROMPT_NODENAME logical is defined. The unsupported /DATE qualifier in the example in the logical TCPWARE_FTP_UNIX_STYLE_BY_DEFAULT was replaced with a new example using a supported qualifier. Chapter 13 The following have been added to the "EXPORT Options" section: What kind of filename mapping you want to use: /FILENAME=option. The NFS-OpenVMS Server includes the UPPERCASE keyword for this qualifier. UPPERCASE changes the default case for exported filenames from lowercase to uppercase, for SRI filename mappings only. The full syntax of the command is $ NETCU ADD EXPORT /FILENAME=(SRI, UPPERCASE) Examples of filename conversions are as follows: VMS Name Lowercase Uppercase foobar.txt foobar.txt FOOBAR.TXT $foobar.txt FOOBAR.TXT foobar.txt foo$bar.txt fooBAR.TXT FOObar.txt Added the following to the caution for NFS_SECURITY(0) in the "Server Parameters" section: A bit mask 8 value of 128 disables PCNFSD deletion of printed files from the spool directory. 33 Chapter 14 Added the following to the "LPD Access File" section: Use a hyphen (-) to specifically disallow access to printing services. The LPD server continues to scan the LPD_USERS.DAT file after encountering wildcard entries. It is recommended you place wildcard entries later in the file, after the more specific non-wildcard entries, as the first acceptable mapping will be used. The following shows an access file that provides a specific mapping for remote user gertrude. The file specifies access to all users with matching names on both systems, and provides a default mapping for all other users on node daisy. !vms-username remote-host remote-user !---------------------------------------- - daisy thorn rose daisy gertrude * daisy * daisy_default daisy * In the first line, user thorn on system daisy is denied access to printing services. In the second line, the remote user gertrude on daisy gets the name rose. In the third line, the LPD server is instructed to map, as is, accounts having corresponding VMS accounts. In the fourth line, if the remote user on daisy does not have a corresponding VMS account on the local system, it is mapped to account DAISY_DEFAULT. Chapter 15 The following has been added to the "Customizing the shell and exec Services" section: The REXEC and the RSHELL servers have the functionality to set up a DECwindows display to the client's IP address if the TCP/IP transport is loaded. To enable this functionality, define the logical: $ DEFINE/SYSTEM/EXEC TCPWARE_RCMD_ENABLE_DISPLAY TRUE Chapter 16 The SMTP component of TCPware has been redesigned and replaced with a new version that includes support for incoming message filtering and anti-relay features. 34 Chapter 16 The following has been added to the "POP3" section: (cont'd) By default, the User Authorization File (UAF) record for the POP3 user is not affected by a user checking for mail. However, if you want to update the LAST-NON-INTERACTIVE-LOGIN-TIME field in the UAF record for each POP3 user with the current system date and time, define the following system-wide logical: $ DEFINE/SYSTEM TCPWARE_POP3_UPDATE_LOGIN_TIME 1 This update takes place when the authentication process is successfully completed. The following has been added to the "IMAP" section: By default, the User Authorization File (UAF) record for the IMAP user is not affected by a user checking for mail. However, if you want to update the LAST-NON-INTERACTIVE-LOGIN-TIME field in the UAF record for each IMAP user with the current system date and time, define the following system-wide logical: $ DEFINE/SYSTEM TCPWARE_IMAP_UPDATE_LOGIN_TIME 1 This update takes place when the authentication process is successfully completed. Chapter 19 The following has been added to the "Incoming Access Restrictions" section: Access lists should be defined in SERVERS.COM. Chapter 26 The following has been added to the "Introduction" section: The Server is supported on all versions of the Alpha platform and on VAX/VMS v6.1 or higher. The VAX/VMS v5.5-2 is supported if DEC C or the DEC C Run-Time Library (RTL) is installed. Chapter 27 Updated the versions of VAX/VMS and OpenVMS that TCPware v5.4 supports. Chapter 28 Updated the versions of VAX/VMS and OpenVMS that TCPware v5.4 supports. 35 Chapter 28 (cont'd) Added the following to the "FINGER and FINGERD" section: FINGERD reports the day of the week, hour, and minute of a login time only if the user has been logged in for LESS than seven days. If the user has been logged in for MORE than seven days, the date is reported in the dd-mm-yy format. For example: Use this old format for users logged in for less than 7 days: SMITH ZEUS Mary Smith 0 Fri 14:36 FTA419: Use this new format for users logged in for more than 7 days at a time: JONES ZEUS John Jones 14 10-Dec-97 FTA372: Added the following to the "NFS Requests and Replies" section: TCPDUMP supports the following options/qualifiers, thus enabling more decoding of RPC-based services. R_RPC -"R" all|udp|tcp /RPC [=ALL|UDP|TCP] For a UNIX-style option, the R must be uppercase and quoted. The option/qualifer values are Value Meaning ======================================= ALL (default) Decode both UDP and TCP UDP Decode only UDP TCP Decode only TCP The following RPC protocols are decoded: NFS Portmapper Network lock Network lock manager version 1 manager version 3 Net status Mount PCNFS version 1 PCNFS version 2 Added the following to Table 28-4: Device Which is... On platform... For medium... ===================================================== FPA-0 DEFPA AXP FDDI 36 3.4 TCPware Programmer's Guide ============================== Chapter 3 In the "Sample Programs" section added information about FINGER.C. Chapter 7 FTP_SET_DEBUG: for the output-routine argument, changed the definition of mechanism to read "passing by reference a pointer to the address of a routine." In the "Error Status Codes" section changed the link information to read: Then LINK with the definitions of TCPware error messages using the link option: TCPWARE:SOCKLIB.OLB/INCLUDE=TCPWARE_MSGPTR Removed the [ ] from around the length qualifier in the FTP_GET_CCB command. Chapter 8 In the "Transitioning to the C Socket Library: Linking Applications" section, changed the example for VAX C to read: $ link prog, sys$input/options tcpware:ucx$ipc/lib sys$share:vaxcrtl/share Chapter 10 In the "Linking the Extension Agent Image" section, added the following to the VAX example: !You must install the shareable image after you copy it. $ INSTALL ADD/OPEN/HEAD/WRITE/SHARE SYS$SHARE:image-name.exe Chapter 12 Added the following to the "What are ONC RPC Services?" section: ONC RPC Services are a set of software development tools that let you build distributed applications on OpenVMS systems. These services are part of TCP-OpenVMS. ONC RPC Services are based on the Open Network Computing (ONC) Remote Procedure Call (RPC) protocols developed by Sun Microsystems, Inc. These protocols are defined in RFC 1057 and RFC 1014. TCPware provides two types of ONC RPC Services: --ONC RPC used with VAX C and the TCPware Socket Library --RPC XDR used with DEC C and the DEC C Socket Library Chapter 15 Added information to the "Management Routines" section on ONCRPC and RPC RTL. Divided the information in Table 15-1 into DEC C and VAX C categories. 37 3.5 TCPware User's Guide ======================== Chapter 1 Updated Table 1-2 with a revised DHCP explanation. Chapter 3 Updated Table 3-1 with a new definition of Case Conversion. The supported version of DECwindows Motif has been updated to 1.1. Updated the definition of COPY and PUT with information about the use of asterisks. Added a note about specifying the SET DEFAULT parameter and qualifiers separately. Removed the following line from the /MULTIPLE qualifier for the PUT command because FTP MPUT does not use the NLST command: The remote host's server must support the FTP NLST command for remote wildcard operations to work. Corrected two bullets in the format section of the OPEN command: Use OPEN in an interactive command file; you will be prompted for a password. This is a security measure. Use the command non-interactively (for example, a batch job); you will not be prompted for a password. You must include the parameters on subsequent lines, after the OPEN command, in the command file. Chapter 5 Added the "VMSLPR Symbiont" section. This section explains how the enhancement to the VMSLPR symbiont can optionally request the remote LPD server to generate a banner page by using the logical: $ DEFINE/SYSTEM/EXEC - _$ TCPWARE_VMSLPRSMB_REMOTE_BANNER TRUE Chapter 9 Removed the square brackets from the /PASSWORD qualifier. /PASSWORD=remote-password Chapter 10 This chapter was revised to reflect the new SMTP for TCPware. Chapter 12 Added the following keywords to the TELNET /CREATE command: NOOPCOM SHUT_ABORT 3.6 TCPware Installation Guide ============================== Chapter 1 Updated the versions of OpenVMS that TCPware v5.4 now supports. Added a step about reinstalling TCPware after performing a major VMS upgrade to the "General Requirements" section. Chapter 2 Added information about the logicals TCPware checks upon startup in the "Installing TCPware on Mixed Platform Clusters" section. 38 Chapter 3 Added the following sections: --Daylight Savings Time Support --TCPware Time Zone Support --Compiled-In Time Zone Rules --User-Defined Time Zone Rules --Format of COUNTRY Specification --Format of ZONE Specification --Format of RULE Specification --Loadable Time Zone Rules Provided with TCPware Made changes to the "Define the Local Time Zone" section, including an example. Chapter 4 Added example 4-3, which... Added the "Configure the Dynamic Host Configuration Protocol Server" section, including example 4-8. Updated the "Configure the Domain Name Services" section, including example 4-10. It is much easier to configure DNS using CNFNET. Updated the "Configure the Miscellaneous Services" section. Removed all information about the number of listening processes to set in the "Configure the FTP-OpenVMS Server" section. Modified step 1 and step 2 in the "CNFNET Steps" on page 4-35. Added example 4-24, which... In the "Configure SMTP-OpenVMS" section: -Simplified "CNFNET Steps", part 1 to two instructions. -Removed "CNFNET Steps", part 2, part 3, and part 4. Chapter 5 Removed the "Configuring the NetWare Services" chapter as NetWare is no longer supported by Process Software. Chapter 6 Added information about running DECnet and running DECwindows. Updated the OpenVMS versions that TCPware v5.4 now supports. Added information on checking logicals in the "Command Startup or Shutdown Process" section. Appendix B Updated this sample configuration to reflect the current version of TCPware. Removed the "Configuring FTP-OpenVMS" section of the example as you can no longer configure multiple listening processes. Appendix C Updated the installed files tables. 39