ECO NUMBER: DSNLINKE022 ----------- PRODUCT: DSNlink for VMS -------- UPDATED PRODUCT: DSNlink for VMS 2.2E ---------------- APPRX BLCK SIZE: 20106 ---------------- Compaq Cover Letter for DSNlink V2.2E for OpenVMS ECO Kit ECO Kit DSNLINKE022 Description -------------------------------------- The DSNlink Release Notes contain a complete explanation of this release. The following are the significant problems that were fixed in this ECO kit: o X.25 Fixes - DSNlink can now communicate through X.25 router nodes. The X.25 transport on the host can make successful connections to customer sites that have X.25 router nodes. However, both the customer DSNlink nodes and the Compaq host must be running DSNlink Version 2.2E. DSNlink Version 2.2E on the host cannot connect to customers' systems if they are running DSNlink Version 2.2D or earlier kits. If you want to use X.25 to communicate with Compaq, contact your Customer Support Center to coordinate your installation of DSNlink Version 2.2E with that of the host to ensure that DSNlink continues to function. o Modem Fixes - The Configuration utility, DSN$CONFIG.COM, when used to enable the modem transport, did not check for and create the LAT device when an LTAxxx: device was used. If the device was missing, DSNlink started the modem daemon. It ran briefly until it exhausted attempts to use the nonexistent device. - Modem connection problems due to data overruns have been significantly reduced with a new error recovery protocol. Errors are detected and corrected. - The modem daemon stopped when making connections to Compaq on OpenVMS Version 7.1 and 7.2 VAX systems. - When a DSNlink modem line was stopped for any reason, the modem retained the type-ahead mode. - The DSNlink modem daemon could disappear without warning. - The cause of data corruption messages has been fixed. o Communications Fixes - A device name beginning with "MB" incorrectly resulted in the DSNlink transport being set up as X.25, when X.25 was not installed on the system. - We now check for LTA devices, and create them, if necessary. - When the route map was rebuilt at the end of the installation process, the Customer Support Center (CSC) entries were appended to the learned entries section of the route map, causing the CSC entries to be doubled. o File Copy Fixes - When invoking the File Copy Window informational debugging statements appear. The statements have been removed. - When customers attempted to delete their copy of a file after copying it to Compaq, the /DELETE_AFTER qualifier was not recognized. - If a host-to-customer or customer-to-host nonbinary file copy was interrupted and then restarted, an RMS error said the input was too large for the user's buffer, and the file copy failed. - The DSN COPY command did not use the Support Center specified in the /SUPPORTCENTER qualifier. o Installation Fixes - During the installation procedure, customers are asked if they want to purge all the files that have been replaced by newer files provided in the DSNlink kit. If they answered yes, not all files were purged. o Interactive Text Search Fixes - Some actions caused an inactive ITS session to timeout with an error. - The host software caused JACKETMSGCORRUPT errors. - When customers with access to many databases entered the SHOW DATABASE command and then quit the listing, the quitting process took a long time because the server continued to send the entire database list. o Mail Fixes - When entering a mail message in the Message area of the DSNlink Mail window, no text appeared as you typed it. o Network Exerciser - Host-to-customer Network Exerciser tests resulted in authentication failures when the Network Exerciser on the customer's system did not have sufficient privileges to access authentication keys. o Remote Login Fixes - Remote logins to Alpha systems could cause the remote login server to fail with an ACCVIO error. This happened mostly when using the modem protocol. o Service Request Application Fixes - Users without the privilege SYSPRV could not send service requests to DSN% addresses using OpenVMS mail. - Defining the logical name MAIL$INTERNET_TRANSPORT caused the DSNlink mail to Compaq or reply mail from Compaq to fail. The workaround is to insert quotation marks around the routing code and service request number parts of DSNlink mail addresses. - After customers submit a service request, the host responds with an acknowledgment mail message. The From field had the address of the sender instead of the address for the service request number. Customers could not use the Mail REPLY command to augment the service request. - The process quota list was not passed to Alpha systems. It may have caused the modem daemon to fail because of insufficient quota values for the process. VMS EXQUOTA errors appeared in the modem daemon run log. o System Fixes - The directory defined by SYS$SCRATCH was not accessible to DSNlink when the SYS$SCRATCH definition pointed to a directory that was different from the directory defined for the AES_DSNLINK account. This problem prevented DSNlink mail from being sent. It affected the modem daemon process as well as the application server processes. The following are enhancements to DSNlink Version 2.2E: o The modem daemon idle time period is now a configurable value. o Enhanced the DSN SHOW LINE/STATISTICS display to show HDLC attributes and statistics. o The regenerate route map feature of the Configuration utility has a new menu item that sets up a single-port option for communications with Compaq. o The DSN SHOW LINE/STATISTICS command includes information about the HDLC (high-level data link control) component. o DSNlink Version 2.2E now contains a utility that checks the customer's modem setup. o When the customer creates or augments a service request using OpenVMS Mail, the mail is submitted to a batch queue for processing. o Customers can mail themselves a copy of the confirmation message that appears when they augment a service request. o The ITS inactivity timer is suspended while customers are extracting an article to a file. Installation Overview --------------------- Before beginning the installation, customers should rename any modem scripts they want to continue using. The DSNlink installation procedure overwrites current modem scripts with new scripts if the script names are identical. For more information, see the DSNlink Version 2.2E Release Notes. The DSNlink Version 2.2E for OpenVMS kit is installed with the following commands: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL DSNLINKE022 ddcu:[dir] Where ddcu:[dir] is the location of the DSNlink kit. The installation procedure checks for the following: o DSNlink Version 2.2 or DSNlink Version 2.2C or DSNlink Version 2.2D o OpenVMS Version 6.2, 7.1, or 7.2 o Sufficient disk space The save set, which contains files for both Alpha and VAX systems, is approximately 20,100 blocks. o The account from which DSNlink is installed has SETPRV or at least the following privileges: CMKRNL DETACH NETMBX SYSPRV SYSNAM SYSLCK TMPMBX WORLD o Running DSNlink modem processes. o A running Queue Manager. o The queue SYS$BATCH DSNlink modem processes must be stopped during the DSNlink V2.2E installation. DSNlink connections using DECnet, X2.5, or TCP/IP are not stopped. A system reboot is not necessary. Copyright (c) Digital Equipment Corporation 1999. All Rights reserved. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. This ECO has not been through an exhaustive field test process. Due to the experimental stage of this ECO/workaround, Compaq makes no representations regarding its use or performance. The customer shall have the sole responsibility for adequate protection and back-up data used in conjunction with this ECO/workaround.