MultiNet V5.1 Release Notes July 2005 This document contains a list of new features and bug fixes that have been made since MultiNet V5.0. Revision/Update Information: This document super- sedes the MultiNet V5.0A Release Notes Operating System and Version: VAX/VMS V5.5-2 or later, OpenVMS VAX V6.2 or later, OpenVMS Alpha V6.2 or later, OpenVMS I64 V8.2 __________ Copyright ©2005 Process Software, LLC. Unpublished - all rights reserved under the copyright laws of the United States No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval sys- tem, or translated into any language or computer language, in any form or by any means electronic, mechanical, magnetic, optical, or otherwise with- out the prior written permission of: Process Software, LLC 959 Concord Street Framingham, MA 01701-4682 USA Voice: +1 508 879 6994; FAX: +1 508 879 0042 info@process.com Process Software, LLC ("Process") makes no rep- resentations or warranties with respect to the con- tents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, Process Software reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Process Software to notify any person of such revision or changes. Alpha AXP, AXP, MicroVAX, OpenVMS, VAX, VAX Notes, VMScluster, and VMS are registered trademarks of Hewlett-Packard Corporation. Kerberos. Copyright © 1989, DES.C and PCBC_ENCRYPT.C Copyright © 1985, 1986, 1987, 1988 by Massachusetts Institute of Technology. Export of this soft- ware from the United States of America is as- sumed to require a specific license from the United States Government. It is the responsibility of any person or organization contemplating export to obtain such a license before exporting. WITHIN THAT CONSTRAINT, permission to use, copy, mod- ify, and distribute this software and its doc- umentation for any purpose and without fee is hereby granted, provided that the above copy- right notice appear in all copies and that both that copyright notice and this permission no- tice appear in supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior per- mission. M.I.T. makes no representations about the suitability of this software for any pur- pose. It is provided "as is" without express or implied warranty. MultiNet is a registered trademark of Process Software. Secure Shell (SSH). Copyright © 2000. This Li- cense agreement, including the Exhibits (Agree- ment), effective as of the latter date of ex- ecution (Effective Date), is hereby made by and between Data Fellows, Inc., a California cor- poration, having principal offices at 675 N. First Street, 8th floor, San Jose, CA 95112170 (Data Fellows) and Process Software, LLC, having a place of business at 959 Concord Street, Framingham, MA 01701 (OEM). TCPware is a registered trademark of Process Soft- ware. iii UNIX is a trademark of UNIX System Laboratories, Inc. All other trademarks, service marks, registered trademarks, or registered service marks mentioned in this document are the property of their re- spective holders. Copyright ©1997, 1998, 1999, 2000 Process Soft- ware Corporation. All rights reserved. Printed in USA. Copyright ©2000, 2001, 2002, 2004 Process Soft- ware, LLC. All rights reserved. Printed in USA. If the examples of URLs, domain names, inter- net addresses, and web sites we use in this doc- umentation reflect any that actually exist, it is not intentional and should not be considered an endorsement, approval, or recommendation of the actual site, or any products or services lo- cated at any such site by Process Software. Any resemblance or duplication is strictly coinci- dental. iv _______________________________________________________ Contents _______________________________________________________ CHAPTER 1 INTRODUCTION 1-1 1.1 TYPOGRAPHICAL CONVENTIONS 1-1 1.2 OBTAINING TECHNICAL SUPPORT 1-2 1.2.1 Before Contacting Technical Support 1-3 1.2.2 Sending Electronic Mail 1-5 1.2.3 Calling Technical Support 1-6 1.2.4 Contacting Technical Support by Fax 1-6 1.3 OBTAINING ONLINE HELP 1-7 1.4 MULTINET FREQUENTLY ASKED QUESTIONS (FAQS) LIST 1-7 1.5 ACCESSING THE MULTINET PUBLIC MAILING LIST 1-7 1.6 PROCESS SOFTWARE WORLD WIDE WEB SERVER 1-8 1.7 OBTAINING SOFTWARE PATCHES OVER THE INTERNET 1-9 1.8 DOCUMENTATION COMMENTS 1-10 1.9 CD-ROM CONTENTS 1-11 1.9.1 Online Documentation 1-12 1.9.1.1 PDF Format 1-12 1.9.1.2 Using Acrobat Reader 1-13 1.9.1.3 Using XPDF 1-13 1.10 Disk Space Requirements 1-14 _______________________________________________________ CHAPTER 2 CHANGES AND ENHANCEMENTS 2-1 2.1 MULTINET V5.1 INSTALLATION NOTE 2-1 2.2 NOTE CONCERNING KERBEROS V5 2-1 2.3 NOTE CONCERNING MULTIWARE 2-1 2.4 NOTE CONCERNING SSH 2-2 iii Contents 2.5 CONVERTED SERVICES 2-2 2.6 NOTE CONCERNING FTP CHANGES 2-2 2.7 SSH CHANGES 2-3 2.8 ENHANCEMENTS 2-4 2.9 FIXED PROBLEMS 2-5 _______________________________________________________ CHAPTER 3 DOCUMENTATION UPDATES 3-1 3.1 MULTINET V5.1 3-1 _______________________________________________________ TABLES 1-1 Typographical Conventions 1-1 1-2 System Information 1-4 iv _______________________________________________________ 1 Introduction These Release Notes describe the changes and en- hancements made to the MultiNet product in version 5.1. This chapter describes conventions used in the MultiNet documentation set and the various meth- ods to contact and receive technical support. o For information about product changes and en- hancements in the MultiNet V5.1 MultiNet Con- solidated Distribution, refer to Chapter 2 of these Release Notes. o For information about changes to the documen- tation set, refer to Chapter 3 of these Release Notes. __________________________________________________________________ 1.1 Typographical Conventions Examples in these Release Notes use the follow- ing conventions: Table_1-1_Typographical_Conventions____________ Convention_____Example________Meaning__________ Angle Represents a key brackets on your keyboard. 1-1 Introduction Typographical Conventions Table_1-1_(Cont.)_Typographical_Conventions____ Convention_____Example________Meaning__________ Angle Indicates that brackets you hold down with a slash the key labeled or while simultaneously pressing another key; in this example, the A key. Square [FULL] Indicates brackets 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 file_name or Between words or hyphen file-name in commands, indicates the item is a single ______________________________element._________ __________________________________________________________________ 1.2 Obtaining Technical Support Process Software provides technical support if you have a current Maintenance Service Agreement. 1-2 Introduction Obtaining Technical Support If you obtained MultiNet from an authorized dis- tributor or partner, you receive your technical sup- port directly from them. You can contact Technical Support by: o Sending electronic mail (Section 1.2.2) o Calling Technical Support (Section 1.2.3) o Faxing a description of your problem to the Tech- nical Support Group (Section 1.2.4) ___________________________ 1.2.1 Before Contacting Technical Support Before you call, or send email or a fax: 1. Verify that your Maintenance Service Agreement is current. 2. Read the online Release Notes completely. 3. Have the following information available: o Your name o Your company name o Your email address o Your voice and fax telephone numbers o Your Maintenance Contract Number o OpenVMS architecture o OpenVMS version o MultiNet layered products and versions 4. Have complete information about your configu- ration, error messages that appeared, and prob- lem specifics. 1-3 Introduction Obtaining Technical Support 5. Be prepared to let a development engineer con- nect 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, MultiNet version, and layered products with the MULTINET SHOW /LI- CENSE command. Execute the following command on a fully loaded system and email the output to sup- port@process.com: $ MULTINET SHOW /LICENSE Process Software MultiNet V5.1 Rev A, VAXsta- tion 4000-90, OpenVMS VAX V7.1 In this example: The machine or system architecture is VAX. The OpenVMS version is V7.1. The MultiNet version is V5.1. Use the following table as a template to record the relevant information about your system: Table_1-2_System_Information___________________ Your System Required_Information__________Information______ Your name Company name Your email address Your voice and fax telephone numbers System architecture VAX, Alpha or I64 1-4 Introduction Obtaining Technical Support Table_1-2_(Cont.)_System_Information___________ Your System Required_Information__________Information______ OpenVMS version MultiNet_version_______________________________ Please provide information about installed Multi- Net applications and patch kits, by sending a copy of MULTINET:MULTINET_VERSION.; file. ___________________________ 1.2.2 Sending Electronic Mail For many questions, electronic mail is the pre- ferred 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 in- formation to help your Technical Support Special- ist process and track your electronic support re- quest. 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-5 Introduction Obtaining Technical Support ___________________________ 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 East- ern Time. For our customers in North America with crit- ical 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 fur- ther details. Before calling, have available the information described in Section 1.2.1. 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 our Support Specialists are assisting other customers and you are put on hold, please stay on the line. Most calls are answered in less than five minutes. If you cannot wait for a Specialist to take your call, please take advantage of our au- tomatic call logging feature by sending email to support@process.com (see the Section on Sending Elec- tronic Mail). ___________________________ 1.2.4 Contacting Technical Support by Fax You can send transmissions directly to Techni- cal Support at 508-879-0042. 1-6 Introduction Obtaining Technical Support Before faxing comments or questions, complete the steps in Section 1.2.1 and include all your sys- tem information at the beginning of your fax mes- sage. Continue with the description of your sit- uation and problem specifics. Include all rele- vant information to help your Technical Support Spe- cialist process and track your fax support request. Faxed questions are answered Monday through Fri- day from 8:30 a.m. to 7:00 p.m., United States East- ern Time. __________________________________________________________________ 1.3 Obtaining Online Help Extensive information about MultiNet is provided in the MultiNet help library. For more informa- tion, enter the following command: $ HELP MULTINET __________________________________________________________________ 1.4 MultiNet Frequently Asked Questions (FAQs) List You can obtain an updated list of frequently asked questions (FAQs) and answers about Process Soft- ware products from the Process Software home page located at http://www.process.com. Choose the Sup- port link to access useful information on FAQs and patch ECOs. __________________________________________________________________ 1.5 Accessing the MultiNet Public Mailing List Process Software maintains two public mailing lists for MultiNet customers: o Info-MultiNet@process.com o MultiNet-Announce@process.com 1-7 Introduction Accessing the MultiNet Public Mailing List The Info-MultiNet@process.com mailing list is a forum for discussion among MultiNet system man- agers and programmers. Questions and problems re- garding MultiNet can be posted for a response by any of the subscribers. To subscribe to Info-MultiNet, send a mail message with the word SUBSCRIBE in the body to Info-MultiNet-request@process.com. The in- formation exchanged over Info-MultiNet is also avail- able via the USENET newsgroup vmsnet.networks.tcp- ip.multinet. You can retrieve the Info-MultiNet archives by anonymous FTP to ftp.multinet.process.com. The archives are located in the directory [MAIL_ARCHIVES.INFO- MULTINET]. You can also find the Info-MultiNet archives on the MultiNet consolidated CD-ROM in the directory: [INFO-MULTINET] The MultiNet-Announce@process.com mailing list is a one-way communication (from Process Software to you) used to post announcements relating to Multi- Net (patch releases, product releases, etc.). To subscribe to MultiNet-Announce, send a mail mes- sage with the word SUBSCRIBE in the body to MultiNet- Announce-request@process.com. __________________________________________________________________ 1.6 Process Software World Wide Web Server Electronic support is provided through the Pro- cess Software web site which you can access with any World Wide Web browser; the URL is http://www.process.com (select Support). 1-8 Introduction Obtaining Software Patches over the Internet __________________________________________________________________ 1.7 Obtaining Software Patches over the Internet Process Software provides software patches in save set and ZIP format on its anonymous FTP server, ftp.multinet.process.com. For the location of soft- ware 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 follow- ing commands: $ MULTINET FTP/USERNAME=ANONYMOUS/PASSWORD="emailaddress" - _$ FTP.MULTINET.PROCESS.COM 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.MULTINET.PROCESS.COM>CD [.PATCHES.MULTINETxxx] FTP.MULTINET.PROCESS.COM>GET update_filename In these commands: emailaddress is your email address in the stan- dard user@host format xxx is the version of MultiNet you want to trans- fer update_filename is the name of the file you want to transfer To transfer files from Process Software directly to an OpenVMS system, you can use the GET command without any other FTP commands. However, if you need to transfer a software patch through an in- termediate non-OpenVMS system, use BINARY mode to transfer the files to and from that system. 1-9 Introduction Obtaining Software Patches over the Internet In addition, if you are retrieving the software patch in save set format, make sure the save set record size is 2048 bytes when you transfer the file from the intermediate system to your OpenVMS sys- tem. o If you use the GET command to download the file size from the intermediate system, use the FTP RECORD-SIZE 2048 command before transferring the file. o If you use the PUT command to upload the file to your OpenVMS system, log into the interme- diate system and use the FTP quote site rms rec- size 2048 command before transferring the file. Process Software also supplies UNZIP utilities for OpenVMS VAX, Alpha and I64 for decompressing ZIP archives in the [PATCHES] directory. To use ZIP format kits, you need a copy of the UNZIP utility. The following example shows how to use UNZIP util- ity, assuming you have copied the appropriate ver- sion of UNZIP.EXE to your current default direc- tory: $ UNZIP := $SYS$DISK:[]UNZIP.EXE $ UNZIP filename.ZIP Use VMSINSTAL to upgrade your MultiNet system with the software patch. __________________________________________________________________ 1.8 Documentation Comments Your comments about the information in these Re- lease Notes can help us improve the documentation. If you have corrections or suggestion for improve- ment, please let us know. 1-10 Introduction Documentation Comments 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 email to techpubs@process.com or mail them to: Process Software 959 Concord Street Framingham, MA 01701-4682 Attention: Marketing Director You can also fax your comments to us at 508-879- 0042. Your comments about our documentation are appreciated. __________________________________________________________________ 1.9 CD-ROM Contents MultiNet V5.1 is distributed on one CD, that contains a distribution for VAX and Alpha (MULTINET051.*) and a distribution for I64 (MULTINET_I64051.*). The directory structure for the CD is: [MULTINET051] MultiNet Kit for VAX/Alpha [MULTINET_I64051] MultiNet Kit for I64 [Documentation] PDF format (.pdf) HTML format (.htm) Release Notes [BIND-DOC] [XPDF] [XPDF.AXP] for Alpha images [XPDF.VAX] for VAX images [LYNX] [LYNX.AXP] for Alpha images [LYNX.VAX] for VAX images [VAX55-DECC-RTL] 1-11 Introduction CD-ROM Contents ___________________________ 1.9.1 Online Documentation The MultiNet documentation set is available on the product CD in PDF format. The Release Notes are available on the product CD in text format. _____________________ 1.9.1.1 PDF Format The MultiNet documentation set has the follow- ing PDF files: o MULTINET_ADMIN_GUIDE.PDF (Installation and Ad- minstrator's Guide) o MULTINET_ADMIN_REFERENCE.PDF (Administrator's Reference Guide) o MULTINET_MESSAGES.PDF (Messages, Logicals, & DEC- net Apps) o MULTINET_PROGRAMMERS_REFERENCE.PDF (Programmer's Reference) o MULTINET_USER_GUIDE.PDF (User's Guide) The PDF format is readable from a PC, a VAX or an Alpha system. There is a PDF reader on the CD for the VAX and Alpha platforms. o Use Adobe Acrobat to read the PDF files from a PC. Your PC must have 386 architecture or later to use Adobe Acrobat Reader. You can get Ac- robat Reader free from Adobe Systems' Website: www.adobe.com. o Use the XPDF Reader (found in the [XPDF] direc- tory) to read the PDF files from a VAX or Alpha system. The [XPDF.AXP] directory contains the Alpha architecture reader, and the [XPDF.VAX] directory contains the VAX architecture reader. 1-12 Introduction Online Documentation 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 MultiNet CD directly to a PC. Load them to your VAX, Alpha or I64 machine, then transfer them to your PC. We suggest using FTP to transfer these files. The following is an example using MS-DOS: C:> ftp node ftp> binary ftp> mget cd:*.pdf In addition, Process Software has included LYNX, the character-cell Web browser for VMS. It is in the [LYNX] directory. _____________________ 1.9.1.2 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 nav- igate the document, or click a Table of Contents entry (on the left) to go directly to that in- formation. Note: The binocular icon opens search functions. The mag- nifying glass icon enlarges the text and illustra- tions. _____________________ 1.9.1.3 Using XPDF Thanks to Derek B. Noonburg for letting us down- load his XPDF application. Note: You need a three-button mouse to use XPDF. 1-13 Introduction Using XPDF At the DCL prompt from the directory in which VAX or Alpha XPDF.EXE is stored, do the following: 1. Type RUN XPDF.EXE. The XPDF screen appears. 2. Position the arrow on any of the icons (except the "?" icon) on the bottom of the screen. 3. Press the right nouse 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 question mark (?) icon. 2. Press the left mouse button to open the online help. __________________________________________________________________ 1.10 Disk Space Requirements The following space (in blocks) is required to install and run MultiNet V5.1 (except for the documentation): Reqd to Install Reqd to run --------------- ----------- VAX 265,000 175,000 Alpha 460,000 235,000 I64 460,000 362,000 In addition, 50,000 blocks are required to install the documentation (PDF and HTML) during installation on all platforms. 1-14 _______________________________________________________ 2 Changes and Enhancements This chapter describes the changes and enhance- ments made for MultiNet V5.1. __________________________________________________________________ 2.1 MultiNet V5.1 Installation Notes The MultiNet V5.1 distribution is on one CD. The savesets for the various platforms are: VAX/ALPHA: [MULTINET051]MULTINET051.* I64 [MULTINET_I64051]MULTINET_I64051.* MultiNet V5.1 installations may only be performed from a random-access device (e.g., disk or CD-ROM). If the MultiNet V5.1 installation is attempted from a sequential-access device (e.g., magtape or TKxx cartridge), the installation will fail. If the dis- tribution savesets have been copied to a sequential- access device (for transporting them, for example), they must be copied to a disk for installation. __________________________________________________________________ 2.2 Itanium VMScluster Node Considerations If installing this on a VMS cluster with multiple Itanium nodes sharing a common system disk the following files must be copied from SYS$LOADABLE_IMAGES on the Itanium system where MultiNet V5.1 was originally installed, to SYS$LOADABLE_IMAGES on each remaining Itanium system in the cluster that will be running MultiNet V5.1: - MULTINET_KERNEL.EXE - MULTINET_KERNEL.STB - SSHLEI.EXE 2-1 Changes and Enhancements Notes Concerning MultiWare __________________________________________________________________ 2.3 Note Concerning Kerberos V5 MultiNet now supports Kerberos V5 for SSH and Telnet (Alpha and I64 only). Kerberos V5 requires Kerberos for HP OpenVMS (version 2.0), which is available on the HP website for systems prior to V8.2. The Kerberos V5 applications can also run with any Kerberos V5 compliant Key Distribution Center (KDC) software. Kerberos V5 applies to OpenVMS VAX V7.3 or higher, VMS Alpha V7.2-2 or higher, and VMS I64 V8.2. __________________________________________________________________ 2.4 Note Concerning MultiWare If you want to continue to use MultiWare with MultiNet, do not install MultiNet V5.1 on your sys- tem. MultiWare and all MultiWare-related appli- cations, including management/configuration func- tionality, have been removed. MultiWare was desup- ported by TGV prior to 1997. __________________________________________________________________ 2.5 Note Concerning SSH You must install the DEC C 6.0 backport library on all OpenVMS VAX v5.5-2 and v6.0 systems prior to using SSH. This is the AACRT060.A file. You can find the ECO on the VAX/ALPHA MultiNet CD in the following directory: VAX55_DECC_RTL.DIR. __________________________________________________________________ 2.6 Converted Services o XNTP has been superceded by NTP and has been removed from MultiNet. If XNTP is enabled on a system being upgraded to MultiNet V5.1, the NTP service will be enabled on the upgraded system, with all pertinent parameters converted as appropriate. __________________________________________________________________ 2.7 Note Concerning FTP Changes There have been a number of changes in the FTP client and server to preserve the case of filenames when ODS-5 disks are being used. This has resulted 2-2 Changes and Enhancements Note Concerning FTP Changes in some changes in the default operation. In par- ticular: o When not operating in UNIX mode, the FTP server no longer makes the filenames returned in an NLST command all lowercase. This can effect MGET op- erations. To get the old behavior, define the logical MULTINET_FTP_LOWERCASE_NLST to be TRUE. When operating in UNIX mode, the SRI encoding is still used. o The FTP client no longer changes the case of file- names to lowercase. This can effect MPUT op- erations. To return to the old behavior, de- fine the logical MULTINET_FTP_LOWERCASE_MPUT to be TRUE. o The FTP client will now use SRI encoding for file- names. This can effect GET operations. The ef- fect can be minimized by defining the logical MULTINET_FTP_UNIX_STYLE_CASE_INSENSITIVE to be TRUE. o When a UNIX style ASCII file on a non-UNIX ma- chine is transferred to MultiNet V5.1 a new line is created in the file upon receipt of either a carriage return/line feed sequence or a line feed. To return to the old behavior, define the logical MULTINET_FTP_ONLY_BREAK_ON_CRLF to be TRUE. o There are new FTP logicals added to MultiNet V5.1. Please check "Messages, Logicals, & DECnet Apps" manual for more details. MULTINET_FTP_ONLY_BREAK_ON_CRLF MULTINET_FTP_SEMANTICS_VARIABLE_IGNORE_CC MULTINET_FTP_SEMANTICS_FIXED_IGNORE_CC MULTINET_FTP_STOU_OLDNAME MULTINET_FTP_MAX_PRE_ALLOCATION __________________________________________________________________ 2.8 SSH Changes o SSH has been upgraded to code level 3.2.9. 2-3 Changes and Enhancements SSH Changes o The cryptographic library used is compiled from unaltered source code from F-Secure which is FIPS 140-2 level 2 compliant, as determined by the Computer Security Division of the National Institute of Science and Technology (NIST). o The CERTVIEW utility has been provided, to allow viewing and validation of certificate contents. o OpenSSH-format keys may now be converted to SSH2 format using SSHKEYGEN. o SFTP2 now has the CHMOD and LCHMOD commands for changing the protection of files. o The SSH2 server now supports the UAI$M_PWDMIX flag. [DE 10020] __________________________________________________________________ 2.9 Enhancements o ARP "arp info overwritten" messages have been supressed. o SSH: The SSHD_MASTER.LOG file now includes a date stamp as well as a time stamp for messages. [DE 9953] o SSH: The location of the SSH server log files may now be set by defining the logical MULTINET_SSH_LOG_FILE to the default filespec desired. Any part of the filespec may be defined (.e.g, the complete filespec, the device/directory only, the filename, the file type). [DE 9884] o SFTP: The logical MULTINET_SFTP_FILE_ESTIMATE_THRESHOLD can be used to set the minimum size (in blocks) for a text file to report an estimated size. When a file is smaller than the specified value the file will be read to determine the exact size that would result in a transfer. Files larger than the specified value will continue to get an estimated size. [DE 9889] 2-4 Changes and Enhancements Enhancements o SFTP2 GET and PUT (and MGET and MPUT) now support -p or --preserve-attributes as an option as the first parameter for the command. This option will cause SFTP to attempt to preserve timestamps and access rights when transferring a file. [DE 9888] o SFTP: Setting the logical MULTINET_SFTP_VMS_ALL_VERSIONS to TRUE will now return all versions of files whether or not the SFTP server is communicating with our SFTP client. [DE 9830] o SFTP: The logical MULTINET_SFTP_ODS2_SRI_ENCODING can be defined to FALSE, NO or 0 (zero) to disable SRI encoding of files with uppercase letters and special characters on ODS 2 disks. [DE 9829] __________________________________________________________________ 2.10 Fixed Problems BOOTP o Fixed problems with BOOTP. [DE 10032] DHCP o The DHCP server would crash. [DE 9758] o The DHCP server would log some informational messages as errors. [DE 9697] o The DHCP server would not start with redundancy/ common link setup. [DE 9669] Drivers o Correct NOTDRIVER access issues. [9759] o The IF_VE driver could cause a system crash. [DE 10005] FTP o The FTP server could report a connection refused or device timeout when using a cluster alias and passive mode. [DE 9748] 2-5 Changes and Enhancements Fixed Problems o The FTP client must honor the flag MULTINET_FTP_UNIX_STYLE_CASE_INSENSITIVE. [DE 9360] o The FTP client doesn't exit on an MGET or MPUT error. [DE 9947] GATED o Fix problem with "invalid device" error messages. [DE 9891] IMAP o The IMAP server truncated mail lines that exceed 256 characters. The logical MULTINET_IMAPD_MAX_RECORD_SIZE may be set to any value between 255 and 1024, defaulting to 255. [DE 9810] KERNEL o Setting a cluster alias may cause a kernel crash. [DE 9880] o Any address ending in ".224" or larger has problems with TCP connections. [DE 9760] o If an ICMP message is received on an interface with no address, the system may crash. [DE 9700] o Correct system crash. [DE 9674] o Two processes can bind to the same port when REUSEADDR is set on the port. [DE 9631, DE 9922] o Spurious EWOULDBLOCK errors may occur on a write. [DE 9919] o Setting a different address on a PD device with multiprocessing enabled will cause a system crash. [DE 9873] o Corrected a possible system crash if a PD device starts off with no address. [DE 9945] 2-6 Changes and Enhancements Fixed Problems o Re-transmission timer not started when sending SYN/ACK in 3-way handshake. [DE 9801] o Heavy send queues result in dropped packets and excessive retries. [DE 9626] o The TCP_DO_NAGLE kernel variable was missing. [DE 9971] o Add the IPPORT_USERRESERVED kernel variable to allow reservation of reserved ports. [DE 9753] LPD o Line feeds may be dropped when printing. [DE 9783] o Printer logicals no longer work after upgrading to MultiNet V5.0. [DE 9642] Master Server o Missing REMOTE USERNAME field in the output from ANALYZE/AUDIT/FULL command for network login failures. Miscellaneous o RDATE give a strange /DELTA time display. [DE 9772] NAMED o NAMED would crash if it couldn't create a temporary file. [DE 9610] NFS o Large directories may cause an insufficient virtual memory error. [DE 9717] o The NFS ACP may crash with Windows Services for UNIX V3.5. [DE 9576] o A non-privileged user could cause the NFS server to crash the system using NFSMOUNT. [DE 9424] 2-7 Changes and Enhancements Fixed Problems o Problems with NFS and FTP file naming with multiple dots in filenames. [DE 9681] o Executing a UNIX ls -l command modifies the file date on a MultiNet server. [DE 9495] Programming o Corrected a potential ACCVIO (or other unexpected result) for programs that call getservent or getprotoent without calling setservent or setprotoent first. [DE 10004] RCP o The returning call to decode a double from the XDR Stream left the double (to be populated) with the same value. [DE 9894] o If a logical name is specified for the destination file, the filename of the resulting file was incorrect. [DE 10046] REXEC o REXEC doesn't handle PIPE commands in the same way as other stacks. [DE 9376] ROUTING o Corrected a problem with a route with a /24 mask being treated as a host route. [DE 9897] o The order in which MULTINET SET/INTERFACE did its operations could cause a bogus route to be added for a network that has been subnetted. [DE 10018] o Increased the number of routes that can be deleted with MULTINET SET/ROUTE/FLUSH. [DE 9950] SNMP o Correct system crash. [DE 9612] SMTP o Correct system crash. [DE 9963] 2-8 Changes and Enhancements Fixed Problems SHOW o Fixed problems with MULTINET SHOW/CONNECT=PROCESS (or PID). [DE 9689/10016] SSH o Corrected a problem with an account marked /NOPASSWORD would be treated as if it had a password. [DE 10042] o Corrected a problem with recursive copies and filenames that are SRI encoded. [DE 9969] o Corrected problems with SCP from Unix to VMS with wildcards. [DE 9774] o Corrected problems using SCP to copy a directory after installing SSH-062_A044. [DE 9690] o SCP2 now saves the file attributes when doing $ SCP2 /VMS /DIRECTORY node::device:[dir]*.LIS_* - device:[dir] [DE 9596] o Correct issues with SFTP ASCII transfers. [DE 9978] o Corrected issues with some clients adding extra "./" in directory specifications. [DE 9952] o Corrected problems with the SFTP client ACCVIOs if a file version is specified and that version already exists. [DE 9386] o After a MYDOOM attack, the SSH server process could become compute-bound. [DE 9661] o If Keberos 5 is installed but not configured on a system, the SSH1 and SSH2 server processes will ACCVIO. [DE 9519, DE 9872] o For the SSH server, the JPI$M_PWDEXPIRED flag isn't set for expired passwords if the user is authenticated by some method other than PASSWORD. [DE 9991] o After applying SSH-080_A044, SSH fails to restart the first time the following command is executed: $ MULT NETCONTROL SSH RESTART [DE 9902] 2-9 Changes and Enhancements Fixed Problems Stream Symbiont o Print jobs with empty files end up retained on error (node unreachable). [DE 9364] TCPDUMP o RIP information was dumped incorrectly. [DE 9954] TELNET o Telnet sessions are randomly disconnected from the server. [DE 9936] o /ENCR was incorrectly added to the value in TT_ACCPORNAM. [DE 9881] o The keyboard doesn't respond when doing $ TELNET/TN3270. [DE 9660] UCX Emulation o Corrected problems with threads in UCX$IPC_SHR. [DE 9617] UCXDRIVER o Properly handle requests to cancel read and write attention asts, correcting a performance problem with EnterpriseSCHEDULE. [D/E 9860] o Corrected a problem where a $QIO with nowait, would return an error status of SYSTEM-F-SHUT (0x208c) instead of SYSTEM-F-SUSPENDED (0x03a4) o Correct a system crash in UCXDRIVER. [DE 9637] 2-10 _______________________________________________________ 3 Documentation Updates This chapter contains a summary of changes to the documentation for MultiNet V5.1. __________________________________________________________________ 3.1 MultiNet V5.1 o Changed the MultiNet version number to read V5.1. o Added information on installing on OpenVMS I64 systems to the MultiNet Installation and Administrator's Guide. o Deleted references to XNTP. o The DECNOT configuration section (Appendix A) has been renamed to Chapter 8 of the MultiNet Messages, Logicals and DECnet Applications manual. o Information about CERTVIEW utility has been added to the MultiNet User's Guide. o Added directions for starting DECnet Application Services on Itanium to Chapter 7 of the MultiNet Messages, Logicals and DECnet Applications manual. 3-1