**************************** ECO SUMMARY INFORMATION **************************** Release Date: 23-SEP-2004 Kit Name: DEC-AXPVMS-VMS732_HBMM-V0200--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-2 Approximate Kit Size: 23904 blocks Installation Rating: INSTALL_2 Required Features: Customer's that have installed the VMS732_HBMM-V0100 kit Host Based Mini-Merge (HBMM) Superseded Kits: VMS732_HBMM-V0100 Mandatory Kit Dependencies: VMS732_UPDATE-V0200 VMS732_PCSI-V0100 Optional Kit Dependencies: None VMS732_HBMM-V0200.PCSI-DCX_AXPEXE Checksum: 1871146026 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS732_HBMM-V0200 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-2 1 KIT NAME: VMS732_HBMM-V0200 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2: To be installed by all customers using the following feature(s): - Customer's that have installed the VMS732_HBMM-V0100 kit - Host Based Mini-Merge (HBMM) 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-2 2.4 New functionality or new hardware support provided: Yes. 3 KITS SUPERSEDED BY THIS KIT: - VMS732_HBMM-V0100 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: - VMS732_PCSI-V0100 - VMS732_UPDATE-V0200 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 [SYSMSG]CLIUTLMSG.EXE (new image) Image Identification Information image name: "CLIUTLMSG" image file identification: "X-3" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:09.45 linker identification: "A11-50" Overall Image Checksum: 917747862 o [SYSEXE]DCL.EXE (new image) Image Identification Information image name: "DCL" image file identification: "X-37" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:23.58 linker identification: "A11-50" Overall Image Checksum: 4268324345 o [SYSLIB]INIT$SHR.EXE (new image) Image Identification Information image name: "INIT$SHR" image file identification: "X-6" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:00:59.83 linker identification: "A11-50" Overall Image Checksum: 1732365509 Page 3 o [SYSEXE]INIT.EXE (new image) Image Identification Information image name: "INIT" image file identification: "X-17" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:26.13 linker identification: "A11-50" Overall Image Checksum: 3368565897 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information image name: "IO_ROUTINES" image file identification: "X-4" image file build identification: "0060111002" link date/time: 10-SEP-2004 10:51:01.19 linker identification: "A11-50" Overall Image Checksum: 969252971 o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) Image Identification Information image name: "IO_ROUTINES_MON" image file identification: "X-4" image file build identification: "0060111002" link date/time: 10-SEP-2004 10:51:03.78 linker identification: "A11-50" Overall Image Checksum: 1400873722 o [SYSEXE]LANACP.EXE (new image) Image Identification Information image name: "LANACP" image file identification: "X-36" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:43.15 linker identification: "A11-50" Overall Image Checksum: 810370841 o [SYSLIB]LIBRTL.EXE (new image) Image Identification Information image name: "LIBRTL" image file identification: "X01-001" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:00:49.35 linker identification: "A11-50" Overall Image Checksum: 3095536194 Page 4 o [SYSLIB]MOUNTSHR.EXE (new image) Image Identification Information image name: "MOUNTSHR" image file identification: "X-6" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:01:00.12 linker identification: "A11-50" Overall Image Checksum: 409538261 o [SYSLIB]NISCS_LAA.EXE (new image) Image Identification Information image name: "NISCS_LAA" image file identification: "X-12A1" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:22.22 linker identification: "A11-50" Overall Image Checksum: 2990762292 o [SYSLIB]SDA$SHARE.EXE (new image) Image Identification Information image name: "SDA$SHARE" image file identification: "X-2" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:33.86 linker identification: "A11-50" Overall Image Checksum: 2753292455 o [SYSEXE]SETSHOSHADOW.EXE (new file) Image Identification Information image name: "SETSHOSHADOW" image file identification: "X-02" image file build identification: "0060111002" link date/time: 10-SEP-2004 11:16:28.99 linker identification: "A11-50" Overall Image Checksum: 2279678995 o [SYSEXE]SHADOW_SERVER.EXE (new image) Image Identification Information image name: "SHADOW_SERVER" image file identification: "X-21" image file build identification: "0060111002" link date/time: 23-AUG-2004 15:45:22.27 linker identification: "A11-50" Overall Image Checksum: 3373532833 Page 5 o [SYSEXE]SHOW.EXE (new image) Image Identification Information image name: "SHOW" image file identification: "X-11A1" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:04:04.93 linker identification: "A11-50" Overall Image Checksum: 136115119 o [SYSEXE]SMISERVER.EXE (new image) Image Identification Information image name: "SMISERVER" image file identification: "X01-15" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:01.52 linker identification: "A11-50" Overall Image Checksum: 2526367050 o [SYS$LDR]SYS$BASE_IMAGE.EXE (new image) Image Identification Information image name: "SYS$BASE_IMAGE" image file identification: "ALPHA XAG8-O2L" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:00:42.75 linker identification: "A11-50" Overall Image Checksum: 4184765337 o [SYSLIB]SYS$PUBLIC_VECTORS.EXE (new image) Image Identification Information image name: "SYS$PUBLIC_VECTORS" image file identification: "X-104A1A1" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:00:39.26 linker identification: "A11-50" Overall Image Checksum: 1911123727 o [SYS$LDR]SYS$SHDRIVER.EXE (new image) Image Identification Information image name: "SYS$SHDRIVER" image file identification: "X-4" image file build identification: "0060111002" link date/time: 21-SEP-2004 13:19:01.33 linker identification: "A11-50" Overall Image Checksum: 3971743417 Page 6 o [SYSLIB]SYS$SSISHR.EXE (new image) Image Identification Information image name: "SYS$SSISHR" image file identification: "V1.0" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:00:44.42 linker identification: "A11-50" Overall Image Checksum: 870109665 o [SYSEXE]SYSBOOT.EXE (new image) Image Identification Information image name: "SYSBOOT" image file identification: "X-114" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:33.43 linker identification: "A11-50" Overall Image Checksum: 521370810 o [SYSEXE]SYSGEN.EXE (new image) Image Identification Information image name: "SYSGEN" image file identification: "X-5" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:27.73 linker identification: "A11-50" Overall Image Checksum: 893621626 o [SYS$LDR]SYSGETSYI.EXE (new image) Image Identification Information image name: "SYSGETSYI" image file identification: "X-7" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:10.11 linker identification: "A11-50" Overall Image Checksum: 646603970 o [SYSEXE]SYSINIT.EXE (new image) Image Identification Information image name: "SYSINIT" image file identification: "X-100A1" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:29.05 linker identification: "A11-50" Overall Image Checksum: 104562840 Page 7 o [SYSEXE]SYSMAN.EXE (new image) Image Identification Information image name: "SYSMAN" image file identification: "X01-22" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:01.14 linker identification: "A11-50" Overall Image Checksum: 2152225299 o [SYSMSG]SYSMSG.EXE (new image) Image Identification Information image name: "SYSMSG" image file identification: "X-9" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:06.58 linker identification: "A11-50" Overall Image Checksum: 538524639 o [SYSEXE]VMOUNT.EXE (new image) Image Identification Information image name: "VMOUNT" image file identification: "X-10" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:02:26.51 linker identification: "A11-50" Overall Image Checksum: 283586002 o [SYSEXE]WBM.EXE (new image) Image Identification Information image name: "WBM" image file identification: "X-01" image file build identification: "0060111002" link date/time: 20-AUG-2004 17:04:06.22 linker identification: "A11-50" Overall Image Checksum: 193861604 o [SYSMGR]CLUSTER_CONFIG.COM (new file) o [SYSMGR]CLUSTER_CONFIG_LAN.COM (new file) o [SYSHLP]HBMM_PRO_V732.HTML (new file) o [SYSHLP]HBMM_PRO_V732_001.HTML (new file) o [SYSHLP]HBMM_PRO_V732_002.HTML (new file) o [SYSHLP]HBMM_PRO_V732_003.HTML (new file) Page 8 o [SYSHLP]HBMM_PRO_V732_004.HTML (new file) o [SYSHLP]HBMM_PRO_V732_005.HTML (new file) o [SYSHLP]HBMM_PRO_V732_CONTENTS.HTML (new file) o [SYS$LDR]IODEF.STB (new file) o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYS$LDR]IO_ROUTINES_MON.STB(new file) o [SYSUPD]SET.CLD (new file) o [SYSUPD]SET.HLP (new file) o [SYSEXE]SHADOW_SERVER.STB (new file) o [SYSUPD]SHOW.CLD (new file) o [SYSUPD]SHOW.HLP (new file) o [SYS$LDR]SYS$SHDRIVER.STB (new file) o [SYSHLP]SYSGEN.HLB (new file) o [SYS$LDR]SYSGETSYI.STB (new file) o [SYSHLP]SYSMANHELP.HLB (new file) o [SYS$STARTUP]VMS$CONFIG-050_SHADOW_SERVER.COM (new file) o [SYSMGR]VMS$IMAGES_MASTER.DAT (new file) o [SYS$STARTUP]VMS$VMS.DAT (new file) o [SYSHLP]VS_HBMM_VMS732-V0100.PDF (new file) o [SYSHLP]VS_HBMM_VMS732-V0100.TXT(new file) 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS732_HBMM-V0200 KIT 6.1 New functionality addressed in this kit 6.1.1 HP OpenVMS Host-Based Minimerge (HBMM) Version 7.3-2 Page 9 6.1.1.1 Functionality Description: This kit provides Host-Based Minimerge (HBMM) functionality for OpenVMS Alpha Version 7.3-2. The Host-Based Minimerge (HBMM) kit contains two new optional capabilities for OpenVMS Volume Shadowing: o Minimerge support for shadow sets that consist of Fibre Channel or SCSI disks. Minimerge is significantly faster than a full merge operation because it merges only those areas of the virtual unit where write activity is known to have occurred. o Allows the user to assign a unique priority to all virtual units, which will be used to select the order that virtual units are selected when a system crashes or a virtual unit is aborted in a cluster. Refer to the OpenVMS Volume Shadowing Support for Host-Based Minimerge (HBMM) manual, which is included in this remedial kit, for further information on HBMM. 6.1.1.2 Documentation The OpenVMS Volume Shadowing Support for Host-Based Minimerge (HBMM) manual is included in the kit in Adobe Acrobat, text, and HTML formats. The files VS-HBMM-VMS732-V0100.PDF, VS-HBMM-VMS732-V0100.TXT, and HBMM_PRO*.HTML are copied to SYS$HELP when the kit is installed. HP recommends that users extract the user manual from the kit and review it before installing the HBMM kit. Once the compressed kit is expanded, user manual files can be extracted from the PCSI kit via the following command: $ PRODUCT EXTRACT FILE VMS732_HBMM/SELECT= file_name Please review Chapter 2 of the OpenVMS Volume Shadowing Support for Host-Based Minimerge user manual for the release notes. When the HBMM kit is installed, online DCL HELP is updated, and includes help on the new, optional qualifiers added to the SET SHADOW and SHOW SHADOW commands. Note that the user manual references the VMS732_HBMM-V0100 kit. The user manual that is included in the VMS732_HBMM-V0200 kit is unchanged from the manual that was included in the superseded VMS732_HBMM-V0100 kit. The features described by this manual are provided by either of these kits. This means that when the manual specifically refers to the VMS732_HBMM-V0100 kit by name, as it does in section 1.1, this information applies to the VMS732_HBMM-V0200 kit as well. Page 10 6.1.1.3 Remedial Kits The VMS732_HBMM-V0200 kit will be included in the future VMS732_UPDATE-V0300 remedial kit. Once VMS732_HBMM-V0200 is installed, you will not be able to install standard versions of future remedial kits that have images in common with the HBMM kit until you install the VMS732_UPDATE-V0300 kit. Remedial kits affected will perform an HBMM check and will not install if HBMM is present. Until the VMS732_UPDATE-V0300 kit ships (anticipated ship date October 2004) HBMM-specific remedial kits will be provided for facilities that have images in common with HBMM. OpenVMS Engineering anticipates a minimal number of HBMM-specific remedial kits will be needed during this time frame. 6.2 Problems addressed in this kit 6.2.1 %SYSTEM-F-IVDEVNAM error on some SET SHADOW commands 6.2.1.1 Problem Description: If a shadow set member device name is specified with the SET SHADOW command, the command will fail with the following error: %SYSTEM-F-IVDEVNAM, invalid device name This failure occurs even though it may be valid or necessary to specify a shadow set member device name with the SET SHADOW command qualifier that was used. For example: $ SET SHADOW $1$DGA107:/COPY_SOURCE %SYSTEM-F-IVDEVNAM, invalid device name The qualifiers that should allow a shadow set member device name are: /COPY_SOURCE, /FORCE_REMOVAL, /MEMBER_TIMEOUT, /READ_COST, and /SITE. Commands that take a shadow set name work correctly. Images Affected: - [SYSEXE]SETSHOSHADOW.EXE Page 11 6.2.2 Handling of a $GETDVI item code could result in a system crash 6.2.2.1 Problem Description: A problem has been corrected in the handling of a $GETDVI item code that could result in a system crash under some circumstances. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB 6.2.3 System Crash 6.2.3.1 Problem Description: A problem has been corrected in the handling of some patterns of intermittent recoverable errors followed by nonrecoverable SS$_DRVERR or SS$_CTRLERR errors on the last remaining member of a shadow set thats undergoing mount verification. This problem could lead to a system crash under some circumstances. Images Affected: - [SYS$LDR]SYS$SHDRIVER.EXE - [SYS$LDR]SYS$SHDRIVER.STB 7 PROBLEMS ADDRESSED IN THE VMS732_HBMM-V0100 KIT 7.1 Controller - Based Minimerge Problem 7.1.1 Problem Description: The HBMM kit includes a fix to a controller-based minimerge problem that was introduced in an earlier version of Volume Shadowing for OpenVMS. You can disregard the advisory on the Controller-Based Minimerge problem, if you have installed the Host-Based Minimerge (HBMM) kit. Images Affected: Page 12 - [SYS$LDR]SYS$SHDRIVER.EXE 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_HBMM-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 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 VMS732_HBMM /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. Page 13 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=V2.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS732_HBMM kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS732_HBMM/PRODUCER=DEC/BASE=AXPVMS- /VER=V2.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit Page 14 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.