**************************** ECO SUMMARY INFORMATION **************************** Release Date: 8-JUN-2004 Kit Name: DEC-AXPVMS-VMS722_FIBRE_SCSI-V0600--4.PCSI Kit Applies To: OpenVMS ALPHA V7.2-2 Approximate Kit Size: 16928 blocks Installation Rating: INSTALL_2 Required Features: Fibrechannel SCSI Superseded Kits: VMS722_FIBRE_SCSI-V0400 Mandatory Kit Dependencies: VMS722_UPDATE-V0100 VMS722_PCSI-V0100 Optional Kit Dependencies: None. VMS722_FIBRE_SCSI-V0600.PCSI-DCX_AXPEXE Checksum: 2193609738 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS722_FIBRE_SCSI-V0600 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 1 KIT NAME: VMS722_FIBRE_SCSI-V0600 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2: To be installed by all customers using the following feature(s): - Fibrechannel - SCSI 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.2-2 2.4 New functionality or new hardware support provided: Yes. 3 KITS SUPERSEDED BY THIS KIT: - VMS722_FIBRE_SCSI-V0400 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: - VMS722_PCSI-V0100 - VMS722_UPDATE-V0100 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 [SYSHLP.UNSUPPORTED]FC$CP.EXE (new image) Image Identification Information image name: "FC$CP" image file identification: "X-2" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:06:47.97 linker identification: "A11-39" Overall Image Checksum: 3785338613 o [SYSLIB]FC$SDA.EXE (new image) Image Identification Information image name: "FC$SDA" image file identification: "X-6A3A1B3" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:06:46.29 linker identification: "A11-39" Overall Image Checksum: 1580352204 o [SYSLIB]IOGEN$FIBRE_CONFIG.EXE (new image) Image Identification Information image name: "IOGEN$FIBRE_CONFIG" image file identification: "X-10A2A1" image file build identification: "X71Z-0050170000" link date/time: 21-AUG-2002 14:04:09.02 linker identification: "A11-39" Overall Image Checksum: 3281952358 Page 3 o [SYSHLP.UNSUPPORTED]MSA_UTIL.EXE (new image) Image Identification Information image name: "MSA_UTIL" image file identification: "X-2" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:06:49.59 linker identification: "A11-39" Overall Image Checksum: 1006911061 o [SYSLIB]SMI$OBJSHR.EXE (new image) Image Identification Information image name: "SMI$OBJSHR" image file identification: "X40-A8" image file build identification: "X71Z-0050170008" link date/time: 19-FEB-2003 10:20:57.46 linker identification: "A11-39" Overall Image Checksum: 928280880 o [SYS$LDR]SYS$DKDRIVER.EXE (new image) Image Identification Information image name: "SYS$DKDRIVER" image file identification: "X-12" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:03:10.83 linker identification: "A11-39" Overall Image Checksum: 984927270 o [SYS$LDR]SYS$FGEDRIVER.EXE (new image) Image Identification Information image name: "SYS$FGEDRIVER" image file identification: "X-26A22A1A3A14" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:06:20.15 linker identification: "A11-39" Overall Image Checksum: 490995221 o [SYS$LDR]SYS$GKDRIVER.EXE (new image) Image Identification Information image name: "SYS$GKDRIVER" image file identification: "X-40A2" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:03:47.18 linker identification: "A11-39" Overall Image Checksum: 1268919948 Page 4 o [SYS$LDR]SYS$MKDRIVER.EXE (new image) Image Identification Information image name: "SYS$MKDRIVER" image file identification: "X-12" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:03:32.04 linker identification: "A11-39" Overall Image Checksum: 3181539319 o [SYS$LDR]SYS$PGADRIVER.EXE (new image) Image Identification Information image name: "SYS$PGADRIVER" image file identification: "X-35A5A1A7" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:06:05.49 linker identification: "A11-39" Overall Image Checksum: 209385484 o [SYS$LDR]SYS$PKADRIVER.EXE (new image) Image Identification Information image name: "SYS$PKADRIVER" image file identification: "X-12A2" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:05:47.28 linker identification: "A11-39" Overall Image Checksum: 809596921 o [SYS$LDR]SYS$PKCDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKCDRIVER" image file identification: "X-3" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:04:01.76 linker identification: "A11-39" Overall Image Checksum: 3712045303 o [SYS$LDR]SYS$PKEDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKEDRIVER" image file identification: "X-3" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:04:26.37 linker identification: "A11-39" Overall Image Checksum: 1799462221 Page 5 o [SYS$LDR]SYS$PKJDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKJDRIVER" image file identification: "X-3" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:04:37.46 linker identification: "A11-39" Overall Image Checksum: 3261847397 o [SYS$LDR]SYS$PKQDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKQDRIVER" image file identification: "X-10A3" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:05:23.04 linker identification: "A11-39" Overall Image Checksum: 4027685376 o [SYS$LDR]SYS$PKSDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKSDRIVER" image file identification: "X-3" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:04:48.13 linker identification: "A11-39" Overall Image Checksum: 928131861 o [SYS$LDR]SYS$PKTDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKTDRIVER" image file identification: "X-3" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:04:59.67 linker identification: "A11-39" Overall Image Checksum: 3475463969 o [SYS$LDR]SYS$PKWDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKWDRIVER" image file identification: "X-29A3" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:05:34.73 linker identification: "A11-39" Overall Image Checksum: 2741376353 Page 6 o [SYS$LDR]SYS$PKZDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKZDRIVER" image file identification: "X-3" image file build identification: "X71Z-0050170031" link date/time: 23-APR-2004 14:05:09.22 linker identification: "A11-39" Overall Image Checksum: 3045454664 o [SYSLIB]LIB.MLB (new file) o [SYS$LDR]SYS$CONFIG.DAT (new file) o [SYS$LDR]SYS$LIB_C.TLB (new file) 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS722_FIBRE_SCSI-V0600 KIT 6.1 New functionality addressed in this kit 6.1.1 Add Emulex LP10000 support 6.1.1.1 Functionality Description: This kit provides support for the Emulex LP10000 2-channel FibreChannel Host Bus Adapter. Images Affected: - [SYSEXE]SYS$CONFIG.DAT - [SYS$LDR]SYS$FGEDRIVER.EXE 6.2 Problems addressed in this kit 6.2.1 Mis-leading errors when mounting tape drive 6.2.1.1 Problem Description: A hardware error is logged any time a tape is mounted on a tape drive, such as a TLZ09, that does not support the Read Write Error Recovery Page (SCSI Mode Page 01h). The error does not prevent the drive from mounting and OpenVMS Release Notes state that this behavior does not indicate a problem with the drive and can be ignored. However, ignoring errors is not a satisfactory answer for customers. Customers cannot distinguish this error from an actual error. This change will disable error logging for this error. Page 7 Images Affected: - [SYS$LDR]SYS$MKDRIVER.EXE 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.2.1 CLD(s) CFS.96327,CFS.97599,CFS.98783,CFS.99263,CFS.99951 6.2.1.2.2 QAR(s) None. 6.2.1.3 Problem Analysis: See Problem Description 6.2.1.4 Release Version of OpenVMS that will contain this change: V7.3-2 6.2.1.5 Work-arounds: None. 6.2.2 Requests issued to HSV FibreChannel storage array disks fail 6.2.2.1 Problem Description: Requests issued to HSV FibreChannel storage array disks fail with a SS$_OPINCOMPL error. If the disk is a member of a shadow set this will cause it to be removed from the set. Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE - [SYS$LDR]SYS$PGADRIVER.EXE Page 8 6.2.2.2 CLDs, and QARs reporting this problem: 6.2.2.2.1 CLD(s) CFS.97060 6.2.2.2.2 QAR(s) None. 6.2.2.3 Problem Analysis: The HSV returns a GOOD SCSI status with a transfer count of 0, which is not illegal by the applicable FibreChannel and SCSI standards but it is unusual. When SYS$DKDRIVER saw this 0-length transfer, it completed the request with SS$_OPINCOMPL. 6.2.2.4 Release Version of OpenVMS that will contain this change: V7.3-2 6.2.2.5 Work-arounds: None. 6.2.3 Excessive FibreChannel disk mount verifications 6.2.3.1 Problem Description: Excessive FibreChannel disk mount verifications, and FibreChannel disks going into mount verification timeout Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE - [SYS$LDR]SYS$PGADRIVER.EXE 6.2.3.2 CLDs, and QARs reporting this problem: Page 9 6.2.3.2.1 CLD(s) None. 6.2.3.2.2 QAR(s) PTR 75-83-1086 6.2.3.3 Problem Analysis: SYS$DKDRIVER was using the SPI$RESET_SCSI_BUS macro to reset the FibreCannel link when it shouldn't have - in parallel SCSI it made some sense to initialize the SCSI bus if some consecutive number of attempts to issue a command failed, but it doesn't make sense for FibreChannel in which transport level problems are recognized and handled by the lower-level drivers; also, SYS$PGADRIVER was issuing a target reset to clear a condition which really didn't warrant it SYS$DKDRIVER uses the SPI$RESET_SCSI_BUS macro to reset the FibreCannel link causing the mountverifications. this makes sense in parallel SCSI but is not necessary for FibreChannel in which transport level problems are recognized and handled by the lower-level drivers. 6.2.3.4 Release Version of OpenVMS that will contain this change: V7.3-2 6.2.3.5 Work-arounds: None. 6.2.4 Provide Additional error logging 6.2.4.1 Problem Description: Provide additional error logging to help diagnose systems with unavailable or missing fibre channel storage. Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE - [SYSLIB]FC$SDA.EXE Page 10 6.2.4.2 CLDs, and QARs reporting this problem: 6.2.4.2.1 CLD(s) None. 6.2.4.2.2 QAR(s) None. 6.2.4.3 Problem Analysis: See Problem Description 6.2.4.4 Release Version of OpenVMS that will contain this change: V7.3-2 6.2.4.5 Work-arounds: None. 6.2.5 SS$_IVADDR error after adding a member to the shadow set. 6.2.5.1 Problem Description: Occasionally, all accesses to a shadow disk return an SS$_IVADDR error after adding a member to the shadow set. Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE 6.2.5.2 CLDs, and QARs reporting this problem: 6.2.5.2.1 CLD(s) 70-3-6235,70-3-7245 6.2.5.2.2 QAR(s) None. Page 11 6.2.5.3 Problem Analysis: If a shadowing silent packack fails in such a way as to leave ucb$l_maxblock = 0, the subsequent read of the shadow SCB from the disk fails with an ss$_ivaddr error. Shadowing does not retry the packack, the disk is never packack'd successfully, and maxblock is permanently 0. A silent packack occurs when a shadow set is mounted on more than one cluster node. The node where the mount command is issued causes a packack/read SCB sequence to occur whenever the shadow unit is mounted. A packack failure can leave maxblock at 0 but the failure is ignored and the read SCB is attempted anyway. The resulting ss$_ivaddr error is not considered eligible for retry by Shadowing. Thus, the disk ends up with maxblock permanently set to zero and all IO requests are returned with ss$_ivaddr errors. 6.2.5.4 Release Version of OpenVMS that will contain this change: V7.3-2 6.2.5.5 Work-arounds: None. 6.3 Problems addressed in Previous FIBRE_SCSI kits 6.3.1 Problems addressed in previous V7.2-2 FIBRE_SCSI ECO kits 6.3.1.1 Problem Description: Problem information for problems addressed in previous V7.2-2 FIBRE_SCSI kits can be found in the file[SYSHLP]VMS722_FIBRE_SCSI-V0100_to_V0400.README. 7 INSTALLATION INSTRUCTIONS 7.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 VMS722_FIBRE_SCSI-V0600.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 Page 12 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.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 VMS722_FIBRE_SCSI /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. 7.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 Page 13 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/SYS 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=V6.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS722_FIBRE_SCSI-V0600 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/SYS ARCHIVE_OLD NO $! $ PROD INSTALL VMS722_FIBRE_SCSI/PRODUCER=DEC/BASE=AXPVMS- /VER=V6.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 8 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 Page 14 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.