ECO NUMBER: ALPMSCP02_062 PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: ALPMSCP02_062 2 KITS SUPERSEDED BY THIS KIT: ALPMSCP01_062 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this kit: ALPCLUSIO01_062 3.2 In order to receive the 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 Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 4.2 Files patched or replaced: o [SYS$LDR]TMSCP.EXE (new image) o [SYS$LDR]MSCP.EXE (new image) 5 PROBLEMS ADDRESSED IN 6 PROBLEMS ADDRESSED IN ALPMSCP02_062 KIT o The ALPMSCP01_062 remedial kit required that the ALPCLUSIO01_062 kit be installed. If the user tried to install the ALPMSCP01_062 kit on a system that had both the ALPCLUSIO01_062 and OpenVMS Alpha Y2K remedial kits installed, the ALPMSCP01_062 kit did not recognize that the ALPCLUSIO01_062 kit had been installed. This caused the ALPMSCP01_062 installation to fail. -- COVER LETTER -- Page 2 11 February 1998 There are no new ECO problem corrections in this kit. If you have installed the ALPMSCP01_062 remedial kit, you do not need to install the ALPMSCP02_062 remedial kit. 7 PROBLEMS ADDRESSED IN ALPMSCP01_062 KIT o A Cache Data Lost error is detected in the tape subsystem due to a hardware related problem. A GUS end message is returned to the client with an end message status of 08 (data error). This status was set up in routine SEND_END in TMSCP. Since this is not a valid status for a GUS, the client TUDRIVER rejects the invalid status, logs an error and then calls TU$RE_SYNCH which breaks the connection. For the same Cache Data Lost error, if an AVAILABLE command is issued, the controller should return CDL until the host clears the condition in the controller. TUDRIVER in the server, upon receipt of an end message for AVAILABLE which indicates CDL, will then issue another AVAILABLE with the clear cache data lost modifier set in the packet. The only status that is checked on the receipt of this end message is for PRESE which will return SS$_DATALOST. Anything else returns SS$_DATALOST. o System crash (INVEXCEPTN) when TMSCP does not get a message buffer during configuration time when a connection to MSCP$TAPE is broken. o An inconsistent transfer count occurs when encountering a forced error on a drive. A drive directly attached (or HSx served) reports a different transfer count from the same drive served via the MSCP server. Code that attempts to determine the LBN of a forced error block by looking at the byte count in the IOST/IOSB will arrive at different values on the same drive when directly accessed or MSCP served. 8 PROBLEMS ADDRESSED IN ALPMSCP01_070 KIT o The problem occurs when ERASE commands with history logging are issued on MSCP clients for large numbers of blocks to MSCP devices served by an OpenVMS MSCP server. On an Alpha server, an "Illegal Command" entry will be posted in the system error log and the command will be aborted. Typically, if the affected device is part of a shadow set, the set will enter mount verification and the I/O request will eventually fail with a "Fatal Controller Error". On a VAX server, no immediate problem is noticed but the possibility of corrupting a shadow set exists should there be a failure during the execution of the ERASE command and a mini-merge is performed when the set -- COVER LETTER -- Page 3 11 February 1998 becomes available. o A satellite node will not boot after a preferpath/forcepath command is issued on the server. o Word instructions are used to reference a byte field. 9 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: INSTALL_2 : To be installed by all customers using the following feature(s): Customers who are MSCP serving disks and tapes need to install this kit. 10 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 ALPMSCP02_062 [location of the saveset] The saveset location may be a tape drive, 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 VMS 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) 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. -- COVER LETTER -- Page 4 11 February 1998 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.