**************************** ECO SUMMARY INFORMATION **************************** Release Date: 3-MAY-2005 Kit Name: DEC-AXPVMS-VMS731_FIBRE_SCSI-V0700--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-1 Approximate Kit Size: 5488 blocks Installation Rating: INSTALL_2 Required Features: Fibrechannel SCSI Reboot Required: Yes - rolling reboot Superseded Kits: VMS731_FIBRE_SCSI-V0600 Mandatory Kit Dependencies: VMS731_UPDATE-V0500 VMS731_PCSI-V0200 Optional Kit Dependencies: None VMS731_FIBRE_SCSI-V0700.PCSI-DCX_AXPEXE Checksum: 332623136 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS731_FIBRE_SCSI-V0700 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.3-1 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - VMS731_FIBRE_SCSI-V0600 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: - VMS731_PCSI-V0200 - VMS731_UPDATE-V0500 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 [SYSLIB]FC$SDA.EXE (new image) Image Identification Information image name: "FC$SDA" image file identification: "X-17A1" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:41:06.12 linker identification: "A11-50" Overall Image Checksum: 1488206821 o [SYSLIB]IOGEN$FIBRE_CONFIG.EXE (new image) Image Identification Information image name: "IOGEN$FIBRE_CONFIG" image file identification: "X-27" image file build identification: "XA2Q-0060030003" link date/time: 24-MAR-2004 11:34:35.58 linker identification: "A11-50" Overall Image Checksum: 1626224016 o [SYSLIB]IOGEN$SCSI_CONFIG.EXE (new image) Image Identification Information image name: "IOGEN$SCSI_CONFIG" image file identification: "X-13" image file build identification: "XA2Q-0060030003" link date/time: 24-MAR-2004 11:34:35.08 linker identification: "A11-50" Overall Image Checksum: 1212410765 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: "XA9J-0060030062" link date/time: 23-FEB-2005 14:41:06.72 linker identification: "A11-50" Overall Image Checksum: 2601487416 o [SYSHLP.UNSUPPORTED]SCSI_INFO.EXE (new image) Image Identification Information image name: "SCSI_INFO" image file identification: "V3" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:41:03.54 linker identification: "A11-50" Overall Image Checksum: 2041986203 o [SYS$LDR]SYS$DKDRIVER.EXE (new image) Image Identification Information image name: "SYS$DKDRIVER" image file identification: "X-12" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:40:53.81 linker identification: "A11-50" Overall Image Checksum: 3329842921 o [SYS$LDR]SYS$FGEDRIVER.EXE (new image) Image Identification Information image name: "SYS$FGEDRIVER" image file identification: "X-70A14" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:41:02.30 linker identification: "A11-50" Overall Image Checksum: 880456999 o [SYS$LDR]SYS$GKDRIVER.EXE (new image) Image Identification Information image name: "SYS$GKDRIVER" image file identification: "X-48A3" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:40:55.26 linker identification: "A11-50" Overall Image Checksum: 2477746749 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: "XA9J-0060030062" link date/time: 23-FEB-2005 14:40:54.78 linker identification: "A11-50" Overall Image Checksum: 1786876606 o [SYS$LDR]SYS$PGADRIVER.EXE (new image) Image Identification Information image name: "SYS$PGADRIVER" image file identification: "X-58A7" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:41:01.25 linker identification: "A11-50" Overall Image Checksum: 1289388827 o [SYS$LDR]SYS$PKADRIVER.EXE (new image) Image Identification Information image name: "SYS$PKADRIVER" image file identification: "X-26A6" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:41:00.50 linker identification: "A11-50" Overall Image Checksum: 3241078531 o [SYS$LDR]SYS$PKCDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKCDRIVER" image file identification: "X-18" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:40:55.74 linker identification: "A11-50" Overall Image Checksum: 4173169997 o [SYS$LDR]SYS$PKEDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKEDRIVER" image file identification: "X-18" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:40:56.25 linker identification: "A11-50" Overall Image Checksum: 3051848833 Page 5 o [SYS$LDR]SYS$PKJDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKJDRIVER" image file identification: "X-18" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:40:56.73 linker identification: "A11-50" Overall Image Checksum: 3601068092 o [SYS$LDR]SYS$PKQDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKQDRIVER" image file identification: "X-22" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:40:58.72 linker identification: "A11-50" Overall Image Checksum: 2596209195 o [SYS$LDR]SYS$PKRDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKRDRIVER" image file identification: "X-33" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:40:59.29 linker identification: "A11-50" Overall Image Checksum: 2060702533 o [SYS$LDR]SYS$PKSDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKSDRIVER" image file identification: "X-18" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:40:57.20 linker identification: "A11-50" Overall Image Checksum: 2436826650 o [SYS$LDR]SYS$PKWDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKWDRIVER" image file identification: "29A7" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:40:59.85 linker identification: "A11-50" Overall Image Checksum: 918709939 Page 6 o [SYS$LDR]SYS$PKZDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKZDRIVER" image file identification: "X-18" image file build identification: "XA9J-0060030062" link date/time: 23-FEB-2005 14:40:58.20 linker identification: "A11-50" Overall Image Checksum: 1382701224 o [SYS$LDR]SYS$CONFIG.DAT (new file) 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS731_FIBRE_SCSI-V0700 KIT 6.1 New functionality addressed in this kit None. 6.2 Problems addressed in this kit 6.2.1 System Page Table Entry (SPTE) resource leak 6.2.1.1 Problem Description: There is a slow leak of System Page Table Entry (SPTE) resources Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE - [SYS$LDR]SYS$PGADRIVER.EXE 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.2.1 CLD(s) None. 6.2.1.2.2 QAR(s) None. Page 7 6.2.1.3 Problem Analysis: An SPTE pointer was being cleared before the resources were released back to the system. 6.2.1.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.1.5 Work-arounds: None. 6.2.2 ABS saves failing with intermittent %BACKUP-F-POSITERR error 6.2.2.1 Problem Description: ABS saves are failing with an intermittent %BACKUP-F-POSITERR error when attempting to append savesets to an existing volumeset. There is no evidence that there is a problem with the media or the tape drive since a DCL backup command can successfully append a saveset to the tape. Images Affected: - [SYS$LDR]SYS$MKDRIVER.EXE 6.2.2.2 CLDs, and QARs reporting this problem: 6.2.2.2.1 CLD(s) 70-3-7781,CFS.105761 6.2.2.2.2 QAR(s) None. 6.2.2.3 Problem Analysis: EOV (End Of Volume) processing does not correctly signal SS$_ENDOFVOLUME. Page 8 6.2.2.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.2.5 Work-arounds: None. 6.2.3 INCONSTATE bugcheck at SYS$FGEDRIVER+11648 6.2.3.1 Problem Description: A system can crash with an INCONSTATE bugcheck at SYS$FGEDRIVER+11648 Crashdump Summary Information: ------------------------------ Bugcheck Type: INCONSTATE, Inconsistent I/O data base Failing PC: FFFFFFFF.80671648 SYS$FGEDRIVER+11648 Failing PS: 08000000.00000804 Module: SYS$FGEDRIVER Offset: 00011648 Stack Pointers: KSP = FFFFFFFF.A30F9E88 ESP = FFFFFFFF.A2981000 SSP = FFFFFFFF.A2979000 USP = FFFFFFFF.A2979000 Failing Instruction: SYS$FGEDRIVER+11648: BUGCHK Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE 6.2.3.2 CLDs, and QARs reporting this problem: 6.2.3.2.1 CLD(s) 70-3-7739 6.2.3.2.2 QAR(s) None. Page 9 6.2.3.3 Problem Analysis: If an IOERR$K_NO_RESOURCES status occurs, the default (unchecked) condition of bugchecking with an INCONSTATE crash occurs. 6.2.3.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.3.5 Work-arounds: None. 6.2.4 System crash with INVEXCEPTN, Exception while above ASTDEL at SYS$PKADRIV 6.2.4.1 Problem Description: If an IOERR$K_NO_RESOURCES status occurs, the default (unchecked) condition of bugchecking with an INCONSTATE crash occurs. The system can crash with an INVEXCEPTN, Exception while above ASTDEL at SYS$PKADRIVER+3558C Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: NULL Current Image: Failing PC: FFFFFFFF.805CF58C SYS$PKADRIVER+3558C Failing PS: 38000000.00000804 Module: SYS$PKADRIVER (Link Date/Time: 5-JAN-2004 20:18:45.42) Offset: 0003558C Stack Pointers: KSP = FFFFFFFF.B4CC9918 ESP = FFFFFFFF.B426F000 SSP = FFFFFFFF.B4269000 USP = FFFFFFFF.B4269000 Failing Instruction: SYS$PKADRIVER+3558C: LDL R0,#X0010(R18) Images Affected: - [SYS$LDR]SYS$PKADRIVER.EXE Page 10 6.2.4.2 CLDs, and QARs reporting this problem: 6.2.4.2.1 CLD(s) 70-3-7873 6.2.4.2.2 QAR(s) None. 6.2.4.3 Problem Analysis: Under certain conditions, double completion of the same I/O can occur during SCSI bus resets. 6.2.4.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.4.5 Work-arounds: None. 6.2.5 Frequent mount verifies can occur on KZPCM and KZPCA controlled disks. 6.2.5.1 Problem Description: Frequent mount verifies and error log entries for command timeouts can occur on KZPCM and KZPCA controlled disks. Images Affected: - [SYS$LDR]SYS$PKWDRIVER.EXE 6.2.5.2 CLDs, and QARs reporting this problem: 6.2.5.2.1 CLD(s) 70-3-7682,70-3-7791 6.2.5.2.2 QAR(s) None. Page 11 6.2.5.3 Problem Analysis: The link to the next I/O was lost. This causes I/O to stop until PKWDRIVER'S sanity timer routine detects it and cleans things up. 6.2.5.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.5.5 Work-arounds: None. 6.2.6 ACCVIO when running SCSI_INFO 6.2.6.1 Problem Description: An ACCVIO can occur when running SCSI_INFO for medium changers and SCSI controllers. Images Affected: - [SYSHLP.UNSUPPORTED]SCSI_INFO.EXE 6.2.6.2 CLDs, and QARs reporting this problem: 6.2.6.2.1 CLD(s) None. 6.2.6.2.2 QAR(s) 75-13-1324 6.2.6.3 Problem Analysis: The utility is driven by some table entries, sorted by device type, in SCSI_INFO.C. For a device type of 'medium changer', one mandatory table entry was set to zero. This causes an ACCVIO whenever SCSI_INFO is run against a medium changer. Page 12 6.2.6.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.6.5 Work-arounds: None. 6.2.7 KZPEC (Smart Array) Throttling fix. 6.2.7.1 Problem Description: On certain configurations, more I/O can be sent to the KZPEC (Smart Array) controller than it periodically can handle. This change detects that this is about to occur and throttles back the I/O. Images Affected: - [SYS$LDR]SYS$PKRDRIVER.EXE 6.2.7.2 CLDs, and QARs reporting this problem: 6.2.7.2.1 CLD(s) None. 6.2.7.2.2 QAR(s) None. 6.2.7.3 Problem Analysis: The problem is due to a hardware problem with the KZPEC (Smart Array 6404). 6.2.7.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2 6.2.7.5 Work-arounds: None. Page 13 6.2.8 System Crash due to bad hardware 6.2.8.1 Problem Description: A system may crash with one of the following, or other, bugchecks if hardware is going bad. Many times, the problems will occur with a bad tape unit. Some errors are logged just prior to the crash. Crashdump Summary Information ----------------------------- Bugcheck Type: KRNLSTAKNV, Kernel stack not valid Failing PC: FFFFFFFF.8E2D7DB4 SYS$MKDRIVER+11DB4 Failing PS: 00000000.00000804 Module: SYS$MKDRIVER (Link Date/Time: 22-APR-2004 13:40:49.41) Offset: 00011DB4 Failing Instruction: SYS$MKDRIVER+11DB4: HALT Crashdump Summary Information ----------------------------- Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Failing PC: 00000000.00000000 Failing PS: 00000000.00000804 Offset: 00000000 Images Affected: - [SYS$LDR]SYS$PKWDRIVER.EXE 6.2.8.2 CLDs, and QARs reporting this problem: 6.2.8.2.1 CLD(s) CFS.108366,QXCM1000206757 6.2.8.2.2 QAR(s) None. 6.2.8.3 Problem Analysis: Crashes occur on a selection timeout when two interrupts for the same I/O request are received in quick succession. One I/O request is completed two times. Page 14 6.2.8.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2 6.2.8.5 Work-arounds: None. 6.2.9 Odd-byte Transfers May Return The Wrong Byte Count 6.2.9.1 Problem Description: Odd-byte transfers may return a byte count that is one byte short of a full load. Images Affected: - [SYS$LDR]SYS$PKWDRIVER.EXE 6.2.9.2 CLDs, and QARs reporting this problem: 6.2.9.2.1 CLD(s) None. 6.2.9.2.2 QAR(s) 75-13-1356, 75-102-2216 6.2.9.3 Problem Analysis: At the end of a data transfer, the driver decrements the number of residue bytes if the "data xferred" status bit is set. The decrement is happening even if the bit is not set. 6.2.9.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 6.2.9.5 Work-arounds: None. Page 15 6.2.10 Medium Offline (MEDOFL) Errors On HP Ultrium 460 Drives 6.2.10.1 Problem Description: Medium Offline (MEDOFL) errors can occasionally occur on HP Ultrium 460 tape drives. These errors occur when a MOUNT or INIT is attempted too soon after the tape has been DISMOUNTed. Images Affected: - [SYS$LDR]SYS$MKDRIVER.EXE 6.2.10.2 CLDs, and QARs reporting this problem: 6.2.10.2.1 CLD(s) None. 6.2.10.2.2 QAR(s) 75-83-1511 6.2.10.3 Problem Analysis: MKDRIVER does not wait long enough for the tape to finish rewinding before declaring failure on the INIT or MOUNT command. 6.2.10.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2 6.2.10.5 Work-arounds: None. 6.2.11 COPY Command May Produce Errors When Copying FILES 6.2.11.1 Problem Description: The COPY command may produce errors wehen copying files. Images Affected: - [SYS$LDR]SYS$PKWDRIVER.EXE Page 16 6.2.11.2 CLDs, and QARs reporting this problem: 6.2.11.2.1 CLD(s) None. 6.2.11.2.2 QAR(s) None. 6.2.11.3 Problem Analysis: There is more than one source for the final byte count. All, some, or none of them can be valid depending on how the transfer executed. Certain bytecount/padcount combinations make it nearly impossible to tell how many bytes were xferred. 6.2.11.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS V8.2 6.2.11.5 Work-arounds: None. 7 PROBLEMS ADDRESSED IN PREVIOUS KITS Descriptions of problems corrected in previous VMS731_FIBRE_SCSI patch kits can be found in the following files: o VMS731_FIBRE_SCSI-V0600.RELEASE_NOTES o VMS731_FIBRE_SCSI-V0500.RELEASE_NOTES o VMS731_FIBRE_SCSI-V0400.RELEASE_NOTES o VMS731_FIBRE_SCSI-V0300.RELEASE_NOTES o VMS731_FIBRE_SCSI-V0200.RELEASE_NOTES o VMS731_FIBRE_SCSI-V0100.RELEASE_NOTES Page 17 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 VMS731_FIBRE_SCSI-V0700.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 VMS731_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. Page 18 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=V7.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS731_FIBRE_SCSI-V0700 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS731_FIBRE_SCSI/PRODUCER=DEC/BASE=AXPVMS- /VER=V7.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit Page 19 9 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.