======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_FIBRE_SCSI-V0800 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : To be installed by all customers using the following feature(s): - FIBRE CHANNEL OR SCSI OR The customers who have installed the kit VMS84I_FIBRE_SCSI-V0700 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 for Integrity Servers V8.4 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - VMS84I_FIBRE_SCSI-V0700 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: - VMS84I_PCSI-V0400 - VMS84I_UPDATE-V1000 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 VMS84I_FIBRE_SCSI-V0800 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Alignment faults with AVIO storage driver 5.2.1.1 Problem Description: Kernel mode alignment faults with AVIO storage driver seen on HPVM guests. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$GSPDRIVER.EXE - [SYS$LDR]SYS$GSPDRIVER.STB 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001277678 Page 3 5.2.1.2.2 PTR(S) None 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.1.4 Work-arounds: None 5.2.2 Disk initialization fails with disk sizes greater than 2TB. 5.2.2.1 Problem Description: Disk initialization fails with "medium is offline" or "bad parameter value" error for disk sizes 2TB or higher. Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE - [SYS$LDR]SYS$DKDRIVER.STB 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases QXCM1001339201 5.2.2.2.2 PTR(S) None 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.2.4 Work-arounds: None Page 4 5.2.3 OpenVMS systems crash with INVEXCEPTN bugcheck, while configuring tape devices. 5.2.3.1 Problem Description: OpenVMS systems crash with INVEXCEPTN bugcheck in PGQDRIVER, as the driver was accessing un-initialized data during tape drive configuration. This issue is fixed. Images Affected: - [SYS$LDR]SYS$PGQDRIVER.EXE - [SYS$LDR]SYS$PGQDRIVER.STB 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases QXCM1001339414 5.2.3.2.2 PTR(S) 75-126-393 5.2.3.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.3.4 Work-arounds: None 5.2.4 OpenVMS system crashes with INVEXCEPTN bugcheck, due to Nonpaged pool corruption caused by PKMDRIVER. 5.2.4.1 Problem Description: rx2800 i2 systems crash with INVEXCEPTN bugcheck due to Nonpaged pool corruption caused by PKMDRIVER, while doing BACKUP operations with large BLOCK_SIZE, to or from a tape device, connected through SC11Xe SCSI controller. This problem has been fixed. Images Affected: Page 5 - [SYS$LDR]SYS$PKMDRIVER.EXE - [SYS$LDR]SYS$PKMDRIVER.STB 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1001370714 5.2.4.2.2 PTR(S) None 5.2.4.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.4.4 Work-arounds: This problem could be worked around by limiting the backup /BLOCK_SIZE qualifier to 8192 bytes or less, until the fixed SYS$PKMDRIVER image can be installed. 5.2.5 FC PERFORMANCE SDA extension fails to display data if device's primary path is set to the MSCP. 5.2.5.1 Problem Description: MSCP path for a device has limited set of functionalities and does not support performance data collection. For performance data collection today, the primary path of the device is considered. So, when the MSCP path is the primary path for the device, FC PERFORMANCE fails to display performance data. This issue is fixed by considering the current path of the device, while displaying performance data. If the device?s current path is MSCP, and FC performance data collection is desired, one needs to set the current path to any available physical path before running SDA>FC PERFORMANCE. Images Affected: - [SYSLIB]FC$SDA.EXE Page 6 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases QXCM1001377677 5.2.5.2.2 PTR(S) 75-126-422 5.2.5.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.5.4 Work-arounds: None 5.2.6 LTT software is unable to scan and find devices connected through QLOGIC ISP2532 (8G FC)card. 5.2.6.1 Problem Description: LTT software is unable to scan and find devices connected through QLOGIC ISP2532 PCIe Fibre HBA, as OpenVMS SNIA HBA API support is not available for this card. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$PGQDRIVER.EXE - [SYS$LDR]SYS$PGQDRIVER.STB - [SYSLIB]HBA_VMS.EXE - [SYSLIB]HBAAPITEST.EXE 5.2.6.2 Quix and PTR cases reporting this problem: 5.2.6.2.1 Quix Cases QXCM1001386644 Page 7 5.2.6.2.2 PTR(S) None 5.2.6.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.6.4 Work-arounds: None 5.2.7 Boot hang observed when VMS is booted from disks in MSA30 enclosure connected through LSI 1030 SCSI adapter. 5.2.7.1 Problem Description: Unable to boot when OpenVMS booted from disks in MSA30 storage enclosure connected to LSI 1030 SCSI adapter in RX3600/RX2660/RX6600 servers. The systems hang with the below errors during boot : PKM - Target Reset not supported in this Port Type 1 PKM - Target Reset not supported in this Port Type 1 This problem has been fixed. Images Affected: - [SYS$LDR]SYS$PKMBTDRIVER.EXE - [SYSEXE]IPB.EXE 5.2.7.2 Quix and PTR cases reporting this problem: 5.2.7.2.1 Quix Cases QXCM1001193068 5.2.7.2.2 PTR(S) None Page 8 5.2.7.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.7.4 Work-arounds: None 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS84I_FIBRE_SCSI patch kits can be found in the following files: o VMS84I_FIBRE_SCSI-V0100.RELEASE_NOTES o VMS84I_FIBRE_SCSI-V0200.RELEASE_NOTES o VMS84I_FIBRE_SCSI-V0300.RELEASE_NOTES o VMS84I_FIBRE_SCSI-V0400.RELEASE_NOTES o VMS84I_FIBRE_SCSI-V0500.RELEASE_NOTES o VMS84I_FIBRE_SCSI-V0600.RELEASE_NOTES o VMS84I_FIBRE_SCSI-V0700.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 VMS84I_FIBRE_SCSI /VERSION=V8.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_FIBRE_SCSI /VERSION=V8.0 - /SELECT=release_note_name[/DESTINATION=destination_directory] The names of individual RELEASE_NOTES files in the kit can be found with: PRODUCT LIST VMS84I_FIBRE_SCSI /VERSION=V8.0 /SELECT = *.RELEASE_NOTES Page 9 7 FILES PATCHED OR REPLACED: o [SYSLIB]FC$SDA.EXE (new image) Image Identification Information Image name: "FC$SDA" Image file identification: "X-42" Image build identification: "0100000154" linker identification: "Linker I02-37" Link Date/Time: 16-JAN-2015 13:50:51.03 Overall Image Checksum: 7E8D3293 o [SYSLIB]HBAAPITEST.EXE (new image) Image Identification Information Image name: "HBAAPITEST" Image file identification: "V1.0" Image build identification: "0100000154" linker identification: "Linker I02-37" Link Date/Time: 16-JAN-2015 13:50:47.37 Overall Image Checksum: 72A8076F o [SYSLIB]HBA_VMS.EXE (new image) Image Identification Information Image name: "HBA_VMS" Image file identification: "V1.0" Image build identification: "0100000154" linker identification: "Linker I02-37" Link Date/Time: 16-JAN-2015 13:50:46.54 Overall Image Checksum: 70B70770 o [SYSEXE]IPB.EXE (new image) Image Identification Information Image name: "IPB" Image file identification: "X-4" Image build identification: "0100000154" linker identification: "Linker I02-37" Link Date/Time: 16-JAN-2015 13:48:33.26 Overall Image Checksum: E4F3C354 o [SYS$LDR]SYS$DKDRIVER.EXE (new image) Image Identification Information Image name: "SYS$DKDRIVER" Image file identification: "X-5" Image build identification: "0100000162" linker identification: "Linker I02-37" Link Date/Time: 25-MAR-2015 13:03:45.86 Overall Image Checksum: EDDE8A5A Page 10 o [SYS$LDR]SYS$GSPDRIVER.EXE (new image) Image Identification Information Image name: "SYS$GSPDRIVER" Image file identification: "X-5" Image build identification: "0100000154" linker identification: "Linker I02-37" Link Date/Time: 16-JAN-2015 13:50:32.81 Overall Image Checksum: B655810B o [SYS$LDR]SYS$PGQDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PGQDRIVER" Image file identification: "X-5" Image build identification: "0100000154" linker identification: "Linker I02-37" Link Date/Time: 16-JAN-2015 13:49:55.69 Overall Image Checksum: AC4C7400 o [SYS$LDR]SYS$PKMBTDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PKMBTDRIVER" Image file identification: "X-5" Image build identification: "0100000154" linker identification: "Linker I02-37" Link Date/Time: 16-JAN-2015 13:48:55.97 Overall Image Checksum: 87CBAC44 o [SYS$LDR]SYS$PKMDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PKMDRIVER" Image file identification: "X-5" Image build identification: "0100000154" linker identification: "Linker I02-37" Link Date/Time: 16-JAN-2015 13:49:26.95 Overall Image Checksum: 904E4821 o [SYS$LDR]SYS$DKDRIVER.STB (new file) o [SYS$LDR]SYS$GSPDRIVER.STB (new file) o [SYS$LDR]SYS$PKMDRIVER.STB (new file) o [SYS$LDR]SYS$PGQDRIVER.STB (new file) Page 11 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. 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 VMS84I_FIBRE_SCSI-V0800.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 VMS84I_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. Page 12 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 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=HP/BASE=I64VMS/VER=V8.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_FIBRE_SCSI-V0800 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_FIBRE_SCSI/PRODUCER=HP/BASE=I64VMS/VER=V8.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT Page 13 $! $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2015 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.