**************************** ECO SUMMARY INFORMATION **************************** Release Date: 12-SEP-2005 Kit Name: DEC-AXPVMS-VMS82A_SHADOWING-V0100--4.PCSI Kit Applies To: OpenVMS ALPHA V8.2 Approximate Kit Size: 2320 blocks Installation Rating: INSTALL_2 Required Features: SHADOWING Reboot Required: Yes - rolling reboot Superseded Kits: None Mandatory Kit Dependencies: None Optional Kit Dependencies: None VMS82A_SHADOWING-V0100.PCSI-DCX_AXPEXE Checksum: 2016391429 DEC-AXPVMS-VMS82A_SHADOWING-V0100--4.PCSI Checksum: 2458775866 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS82A_SHADOWING-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : To be installed by all customers using the following feature(s): - SHADOWING 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 V8.2 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - None Page 2 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 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS82A_SHADOWING-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Suspending SHADOW_SERVER Process Hangs All Mounts and Dismounts 5.2.1.1 Problem Description: Suspending the SHADOW_SERVER process causes all mounts and dismounts of shadow sets to hang for as long as the SHADOW_SERVER is suspended. Images Affected: - [SYSEXE]SHADOW_SERVER.EXE 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) None. 5.2.1.2.2 QAR(s) None. 5.2.1.3 Problem Analysis: Prior to the Host Based Mini Merge (HBMM) version of HBVS, the SHADOW_SERVER process dealt with shadow set merges and member copies and not much else. As such, a system manager could suspend the shadow server if they wished to temporarily suspend all shadow set merges and copies on this node. However, in the HBMM version of Host Based Volume Shadowing (HBVS), the SHADOW_SERVER has additional responsibilities. One of these responsibilities is to play an active role in the mount Page 3 and dismount of every shadow set, even if HBMM is not in use. This change prevents suspending the shadow server. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.1.5 Work-arounds: None. 5.2.2 XQPERR System Crash 5.2.2.1 Problem Description: The system can crash with an XQPERR bugcheck. Crashdump Summary Information: ------------------------------ Bugcheck Type: XQPERR, Error detected by file system XQP Current Process: BPCD_BG2900 Failing PC: FFFFFFFF.8023C8A8 F11BXQP+128A8 Failing PS: 30000000.00000000 Module: F11BXQP (Link Date/Time: 17-MAR-2004 12:16:07.28) Offset: 000128A8 Stack Pointers: KSP = 00000000.7AF20E30 ESP = 00000000.7FFA6000 SSP = 00000000.7FFAC100 USP = 00000000.7AD6BD30 Failing Instruction: F11BXQP+128A8: BUGCHK Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 5.2.2.2 CLDs, and QARs reporting this problem: Page 4 5.2.2.2.1 CLD(s) 70-3-8231,QXCM1000211838 5.2.2.2.2 QAR(s) None. 5.2.2.3 Problem Analysis: When a member is being removed from a shadowset, it is possible for an IO to get queued if the SHD bit was clear but the MNT bit was still set. This results in the crash because the Volume Control block (VCB) is already gone. 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.2.5 Work-arounds: None. 5.2.3 Performance Enhancement 5.2.3.1 Problem Description: Increase read I/O throughput by checking to see if user read I/O must be merged. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) None. 5.2.3.2.2 QAR(s) None. Page 5 5.2.3.3 Problem Analysis: While a virtual unit is in a merging state, all user read I/O must be merged, unless it is in an area of the volume that has already been merged. This is true for virtual units that are doing or are going to do either a full merge or a mini merge. This fix checks if the system is a Host Based Mini Merge bitmap master. If it is, the extent of the I/O in the bitmap will be checked to see if the user read must be merged. Eliminating a merge of a user read I/O will increase read I/O throughput. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.3.5 Work-arounds: None. 5.2.4 Cannot Perform I/O to Virtual Unit 5.2.4.1 Problem Description: Systems in a cluster may not be able perform I/O to a virtual unit that is in mount verification. This problem only exists for virtual units that are ODS-5. Mount Verification can be aborted if this condition occurs by using either of the following commands: o $ SET SHADOW/ABORT_VIRTUAL_UNIT DSAn: o $ SET DEVICE/ABORT_VIRTUAL_UNIT DSAn: Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) None. Page 6 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: If a virtual unit, that is also an ODS-5 volume, is mounted on more than one system in the cluster, and the system manager changes the volume label, that change will modify the FILES-11 structures on the volume and the FILES-11 data structures in the memory of the system upon which the SET VOLUME /LABEL command was issued. However the memory Files-11 data structure on all the other systems are not updated. The virtual unit can continue to be used on all systems, until that virtual unit goes into Mount Verification. The system that issued the SET VOLUME /LABEL command will correctly exit Mount Verification. The other systems will serially remove shadow set members for each Mount Verification event. The OPCOM message at member removal will include: "(path1, path2) is an incorrect shadow set member volume." Once the shadow set is down to one member,the virtual unit will remain in Mount Verification, even after the Mount Verification timer has expired. While the virtual unit is in this state, all other systems may have difficulty doing I/O to that virtual unit. 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.4.5 Work-arounds: None. 5.2.5 OPCOM Messages For Copy or Merge Operations Not Clear 5.2.5.1 Problem Description: OPCOM messages are not clear on whether a copy or merge operation is starting or resuming. Images Affected: - [SYSEXE]SHADOW_SERVER.EXE Page 7 5.2.5.2 CLDs, and QARs reporting this problem: 5.2.5.2.1 CLD(s) None. 5.2.5.2.2 QAR(s) None. 5.2.5.3 Problem Analysis: See problem description. 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.5.5 Work-arounds: None. 5.2.6 Mount Verification Messages Erroneously Broadcast 5.2.6.1 Problem Description: Mount verification messages are broadcast for operations that should not have caused them. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 5.2.6.2 CLDs, and QARs reporting this problem: 5.2.6.2.1 CLD(s) QXCM1000197287 5.2.6.2.2 QAR(s) None. Page 8 5.2.6.3 Problem Analysis: State logic loses synchronization by not accounting for all the error codes that shadowing uses. 5.2.6.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.6.5 Work-arounds: None. 5.2.7 SHOW SHADOW Command Not Displaying Dis-Similar Device Shadowing 5.2.7.1 Problem Description: The SHOW SHADOW command is not displaying dis-similar device shadowing in the enhanced features field. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE 5.2.7.2 CLDs, and QARs reporting this problem: 5.2.7.2.1 CLD(s) QXCM1000231786,70-3-8328 5.2.7.2.2 QAR(s) None. 5.2.7.3 Problem Analysis: The SHOW SHADOW DSAn: command is used to display the "Enhanced Shadowing Features in use:" on that DSA device. When a system boots using a Host Based Volume Shadowing (HBVS) system disk that contains multiple shadow set members that require DDS to be set as a virtual unit (VU) characteristic, that VU characteristic is not being set. Page 9 5.2.7.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.7.5 Work-arounds: None. 6 FILES PATCHED OR REPLACED: o [SYSEXE]SHADOW_SERVER.EXE (new image) Image Identification Information image name: "SHADOW_SERVER" image file identification: "X-23" image file build identification: "XAJT-0070050004" link date/time: 9-MAY-2005 18:55:55.25 linker identification: "A11-50" Overall Image Checksum: 2669477317 o [SYS$LDR]SYS$SHDRIVER.EXE (new image) Image Identification Information image name: "SYS$SHDRIVER" image file identification: "X-5" image file build identification: "XAJT-0070050004" link date/time: 9-MAY-2005 18:55:56.41 linker identification: "A11-50" Overall Image Checksum: 2919416703 7 INSTALLATION INSTRUCTIONS 7.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: Page 10 o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer NO for each image that you want to keep. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 7.2 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 VMS82A_SHADOWING-V0100.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 7.3 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 VMS82A_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. Page 11 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. 7.4 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=V1.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS82A_SHADOWING-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS82A_SHADOWING/PRODUCER=DEC/BASE=AXPVMS- /VER=V1.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT Page 12 $! $ exit $! 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2005 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.