ECO NUMBER: VAXLAD02_062 PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: VAXLAD02_062 2 KITS SUPERSEDED BY THIS KIT: VAXLAD01_062 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: None. 3.2 In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS VAX V6.2 4.2 Files patched or replaced: o [SYSEXE]ESS$LADCP.EXE (new image) o [SYSEXE]ESS$LASTCP.EXE (new image) o [SYS$LDR]ESS$DADDRIVER.EXE (new image) o [SYS$LDR]ESS$LADDRIVER.EXE (new image) o [SYS$LDR]ESS$LASTDRIVER.EXE (new image) o [SYS$LDR]ESS$MADDRIVER.EXE (new image) o [SYS$STARTUP]ESS$STARTUP.COM o [SYS$STARTUP]ESS$LAST_STARTUP.COM -- COVER LETTER -- Page 2 16 September 1999 5 PROBLEMS ADDRESSED IN VAXLAD02_062 KIT o In a multi-processor environment, the service solicitation queues may be accessed by several processors. Since these queues are not synchronized correctly, they can get corrupted. Thus, the system crashes with an INVEXCEPTN at around LASTDRIVER+3513 in routine LAST$TICK. Note that LAST should not be started on non-connected Ethernet controllers. Otherwise, problems with the LADCP> SHOW SERVICE command can occur. This problem is corrected in OpenVMS VAX V7.2 Image(s) Affected: - [SYS$LDR]SYS$LASTDRIVER.EXE o If a tape is initialized on a TZ87 and then put on a TZ86 with an attempt to re-initialize the tape, the TZ86 takes an excessive amount of time to determine how to handle the tape. Hence, it times out. This problem is corrected in OpenVMS VAX V7.2 Image(s) Affected: - [SYS$LDR]SYS$MADDRIVER.EXE 6 PROBLEMS ADDRESSED IN VAXLAD01_062 KIT o UCB$L_DEVCHAR2 characteristics bits are not defined correctly when the template UCB is created. This problem causes SECURITY to crash the system and causes LADCP> BIND SERVICE/TAPE to prefix device name, MADx, with a node name or allocation class. This result is inconsistent with the DAD device naming convention. o The occasional packet transmitted by EWDRIVER had a source address and protocol type of zeros, which are discarded by the receiver. The booting system then retransmitted the packet 3 seconds later. However, since it is handling only 10 packets per second, the system booted very slowly. o If LADDRIVER parses connection (or solicitation) messages that have the sign bit set in the service class (an invalid value), the OpenVMS system will crash with an INVEXCEPTN bugcheck. o LASTDRIVER crashes when it receives a run message in circuit stalled. -- COVER LETTER -- Page 3 16 September 1999 o 1. Typing a CTRL/Y at a certain instance could cause an IO$_PACKACK function to a MAD device to be canceled. The result could eventually be that the system crashes in I/O post processing. 2. LADCP BIND/UNIT=x will cause a duplicate UCB unit number to be generated if the unit number specified is greater then the seed unit number. This problem can happen for both DADDRIVER and MADDRIVER. o When booting from a CD, the InfoServer client can't be started. o InfoServer Client STOP/START bugs were fixed. o The system crashes in LTDRIVER when SSB is deleted prematurely while an UNLOAD is in progress. o The LASTDRIVER image crashes when it receives an Advertisement (ADV) or Solicit (SOL) message with a negative message length. o An overrun error on magtape occurs if the record size is greater then 65024. o In the past, BIND/TAPE/NOPERMANENT "tape_service" created a MADx device UCB that could be deleted once the UCB reference count went to zero. Problems occurred when the UCB was deleted due to the use of the /NOPERMANENT qualifier, that is multivolume BACKUP. Note: A MAD device is a tape device that is attached to an InfoServer. 7 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: INSTALL_2 : To be installed by all customers using the following feature(s): Infoserver -- COVER LETTER -- Page 4 16 September 1999 8 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 VAXLAD02_062 [location of the saveset] The saveset location may be a tape drive, CD, or a disk directory that contains the kit saveset. The images in this kit will not take effect until the system is rebooted. If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. Copyright (c) Compaq Computer Corporation, 1999 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 Compaq Computer Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Compaq Computer 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 COMPAQ 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.