**************************** ECO SUMMARY INFORMATION **************************** Release Date: 27-JUL-2007 Kit Name: DEC-AXPVMS-VMS83A_FIBRE_SCSI-V0200--4.PCSI$COMPRESSED;2 Kit Applies To: OpenVMS ALPHA V8.3 Approximate Kit Size: 2759 blocks Installation Rating: INSTALL_2 Required Features: Fibrechannel SCSI Reboot Required: Yes - rolling reboot Superseded Kits: VMS83A_FIBRE_SCSI-V0100 Mandatory Kit Dependencies: VMS83A_UPDATE-V0300 or later Optional Kit Dependencies: None Checksums: VMS83A_FIBRE_SCSI-V0200.ZIPEXE Checksum: 886763465 DEC-AXPVMS-VMS83A_FIBRE_SCSI-V0200--4.PCSI$COMPRESSED;2 Checksum: 3246746285 VMS83A_FIBRE_SCSI-V0200.ZIPEXE MD5 Checksum: 918294F83C68B26007BB0E9277833821 DEC-AXPVMS-VMS83A_FIBRE_SCSI-V0200--4.PCSI$COMPRESSED;2 MD5 Checksum: 0CAF4EC4EA50C6C5941BC4518CFE1114 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS83A_FIBRE_SCSI-V0200 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : To be installed by all customers using the following feature(s): - Fibrechannel - SCSI 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.3 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - VMS83A_FIBRE_SCSI-V0100 4 KIT DEPENDENCIES: Page 2 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS83A_UPDATE-V0300 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 VMS83A_FIBRE_SCSI-V0200 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 SANCP Privilege Failure 5.2.1.1 Problem Description: A privilege failure occurs when executing SANCP, even if the process currently has all required privileges : $ MCR SYS$ETC:SANCP %SANCP-F-NOPRIV, insufficient authorized privileges Images Affected: - [SYSHLP.UNSUPPORTED]SANCP.EXE 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) None. Page 3 5.2.1.2.2 QAR(s) None. 5.2.1.3 Problem Analysis: SANCP was checking to see if all of the required privileges were authorized, but a process which has has SETPRV can enable privileges which are not in its authorized mask. SANCP saw this as having insufficient privileges 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.1.5 Work-arounds: None. 5.2.2 Failure Status Not Logged 5.2.2.1 Problem Description: If the reset of the Emulex FC HBA fails due to the hardware error (in KERNEL$ENABLE_RING), the failure status of the reset unit is not logged in the error log file. Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) QXCM1000403365 5.2.2.2.2 QAR(s) None. Page 4 5.2.2.3 Problem Analysis: The error logging mechanism was not in place in the FG$ENABLE_RING routine if the reset unit fails due to a hardware error. 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.2.5 Work-arounds: None. 5.2.3 Misconfigured GG devices Cause System Crash 5.2.3.1 Problem Description: GG devices misconfigured as DG devices (disks), often cause an INVEXCEPTH system crash. Images Affected: - [SYS$LDR]SYS$PGADRIVER.EXE - [SYS$LDR]SYS$PGQDRIVER.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) 75-118-127 5.2.3.3 Problem Analysis: See problem description. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 Page 5 5.2.3.5 Work-arounds: None. 5.2.4 Intermittent INVEXCEPTN System Crashes 5.2.4.1 Problem Description: When utilizing the SNIA interface into an Emulex Fibre Channel HBA, the user will see intermittent INVEXCEPTN system crashes. The failing PC will be in the OTS$MOVE routine and can be traced back to a memmove in the copy_data routine in SYS$PGADRIVER. Images Affected: - [SYS$LDR]SYS$PGADRIVER.EXE 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) None. 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: A scratch PTE is not being zeroed before populating it. 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.4.5 Work-arounds: None. 5.2.5 Processes Unable to Exit Back to Command Prompt Page 6 5.2.5.1 Problem Description: Processes which have done I/O to a FibreChannel port driver are unable to exit back to the command prompt. Normal disk, tape or generic I/O is not at risk - instead, it is I/O that a user may not know is being executed on their behalf as part of some utility program commands such as SYSMAN IO, SDA or performance monitoring scripts. The stuck process will have a non-0 reference count on some page of memory due to an IO being cancelled off of the port's pending I/O queue and leaving this memory locked. Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE - [SYS$LDR]SYS$PGQDRIVER.EXE - [SYS$LDR]SYS$PGADRIVER.EXE 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: These drivers do not consider the non-standard buffer locking mechanism used by a fairly new service API (IO$_ACCESS) in their cancel I/O routines. 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.5.5 Work-arounds: None. Page 7 5.2.6 IO$_DIAGNOSE Related System Crash 5.2.6.1 Problem Description: The VMS83A_FIBRE_SCSI-V0100 patch kit included a problem with the SCSI driver IO$_DIAGNOSE function that will make systems with this patch installed susceptible to an IO$_DIAGNOSE induced crash. Such crashes can be reflected in several ways: o An INVEXCEPTN crash o POOLCHECK, Corruption or inconsistency in pool discovered by pool checker (poolcheck enabled) The change in this kit removes the change shipped in the VMS83A_FIBRE_SCSI-V0100 patch kit and restores the pre-kit behavior for this problem. OpenVMS engineering is developing a complete correction for the IO$_DIAGNOSE problems. This change will ship in a subsequent FIBRE_SCSI patch kit. Images Affected: - [SYS$LDR]SYS$GKDRIVER.EXE - [SYS$LDR]SYS$MKDRIVER.EXE - [SYS$LDR]SYS$DKDRIVER.EXE 5.2.6.2 CLDs, and QARs reporting this problem: 5.2.6.2.1 CLD(s) QXCM1000424933,QXCM1000437529,QXCM1000445135 5.2.6.2.2 QAR(s) None. 5.2.6.3 Problem Analysis: See problem description. 5.2.6.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 Page 8 5.2.6.5 Work-arounds: None. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS83A_FIBRE_SCSI ECO kits can be found in the following files: o VMS83A_FIBRE_SCSI-V0100.RELEASE_NOTES Before kit installation, these files can be extracted from the kit via the following commands: o To extract all release notes files at once use: PRODUCT EXTRACT RELEASE_NOTES VMS83A_FIBRE_SCSI - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS83A_FIBRE_SCSI - /SELECT=[SYSUPD]release_note_name[/DESTINATION=destination_directory] The names of individual RELEASE_NOTES files in the kit can be found with: PRODUCT LIST {PCSI Installation Name} /SELECT = *.RELEASE_NOTES 7 FILES PATCHED OR REPLACED: o [SYSHLP.UNSUPPORTED]SANCP.EXE (new image) Image Identification Information image name: "SANCP" image file identification: "X-2" image file build identification: "XBCA-0080070026" link date/time: 25-JUL-2007 15:41:29.86 linker identification: "A13-03" Overall Image Checksum: 662762540 o [SYS$LDR]SYS$DKDRIVER.EXE (new image) Image Identification Information image name: "SYS$DKDRIVER" image file identification: "X-9" image file build identification: "XBCA-0080070026" link date/time: 25-JUL-2007 15:41:06.25 linker identification: "A13-03" Overall Image Checksum: 3497790036 Page 9 o [SYS$LDR]SYS$FGEDRIVER.EXE (new image) Image Identification Information image name: "SYS$FGEDRIVER" image file identification: "X-70A4A42A2" image file build identification: "XBCA-0080070026" link date/time: 25-JUL-2007 15:41:23.87 linker identification: "A13-03" Overall Image Checksum: 911148158 o [SYS$LDR]SYS$GKDRIVER.EXE (new image) Image Identification Information image name: "SYS$GKDRIVER" image file identification: "X-63A3" image file build identification: "XBCA-0080070026" link date/time: 25-JUL-2007 15:41:08.96 linker identification: "A13-03" Overall Image Checksum: 4159066482 o [SYS$LDR]SYS$MKDRIVER.EXE (new image) Image Identification Information image name: "SYS$MKDRIVER" image file identification: "X-14" image file build identification: "XBCA-0080070026" link date/time: 25-JUL-2007 15:41:08.02 linker identification: "A13-03" Overall Image Checksum: 1665740736 o [SYS$LDR]SYS$PGADRIVER.EXE (new image) Image Identification Information image name: "SYS$PGADRIVER" image file identification: "X-93A2" image file build identification: "XBCA-0080070026" link date/time: 25-JUL-2007 15:41:18.80 linker identification: "A13-03" Overall Image Checksum: 2602216751 o [SYS$LDR]SYS$PGQDRIVER.EXE (new image) Image Identification Information image name: "SYS$PGQDRIVER" image file identification: "X-38A1" image file build identification: "XBCA-0080070026" link date/time: 25-JUL-2007 15:41:20.96 linker identification: "A13-03" Overall Image Checksum: 209073287 Page 10 o [SYS$LDR]SYS$PKMDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKMDRIVER" image file identification: "X-38A1" image file build identification: "XBCA-0080070026" link date/time: 25-JUL-2007 15:41:17.41 linker identification: "A13-03" Overall Image Checksum: 2839078552 o [SYS$LDR]SYS$PKRDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKRDRIVER" image file identification: "X-38A1" image file build identification: "XBCA-0080070026" link date/time: 25-JUL-2007 15:41:16.12 linker identification: "A13-03" Overall Image Checksum: 637178695 o [SYS$LDR]SYS$PKWDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKWDRIVER" image file identification: "X-38A1" image file build identification: "XBCA-0080070026" link date/time: 25-JUL-2007 15:41:16.51 linker identification: "A13-03" Overall Image Checksum: 175310916 8 INSTALLATION INSTRUCTIONS 8.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: 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. Page 11 o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 8.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS83A_FIBRE_SCSI-V0200.ZIPEXE 8.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 VMS83A_FIBRE_SCSI[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. 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.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 Page 12 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 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS83A_FIBRE_SCSI-V0200 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS83A_FIBRE_SCSI/PRODUCER=DEC/BASE=AXPVMS/VER=V2.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2007 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. Page 13 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.