**************************** ECO SUMMARY INFORMATION **************************** Release Date: 19-OCT-2004 Kit Name: DEC-AXPVMS-VMS731_SHADOWING-V0300--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-1 Approximate Kit Size: 2240 blocks Installation Rating: INSTALL_2 Required Features: Shadowing Superseded Kits: VMS731_SHADOWING-V0200 Mandatory Kit Dependencies: VMS731_UPDATE-V0400 VMS731_PCSI-V0200 Optional Kit Dependencies: None. VMS731_SHADOWING-V0300.PCSI-DCX_AXPEXE Checksum: 3404611191 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS731_SHADOWING-V0300 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 1 KIT NAME: VMS731_SHADOWING-V0300 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2: To be installed by all customers using the following feature(s): - Shadowing This 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) 2.2 Reboot Requirement: Reboot Required. HP strongly recommends that a reboot is performed immediately after kit installation to avoid system instability. 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. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.3-1 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - VMS731_SHADOWING-V0200 Page 2 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS731_PCSI-V0200 - VMS731_UPDATE-V0400 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None. 5 FILES PATCHED OR REPLACED: o [SYSEXE]SHADOW_SERVER.EXE (new image) Image Identification Information image name: "SHADOW_SERVER" image file identification: "X-13" image file build identification: "XA2Q-0060030020" link date/time: 16-SEP-2004 15:26:36.76 linker identification: "A11-50" Overall Image Checksum: 1276100377 o [SYS$LDR]SYS$SHDRIVER.EXE (new image) Image Identification Information image name: "SYS$SHDRIVER" image file identification: "X-3" image file build identification: "XA2Q-0060030020" link date/time: 16-SEP-2004 15:26:38.80 linker identification: "A11-50" Overall Image Checksum: 1527715988 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS731_SHADOWING-V0300 KIT Page 3 6.1 New functionality addressed in this kit None. 6.2 Problems addressed in this kit 6.2.1 Second system to mount Dissimilar Device Shadowset gets DEVBUSYINSET error 6.2.1.1 Problem Description: The second system to try and mount a Dissimilar Device Shadowset will get a DEVBUSYINSET error from the mount command. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.2.1 CLD(s) 70-3-8093 6.2.1.2.2 QAR(s) None. 6.2.1.3 Problem Analysis: The wrong mode is used to update the Member Of Set lock value block. 6.2.1.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.1.5 Work-arounds: None. Page 4 6.2.2 Write not completed to all members of the shadow set 6.2.2.1 Problem Description: On shadow sets, where write logging was being used for minimerge recovery operations, a condition existed where a write might not be completed to all members of the shadow set. The write, making it to at least one member, was logged but the shadowing driver did not recognize that it was logged. As a result, this difference in the data on the shadow set members was not corrected during a controller-based minimerge. The set would stay in the condition where some members had the written data while others would not. The analyze disk shadow utility would detect this discrepancy. This problem only occurred when using controller-based write logging. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE - [SYS$LDR]SYS$SHDRIVER_MON.EXE 6.2.2.2 CLDs, and QARs reporting this problem: 6.2.2.2.1 CLD(s) None. 6.2.2.2.2 QAR(s) 75-80-298 6.2.2.3 Problem Analysis: The CNID field, used to determine whether or not the failing node had an outstanding write to a set was being cleared. If the node failure occurred on a system with a CNID other than zero, the write logging merge would not work since it would appear that the system had no writes. 6.2.2.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 Page 5 6.2.2.5 Work-arounds: None. 6.2.3 PCSI UNDO of kit not possible 6.2.3.1 Problem Description: Due to a typographical error in a command file used during a PCSI UNDO of the kit, the VMS731_SHADOWING-V0200 kit could not be removed with a PRODUCT UNDO PATCH command. This kit includes a corrected COM file. Note that, installing this kit will not fix the problem on the system caused by the VMS731_SHADOWING-V0200 kit. In order to eliminate the kit removal failure you will need to take the following steps to correct the PREUNDO.COM file. *** WARNING *** Before making any changes to a PREUNDO.COM FILE, copy the PREUNDO.COM file to another filename, e.g. PREUNDO.COM_BACKUP. If there are problems executing any of the following steps, this backup copy can be used to start over. *************** To find PREUNDO.COM files that have the problem: 1. Search for PCSI$UNDO directories that have the defective line: $ search SYS$SYSDEVICE:[PCSI$UNDO_*.SYSUPD]PREUNDO.COM - _$ "$ REBOOT" This will give a list similar to the following: $ search SYS$SYSDEVICE:[PCSI$UNDO_*.SYSUPD]PREUNDO.COM - _$ "$REBOOT" ****************************** SYS$SYSDEVICE:[PCSI$UNDO_007.SYSUPD]PREUNDO.COM;1 $ Reboot: ****************************** SYS$SYSDEVICE:[PCSI$UNDO_008.SYSUPD]PREUNDO.COM;1 $ Reboot $ Note that in the second entry the "$ Reboot" line is missing a ":". This is the problem that is causing the UNDO error. Since this error occurred in several Page 6 kits, there may be more than one result that is missing the ":". 2. Edit any PREUNDO.COM file that has the error by adding the ":". Specifically, change "$ REBOOT" to "$ REBOOT:". Alternately, the line can be commented out by adding a "!", e.g. "$!REBOOT. 3. After editing the PREUNDO.COM file, there will be two versions of the PREUNDO.COM file. If you have not heeded the above warning to create a backup copy of the file, rename the original version of the file (PREUNDO.COM;1) to something other than PREUNDO.COM, e.g. PREUNDO.COM_OLD. Otherwise, delete PREUNDO.COM;1 4. Rename the new version of the file (PREUNDO.COM;2) to PREUNDO.COM;1 5. Once the PREUNDO.COM file is successfully edited and renamed, the old file that was renamed in step 3 and/or the backup version can be deleted. Kits that had the UNDO problem will now be able to be successfully removed. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE - [SYS$LDR]SYS$SHDRIVER_MON.EXE 6.2.3.2 CLDs, and QARs reporting this problem: 6.2.3.2.1 CLD(s) None. 6.2.3.2.2 QAR(s) 75-80-298 6.2.3.3 Problem Analysis: The CNID field, used to determine whether or not the failing node had an outstanding write to a set was being cleared. If the node failure occurred on a system with a CNID other than zero, the write logging merge would not work since it would appear that the system had no writes. Page 7 6.2.3.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.3.5 Work-arounds: None. 7 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed in previously released VMS732_SHADOWING kits can be found in the following files: o [SYSLIB]VMS731_SHADOWING-V0200.RELEASE_NOTES o [SYSLIB]VMS731_SHADOWING-V0100.RELEASE_NOTES 8 INSTALLATION INSTRUCTIONS 8.1 Compressed File This kit is provided as a DCX compressed kit. To expand this file to the installable PCSI file, run the file with a RUN file_name command. When the file is run you will see the following output: $ RUN VMS732_SHADOWING-V0200.PCSI-DCX_AXPEXE FTSV DCX auto-extractible compressed file for OpenVMS (AXP) FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT Copyright (c) Digital Equipment Corp. 1993 Options: [output_file_specification] [input_file_specification] The decompressor needs to know the filename to use for the decompressed file. If you don't specify any, it will use the original name of the file before it was compressed, and create it in the current directory. If you specify a directory name, the file will be created in that directory. Decompress into (file specification): If you want the file to be expanded into a different directory, enter the directory specification. DO NOT enter a new file name. The expanded file must retain the original name. If you want to expand the file via batch, the command file must contain an answer to the Decompress into "(file specification)" question, either a or an alternate directory specification Page 8 8.2 Installation Command Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS731_SHADOWING /SAVE_RECOVERY_DATA [/SOURCE=location of Kit] The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. Using this qualifier will allow easy removal of the kit from the system in the event of problems. The kit location may be a tape drive, CD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 8.3 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following logical name definitions and commands: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE o To avoid the REBOOT question, define the following: $ DEFINE/SYS NO_ASK$REBOOT TRUE o To save replaced files as *.*_OLD define the following logical name as YES. If you do not wish to save replaced files, define the logical name as NO. Note that if you use the /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT INSTALL command all replaced files will be saved as part of that operation. There is no need to also save files as *.*_OLD: $ DEFINE/JOB ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V3.0/SAVE_RECOVERY_DATA Page 9 o De-assign the logical names assigned For example, a sample command file to install the VMS731_SHADOWING-V0300 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS731_SHADOWING/PRODUCER=DEC/BASE=AXPVMS- /VER=V3.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2004 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. 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 HP 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.