**************************** ECO SUMMARY INFORMATION **************************** Release Date: 30-JUN-2004 Kit Name: DEC-AXPVMS-VMS73_DRIVER-V0700--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3 Approximate Kit Size: 8624 blocks Installation Rating: INSTALL_1 Superseded Kits: VMS73_DRIVER-V0600 Mandatory Kit Dependencies: VMS73_UPDATE-V0300 VMS73_PCSI-V0200 Optional Kit Dependencies: None VMS73_DRIVER-V0700.PCSI-DCX_AXPEXE Checksum: 883739676 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS73_DRIVER-V0700 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3 1 KIT NAME: VMS73_DRIVER-V0700 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1 : To be installed by all customers. 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.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - VMS73_DRIVER-V0600 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS73_PCSI-V0200 - VMS73_UPDATE-V0300 Page 2 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 [SYSEXE]CONFIGURE.EXE (new image) Image Identification Information image name: "CONFIGURE" image file identification: "X-7" image file build identification: "X9UH-0060010009" link date/time: 19-MAR-2004 18:10:54.94 linker identification: "A11-50" Overall Image Checksum: 3683783610 o [SYSHLP]PE$SDA.EXE (new image) Image Identification Information image name: "PE$SDA" image file identification: "X-9A1" image file build identification: "0060010009" link date/time: 19-MAR-2004 18:12:56.77 linker identification: "A11-50" Overall Image Checksum: 454328238 o [SYSEXE]SCACP.EXE (new image) Image Identification Information image name: "SCACP" image file identification: "X-13" image file build identification: "X9UH-0060010009" link date/time: 19-MAR-2004 18:12:19.83 linker identification: "A11-50" Overall Image Checksum: 595461824 o [SYSLIB]SDA$SHARE.EXE (new image) Image Identification Information image name: "SDA$SHARE" image file identification: "X-6B1" image file build identification: "X9UH-0060010025" link date/time: 17-OCT-2003 03:25:07.50 linker identification: "A11-50" Overall Image Checksum: 3488148667 Page 3 o [SYSEXE]STACONFIG.EXE (new image) Image Identification Information image name: "STACONFIG" image file identification: "X-39A1" image file build identification: "X9UH-0060010009" link date/time: 19-MAR-2004 18:11:29.49 linker identification: "A11-50" Overall Image Checksum: 343104334 o [SYS$LDR]SYS$BASE_IMAGE.EXE (new image) Image Identification Information image name: "SYS$BASE_IMAGE" image file identification: "ALPHA X9UH-K5L" image file build identification: "X9UH-0060010067" link date/time: 17-OCT-2003 03:11:36.30 linker identification: "A11-50" Overall Image Checksum: 1421204007 o [SYS$LDR]SYS$DQDRIVER.EXE (new image) Image Identification Information image name: "SYS$DQDRIVER" image file identification: "X-26A1" image file build identification: "X9UH-0060010018" link date/time: 5-MAR-2004 20:53:25.71 linker identification: "A11-50" Overall Image Checksum: 337110557 o [SYS$LDR]SYS$DRDRIVER.EXE (new image) Image Identification Information image name: "SYS$DRDRIVER" image file identification: "X-19A1" image file build identification: "X9UH-0060010018" link date/time: 5-MAR-2004 20:53:08.09 linker identification: "A11-50" Overall Image Checksum: 976604099 o [SYS$LDR]SYS$DUDRIVER.EXE (new image) Image Identification Information image name: "SYS$DUDRIVER" image file identification: "X-3" image file build identification: "X9UH-0060010018" link date/time: 5-MAR-2004 20:37:00.38 linker identification: "A11-50" Overall Image Checksum: 1581571375 Page 4 o [SYS$LDR]SYS$PADRIVER.EXE (new image) Image Identification Information image name: "SYS$PADRIVER" image file identification: "X-3" image file build identification: "X9UH-0060010018" link date/time: 5-MAR-2004 20:49:35.45 linker identification: "A11-50" Overall Image Checksum: 437853156 o [SYS$LDR]SYS$PBDRIVER.EXE (new image) Image Identification Information image name: "SYS$PBDRIVER" image file identification: "X-28" image file build identification: "X9UH-0060010018" link date/time: 5-MAR-2004 20:37:39.15 linker identification: "A11-50" Overall Image Checksum: 2966075252 o [SYS$LDR]SYS$PCADRIVER.EXE (new image) Image Identification Information image name: "SYS$PCADRIVER" image file identification: "X-3" image file build identification: "X9UH-0060010018" link date/time: 5-MAR-2004 20:48:28.26 linker identification: "A11-50" Overall Image Checksum: 4239341476 o [SYS$LDR]SYS$PEDRIVER.EXE (new image) Image Identification Information image name: "SYS$PEDRIVER" image file identification: "X-3" image file build identification: "X9UH-0060010018" link date/time: 5-MAR-2004 20:44:23.40 linker identification: "A11-50" Overall Image Checksum: 2699208475 o [SYS$LDR]SYS$PEDRIVER_MON.EXE (new image) Image Identification Information image name: "SYS$PEDRIVER_MON" image file identification: "X-3" image file build identification: "X9UH-0060010018" link date/time: 5-MAR-2004 20:45:44.59 linker identification: "A11-50" Overall Image Checksum: 2696660224 Page 5 o [SYS$LDR]SYS$PIDRIVER.EXE (new image) Image Identification Information image name: "SYS$PIDRIVER" image file identification: "X-3" image file build identification: "X9UH-0060010018" link date/time: 5-MAR-2004 20:48:21.86 linker identification: "A11-50" Overall Image Checksum: 1046151105 o [SYS$LDR]SYS$PJDRIVER.EXE (new image) Image Identification Information image name: "SYS$PJDRIVER" image file identification: "X-3" image file build identification: "X9UH-0060010018" link date/time: 5-MAR-2004 20:49:09.87 linker identification: "A11-50" Overall Image Checksum: 87496321 o [SYS$LDR]SYS$PMDRIVER.EXE (new image) Image Identification Information image name: "SYS$PMDRIVER" image file identification: "X-31" image file build identification: "X9UH-0060010018" link date/time: 5-MAR-2004 20:42:02.58 linker identification: "A11-50" Overall Image Checksum: 2552391472 o [SYS$LDR]SYS$PNDRIVER.EXE (new image) Image Identification Information image name: "SYS$PNDRIVER" image file identification: "X-3" image file build identification: "X9UH-0060010018" link date/time: 5-MAR-2004 20:46:06.76 linker identification: "A11-50" Overall Image Checksum: 4052856476 o [SYS$LDR]SYS$TUDRIVER.EXE (new image) Image Identification Information image name: "SYS$TUDRIVER" image file identification: "X-3" image file build identification: "X9UH-0060010018" link date/time: 5-MAR-2004 20:52:03.92 linker identification: "A11-50" Overall Image Checksum: 4089865765 Page 6 o [SYS$LDR]SCSDEF.STB image) 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS73_DRIVER-V0700 KIT 6.1 New functionality addressed in this kit None. 6.2 Problems addressed in this kit 6.2.1 A multiprocessor system may crash with a CPUSPINWAIT or INVEXCEPTN bugcheck in DUTU$CANCEL. 6.2.1.1 Problem Description: A multiprocessor system may crash with a CPUSPINWAIT or INVEXCEPTN bugcheck in DUTU$CANCEL. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Failing PC: FFFFFFFF.80751A54 SYS$DUDRIVER+0FA54 Failing PS: 20000000.00000800 Module: SYS$DUDRIVER (Link Date/Time: 1-OCT-2003 21:18:58.53) Offset: 0000FA54 Stack Pointers: KSP = 00000000.7FF87418 ESP = 00000000.7FF8BA70 SSP = 00000000.7FF9CD00 USP = 00000000.0010FBD0 Images Affected: - [SYS$LDR]SYS$DUDRIVER.EXE - [SYS$LDR]SYS$TUDRIVER.EXE 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.2.1 CLD(s) None. Page 7 6.2.1.2.2 QAR(s) 75-102-14 6.2.1.3 Problem Analysis: If during cancel scan of restart queue a cancellable CDRP was located, it was REMQUEUED and then its flink was used to continue the queue scan. It may have been updated/stale while being posted, leading to a CPUSPINWAIT bugcheck or INVEXCEPTN bugcheck. 6.2.1.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.1.5 Work-arounds: None. 6.2.2 AVAIL MSCP command can trigger a mount verify, which cancels the AVAIL. 6.2.2.1 Problem Description: An AVAIL MSCP command can trigger a mount verify, which cancels the AVAIL and cause a served RAID set to remain online to a host. Images Affected: - [SYS$LDR]SYS$DUDRIVER.EXE - [SYS$LDR]SYS$TUDRIVER.EXE 6.2.2.2 CLDs, and QARs reporting this problem: 6.2.2.2.1 CLD(s) None. 6.2.2.2.2 QAR(s) 75-83-1578 Page 8 6.2.2.3 Problem Analysis: See Problem Description 6.2.2.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.2.5 Work-arounds: None. 6.2.3 If the direct path failed, MSCP served paths were not being used. 6.2.3.1 Problem Description: If the direct path failed, MSCP served paths were not being used. Images Affected: - [SYS$LDR]SYS$DUDRIVER.EXE - [SYS$LDR]SYS$TUDRIVER.EXE 6.2.3.2 CLDs, and QARs reporting this problem: 6.2.3.2.1 CLD(s) 70-3-7075 6.2.3.2.2 QAR(s) None. 6.2.3.3 Problem Analysis: The UCB$V_VALID bit was not cleared until after the end message of an AVAIL MSCP command. This allows the following to happen: 1. AVAIL message is sent by a $ DISMOUNT command. 2. It is acted on by the HSJ by placing drive in the AVAILABLE state. Page 9 3. The HSJ sends an AVAILABLE_ATTENTION datagram. 4. The datagram triggers mount verify which sends a PACKACK and a MSCP ONLINE command, essentially undoing the AVAIL. 5. End message sent by HSJ. Dismounted unit remains ONLINE to the host. 6.2.3.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.3.5 Work-arounds: A DCL MOUNT and DISMOUNT of the drive can be performed if it is necessary to delete a RAID unit on the HSJ. 6.2.4 System can crash with a CPUSPINWAIT, CPU spinwait timer expired bugcheck 6.2.4.1 Problem Description: System can crash with a CPUSPINWAIT, CPU spinwait timer expired bugcheck: Crashdump Summary Information: ------------------------------ Bugcheck Type: CPUSPINWAIT, CPU spinwait timer expired Current Process: NULL Current Image: Failing PC: FFFFFFFF.800883A4 SMP$TIMEOUT_C+00064 Failing PS: 18000000.00000804 Module: SYSTEM_SYNCHRONIZATION_MIN (Link Date/Time: 19-FEB-2003 11:27:32.44) Offset: 000003A4 Stack Pointers: KSP = FFFFFFFF.AC335DD8 ESP = FFFFFFFF.AC337000 SSP = FFFFFFFF.AC321000 USP = FFFFFFFF.AC321000 Failing Instruction: SMP$TIMEOUT_C+00064: BUGCHK Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE Page 10 - [SYS$LDR]SYS$PEDRIVER_MON.EXE 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) 75-102-3 6.2.4.3 Problem Analysis: SPINWAIT timeout occurs due to PEdriver looping for many seconds in PEM$CC_ECS_ORDER. The port will be out of message or datagram free queue entries as indicated by PORT$V_NEED_MFQ and/or PORT$V_NEED_DFQ set. 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 Cluster hang during MC/SMCI connected node shutdown 6.2.5.1 Problem Description: Whenever a cluster member's VMS$VAXcluster SYSAP is connected via Memory Channel and/or Shared Memory CI to another node, and that partner node goes away, the member will hang waiting for the full RECNXINTERVAL before initiating a cluster state transition. Images Affected: - SYS$PEDRIVER.EXE - SYS$PEDRIVER_MON.EXE - SYS$PIDRIVER.EXE - SYS$PJDRIVER.EXE Page 11 - SYS$PADRIVER.EXE - SYS$PBDRIVER.EXE - SYS$PMDRIVER.EXE - SYS$PNDRIVER.EXE - SYS$PCADRIVER.EXE 6.2.5.2 CLDs, and QARs reporting this problem: 6.2.5.2.1 CLD(s) None. 6.2.5.2.2 QAR(s) 75-13-1146 6.2.5.3 Problem Analysis: This occurs because these interconnects can not implement the SCS HOST_SHUTDOWN (last gasp datagram) message. The full RECNXINTERVAL delay can occur even when there is another cluster interconnect that supports the SCS HOST_SHUTDOWN message. This is because the connection manager only received host shutdown messages that are delivered by the circuit that is currently being used by the VMS$VAXcluster SYSAP. 6.2.5.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.5.5 Work-arounds: None. 6.2.6 Improperly formatted Errorlog entry Page 12 6.2.6.1 Problem Description: A misleading VC (Virtual Connection) timeout error log entry is output when the real error is an ill-formed SCS message, or other message causing a VC closure. Images Affected: - SYS$PEDRIVER.EXE - SYS$PEDRIVER_MON.EXE - SYS$PIDRIVER.EXE - SYS$PJDRIVER.EXE - SYS$PADRIVER.EXE - SYS$PBDRIVER.EXE - SYS$PMDRIVER.EXE - SYS$PNDRIVER.EXE - SYS$PCADRIVER.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-83-668 6.2.6.3 Problem Analysis: See Problem Description 6.2.6.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 Page 13 6.2.6.5 Work-arounds: None. 6.2.7 System performance appears to be very sluggish 6.2.7.1 Problem Description: System performance appears to be very sluggish with unexplained high interrupt stack time and/or high mpsynch time when running with one or more LAN devices with unplugged or failed CABLES, or switch ports. With several such disconnected devices, the system may be unable to successfully boot, may not be able to join a cluster, or may experience unexplained VC (virtual Circuit) closures and/or CLUEXITS. Images Affected: - SYS$PEDRIVER.EXE - SYS$PEDRIVER_MON.EXE 6.2.7.2 CLDs, and QARs reporting this problem: 6.2.7.2.1 CLD(s) 70-3-7119 70-3-7425 6.2.7.2.2 QAR(s) None. 6.2.7.3 Problem Analysis: See Problem Description 6.2.7.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.7.5 Work-arounds: None. Page 14 7 PROBLEMS ADDRESSED IN PREVIOUS KITS 7.1 Problems addressed in previous V7.3 DRIVER kits The VMS73_DRIVER-V0700 ECO kit includes problems fixed by all V7.3 DRIVER ECO kits issued since VMS73_UPDATE-V0300. Problems addressed by these DRIVER kits can be found in the following file: o [SYSHLP]VMS73_DRIVER-V0600.RELEASE_NOTES 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 VMS73_DRIVER-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 VMS73_DRIVER /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 Page 15 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.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/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=V7.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS73_DRIVER-V0700 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/SYS ARCHIVE_OLD NO $! $ PROD INSTALL VMS73_DRIVER/PRODUCER=DEC/BASE=AXPVMS- /VER=V7.0/SAVE_RECOVERY_DATA $! Page 16 $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 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.