ECO NUMBER: DSNLINKC022 ----------- PRODUCT: DSNlink for VMS -------- UPDATED PRODUCT: DSNlink for VMS 2.2C ---------------- APPRX BLCK SIZE: 18954 ---------------- *********************************** KIT NAME: DSNLINKC022.A --------- OLD PRODUCT: DSNlink V2.2 for OpenVMS ------------ NEW PRODUCT: DSNlink V2.2C for OpenVMS ------------ APPRX BLK SIZE: 18000 blocks --------------- DIGITAL Cover Letter for DSNlink for OpenVMS ECO Kit V2.2C. ECO Kit DSNLINKC022 Description -------------------------------------- The DSNlink Release Notes contain a complete explanation of this release. Below is a brief description: o These Remote Login problems have been fixed: - A remote login session could be terminated if a specialist entered a commands that produce large, single-record output, such as the command SHOW CLUSTER/CONTINUOUS. - All reported causes of disconnecting have been resolved. o Numerous conditions that could lead to a JACKETMSGCORRUPT error while running the ITS application have been resolved. o These File Copy application problems have been fixed: - If a file transferred from the host to a customer's system had (RWED,RWED,RE,) protection, the file rename operation failed. - The Monitoring and Performance History (MPH) analysis tool did not submit files for processing on the host. - The Analysis Tool option did not work unless you supplied a service request number. - File Copy ignored the local authorizations file and allowed all DSNlink users to use File Copy. o These modem transport problems have been fixed: - Modem dialing errors were occurring when some of the modem scripts went into a loop between the script's last two sections. - Customer initiated connections were failing due to some incorrect script settings. - Conditions have been fixed that lead to SYSTEM-F-ABORT messages. - The DTE speed specified during the DSNlink installation was ignored. - Modem connections failed when DSNlink could not lock the modem's virtual line database (VLDB) to send DSNlink mail using OpenVMS mail. This occurred when the sending account did not have the SYSLCK privilege. - The DSN TEST WIRE command generated a device error message, which prevented the test from working. - Modem speeds over 19200 were unstable when using a modem connection to a serial port on a system running OpenVMS Version 7.0. - Modem daemons could hang in an online state if an incoming modem connection was dropped before a link was started and the hangup signal was not detected. - The modem daemon stopped with a CMA-F-IN_USE error due to an abnormal DTE line termination. - DSNlink applications failed if you used the T trace flag on the DSNMODEMAPI_TRACE logical name. - Line daemon could fail with SYSTEM-F-EXQUOTA error without giving enough information to identify the exhausted quota. More information is now provided. - Numerous conditions have been resolved that could lead to line daemon crashes. o DSNlink could not start applications if there was a missing closing quotation mark in the final entry the configuration file, remote authorizations file, or local authorizations file. o These are fixes to the Service Request Application: - You could not change Customer Support Centers using the /SUPPORTCENTER qualifier. - If you attempted to fetch a list of closed service requests from a host that does not provide such lists, an error message window appeared and the process hung. - In the local authorizations file, entries that allow access to the Service Request application, dsn_sra, incorrectly produced "You are not authorized to use this application" messages. - In the DECwindows Motif interface, when errors occurred connecting to the host followed by the user clicking anywhere in the window, the application stopped and generated random application termination errors. - Time zone differences could cause clocks on the host system and your system to appear to be as much as 23 hours different. 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.2C Release Notes. The DSNlink Version 2.2C for OpenVMS kit is installed with the following commands: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL DSNLINKC022 ddcu:[dir] Where ddcu:[dir] is the location of the DSNlink kit. The installation procedure checks for the following: o DSNlink Version 2.2 o Sufficient disk space The save set, which contains files for both Alpha and VAX systems, is approximately 19,000 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 is not stopped by the installation. A system reboot is not necessary. Copyright (c) Compaq Computer Corporation 1999. All Rights reserved. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. 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.