ECO NUMBER: ALPLAT05_061 ----------- PRODUCT: OpenVMS Alpha Operating System -------- UPDATED PRODUCT: OpenVMS Alpha Operating System 6.1 ---------------- APPRX BLCK SIZE: 1078 ---------------- COVER LETTER 1 KIT NAME: ALPLAT05_061 2 KITS SUPERSEDED BY THIS KIT: ALPLAT04_061 3 KIT DESCRIPTION: 3.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V6.1, V6.1-1H1, V6.1-1H2 3.2 In order to receive the full fixes listed in this kit the following remedial kits also need to be installed: None 3.3 Files patched or replaced: o [SYS$LDR]SYS$LTDRIVER.EXE (new image) o [SYSEXE]LATACP.EXE (new image) o [SYSEXE]LATCP.EXE (new image) 4 PROBLEMS ADDRESSED IN ALPLAT05_061 KIT o VCRP packets are being overwritten. o CREATE LINE LINK$NAME/DEV=XXA0: command in LATCP can crash the system. o After executing the following commands: LATCP> CREATE SERVICE SERVICE1/APPL LATCP> CREATE SERVICE SERVICE2/APPL LATCP> CREATE SERVICE SERVICE3/APPL LATCP> DELETE SERVICE SERVICE2 LATCP> SET SERVICE SERVICE3/STATIC_RATING=1 the static ratings for services following SERVICE2 can not be -- COVER LETTER -- Page 2 7 January 1998 changed. 5 PROBLEMS ADDRESSED IN ALPLAT04_061 KIT o Item list verification routines caused an ACCVIO o LATACP crashes with PGFIPLHI o LTDRIVER crashes with INVEXCEPTN o Some applications use break through the system service to write to their numerous terminals at the same time. When LATCP is running, the management LTA device created by LATCP is also broadcast to. This slows done the application to the point where the application exhausts its byte limit. o An MC LATCP CREATE PORT command with an invalid device name will crash the system. 6 PROBLEMS ADDRESSED IN ALPLAT01_062 KIT FOR OPENVMS ALPHA V6.1, V6.1-1H1, V6.1-1H2 o Fix possible CPUSPINWAIT crashes and another crash during LAT $QIO postprocessing. o System can only sustain about 125 LAT X sessions to various VXT 2000s on the network. Some customers have more than 125 VXT 2000s and not all users can connect to larger OpenVMS systems. o If LTDRIVER times out a virtual circuit, it will build and transmit a LAT Stop message. If a session on the virtual circuit attempts to write data while the datalink layer owns the Stop message (i.e. the message is on the "to be transmitted" queue), the system will crash in routine LT$DECLARE_CIRC_EVENT. o In the following cases, the print symbiont prints an unwanted form feed after a print job: 1. Output ends exactly at the end of the page 2. File printed with a /PASSALL switch ends with a form feed o Possible CPUSPINWAIT crashes in LT$PORT_CANCEL. o Fix LATACP hangs due to improper synchronization of queuing to LATACP. -- COVER LETTER -- Page 3 7 January 1998 7 PROBLEMS ADDRESSED IN AXPLAT03_061 KIT o If a user connects and disconnects to an LTA device too quickly the following error messages will be generated on the terminal server: Local -207- Protocol violation or Local -226- Protocol violation This will cause every user connected to that host to be disconnected. 8 PROBLEMS ADDRESSED IN AXPLAT02_061 KIT o FDDI controllers are slower than Ethernet controllers when it comes to asynchronous device control events. Because of the CPU speed of Alpha systems, it is possible for a user to create a LAT link on an FDDI controller, delete it and then delete it a 2nd time thus causing a system crash. 9 PROBLEMS ADDRESSED IN AXPLAT01_061 KIT o In V6.1, LATACP was modified to set the LAT rating to 0 if all OpenVMS LMF units have been consumed. Unfortunately, LATACP only checked the OpenVMS ALPHA LMF units. It should also check OpenVMS ALPHA USER. LATACP has been changed to check the same LMF PAKs that LOGINOUT checks before determining if all OpenVMS LMF units have been consumed. NOTE: A LAT rating of 0 does not mean that LAT connections are disabled. It is simply the lowest possible rating that LAT nodes will advertise (meaning the system is 'not very available'). This bug hampers LAT load balancing in an OpenVMS cluster. 10 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide as to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: 2 : To be installed by all customers using the following -- COVER LETTER -- Page 4 7 January 1998 feature(s): LAT 11 INSTALLATION INSTRUCTIONS: Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL ALPLAT04_061 [location of the saveset] The saveset location may be a tape drive, or a disk directory that contains the kit saveset. System should be rebooted after successful installation of the kit. If you have other nodes in your VMScluster, they should also be rebooted in order to make use of the new image(s). Copyright (c) Digital Equipment Corporation, 1998 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL DIGITAL BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.