**************************** ECO SUMMARY INFORMATION **************************** Release Date: 6-JUN-2007 Kit Name: DEC-AXPVMS-VMS82A_DRIVER-V0200--4.PCSI$COMPRESSED Kit Applies To: OpenVMS ALPHA V8.2 Approximate Kit Size: 3171 blocks Installation Rating: INSTALL_1 Reboot Required: Yes - rolling reboot Superseded Kits: VMS82A_DRIVER-V0100 Mandatory Kit Dependencies: VMS82A_UPDATE-V0600 or later VMS82A_PCSI-V0100 or later Optional Kit Dependencies: None Checksums: VMS82A_DRIVER-V0200.ZIPEXE Checksum: 341689847 DEC-AXPVMS-VMS82A_DRIVER-V0200--4.PCSI$COMPRESSED Checksum: 4284725615 VMS82A_DRIVER-V0200.ZIPEXE MD5 Checksum: CCCE333E9DAF1ACC27A9DB708CDB9B82 DEC-AXPVMS-VMS82A_DRIVER-V0200--4.PCSI$COMPRESSED MD5 Checksum: 01A7F022267F4877918DEEB4A9C68D66 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS82A_DRIVER-V0200 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 V8.2 2.4 New functionality or new hardware support provided: Yes 3 KITS SUPERSEDED BY THIS KIT: - VMS82A_DRIVER-V0100 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS82A_PCSI-V0100 - VMS82A_UPDATE-V0600 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 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS82A_DRIVER-V0200 KIT 5.1 New functionality addressed in this kit 5.1.1 Remove Fibre Channel Device Creation Restriction 5.1.1.1 Functionality Description: Although it is possible to create Fibre Channel devices with unit numbers greater than 9999 on server systems in an OpenVMS cluster system, prior to this fix such devices were not configured on the potential MSCP/TMSCP client systems for those devices. This restriction is documented in section 7.4.2.3 in the "Guidelines for OpenVMS Cluster Configurations" as a temporary restriction. With the change provided by this VMS82A_DRIVER-V0200 patch kit, this restriction is removed and it will be possible to serve Fibre Channel disk and tape devices whose unit numbers are greater than 9999 via the MSCP and TMSCP servers. After this kit is installed, it is possible to revert to the prior behavior and disallow the configuration of served Fibre Channel devices whose unit numbers are greater than 9999 by assigning a value of 16 to the MSCP_SERVE_ALL and TMSCP_SERVE_ALL SYSGEN parameters. Images Affected: - [SYS$LDR]SYS$DUDRIVER.EXE - [SYS$LDR]SYS$TUDRIVER.EXE - [SYSEXE]SYSBOOT.EXE - [SYSEXE]SYSGEN.EXE - [SYSEXE]SMISERVER.EXE - [SYSEXE]SYSMAN.EXE - [SYSLIB]SMI$OBJSHR.EXE Page 3 - [SYSLIB]SMI$SHR.EXE 5.2 Problems addressed in this kit 5.2.1 Problems When Booting a Node with an SCS Port 5.2.1.1 Problem Description: When booting a node with an SCS port, if the BAP (Bus Addressable Pool) SYSGEN parameters are inconsistent with the node's physical memory and PCI bus configuration, one or both of the following can occur: o A misleading error message is displayed, then the port goes offline: %PEA0, Insufficient Non-paged Pool for Initialization %PEA0, Port is going Offline. o The system can crash with an INVEXCEPTION in PEdriver, usually in or near the routine: SCSCI$INIT_CTLR Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER.STB - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PEDRIVER_MON.STB 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) None. 5.2.1.2.2 QAR(s) 75-45-1448,75-45-1448 5.2.1.3 Problem Analysis: The first SCS port to be initialized calls into SYS$SCS which causes SCS to allocate and initialize a data structure. However, depending on the system's configuration, SCS will allocate the data structure either from non-paged pool or BAP. If this allocation Page 4 fails, the port issues an error message and attempts to go offline. The error message generated only mentions non-paged pool, and does not mention BAP ; the PDT's spinlock address contains zero, which causes the INVEXCEPTION. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.3 5.2.1.5 Work-arounds: None. 5.2.2 SMCIPORT Crash 5.2.2.1 Problem Description: The system can experience an SMCIPORT crash when creating a self communication channel for the Galaxy Shared Memory Cluster Interconnect (SMCI). This crash will occur if the low bit of the system parameter SMCI_FLAGS is set. Images Affected: - [SYS$LDR]SYS$PBDRIVER.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) QXCM1000228349 5.2.2.2.2 QAR(s) None. 5.2.2.3 Problem Analysis: See problem description 5.2.2.4 Release Version of OpenVMS that will contain this change: OpenVMS V8.3 Alpha Page 5 5.2.2.5 Work-arounds: None. 5.2.3 INVEXCEPTION Bugcheck 5.2.3.1 Problem Description: An INVEXCEPTION can result when stopping SCA use of a LAN device by using either LAVC$STOP_BUS, or SCACP> STOP LAN_DEVICE. Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER.STB - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PEDRIVER_MON.STB 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-112-161 5.2.3.3 Problem Analysis: A register was being unnecessarily cleared when the code detected that the LAN device associated with a channel was going away. Subsequently, the zeroed register was being used to unlock the PM spinlock. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMs Alpha after V8.3 Page 6 5.2.3.5 Work-arounds: None. 5.2.4 SSRVEXCEPT Bugcheck 5.2.4.1 Problem Description: An SSRVEXCEPT, Unexpected system service exception bugcheck can occur. Images Affected: - [SYS$LDR]SYS$RTTDRIVER.EXE 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) QXCM1000237866 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: The bugcheck occurs when SYS$RTTDRIVER was used to access a remote device. During the transfer, an implicit sign extend of the registers being preserved is done. In this case, instead of making the top 32 bits ones, they were made zeros, which caused the resultant ACCVIO and system crash. 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. Page 7 5.2.5 Invalid Exception Crash 5.2.5.1 Problem Description: SYS$PEDRIVER traces various events in trace buffers. Under rare circumstances, the trace data may extend past the end of the trace buffer, over-writing the next structure in non-paged pool, resulting in a possible invalid exception crash. Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER.STB - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PEDRIVER_MON.STB 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: See problem description. 5.2.5.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.3 5.2.5.5 Work-arounds: None. 5.2.6 INVEXCEPTN/ACCVIO, VAXPORT or NETDLLERR Bugcheck Page 8 5.2.6.1 Problem Description: With process acked packets, it is possible that a VC (Virtual Circuit) is closed due to a buffer size change while scanning the list of acked packets. This may result in a system crash because the retransmit queue is unexpectedly empty. The crash occurs when PEDRIVER attempts to access an element on the retransmit queue and there are not any. The crash usually appears as an INVEXCEPTN/ACCVIO in the routine TR.RCV_ACK, but may also appear as a VAXPORT bugcheck or as a NETDLLERR bugcheck. The NETDLLERR bugcheck occurs when the LAN driver is processing transmit completion and the next expected VCRP request to complete is not the one actually next on the queue for completion, i.e., the transmit pending queue has been corrupted. Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER.STB - [SYS$LDR]SYS$PEDRIVER_MON.EXE - [SYS$LDR]SYS$PEDRIVER_MON.STB 5.2.6.2 CLDs, and QARs reporting this problem: 5.2.6.2.1 CLD(s) 70-3-8923 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 9 5.2.6.5 Work-arounds: None. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS82A_DRIVER ECO kits can be found in the following files: o VMS82A_DRIVER-V100.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 VMS82A_DRIVER/VERSION= - /DESTINATION= destination_directory o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS82A_DRIVER/VERSION= V2.0 - /SELECT=[SYSUPD]release_note_name/DESTINATION=destination_directory 7 FILES PATCHED OR REPLACED: o [SYSLIB]SMI$OBJSHR.EXE (new image) Image Identification Information image name: "SMI$OBJSHR" image file identification: "X40-A9" image file build identification: "XAJT-0070050009" link date/time: 12-APR-2007 10:51:02.40 linker identification: "A11-50" Overall Image Checksum: 515583805 o [SYSLIB]SMI$SHR.EXE (new image) Image Identification Information image name: "SMI$SHR" image file identification: "X01-04" image file build identification: "XAJT-0070050009" link date/time: 12-APR-2007 10:50:59.57 linker identification: "A11-50" Overall Image Checksum: 1782654031 o [SYSEXE]SMISERVER.EXE (new image) Image Identification Information Page 10 image name: "SMISERVER" image file identification: "X01-15" image file build identification: "XAJT-0070050009" link date/time: 12-APR-2007 10:51:04.90 linker identification: "A11-50" Overall Image Checksum: 2448100526 o [SYS$LDR]SYS$DUDRIVER.EXE (new image) Image Identification Information image name: "SYS$DUDRIVER" image file identification: "X-5" image file build identification: "XAJT-0070500011" link date/time: 15-MAR-2007 09:49:57.43 linker identification: "A11-50" Overall Image Checksum: 123512055 o [SYS$LDR]SYS$PBDRIVER.EXE (new image) Image Identification Information image name: "SYS$PBDRIVER" image file identification: "X-32" image file build identification: "XAJT-0070500011" link date/time: 15-MAR-2007 09:49:37.99 linker identification: "A11-50" Overall Image Checksum: 2427954809 o [SYS$LDR]SYS$PEDRIVER.EXE (new image) Image Identification Information image name: "SYS$PEDRIVER" image file identification: "X-3" image file build identification: "XAJT-0070500011" link date/time: 15-MAR-2007 09:50:03.11 linker identification: "A11-50" Overall Image Checksum: 1268471770 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: "XAJT-0070500011" link date/time: 15-MAR-2007 09:50:03.74 linker identification: "A11-50" Overall Image Checksum: 2399575563 o [SYS$LDR]SYS$RTTDRIVER.EXE (new image) Image Identification Information image name: "SYS$RTTDRIVER" image file identification: "X-5" Page 11 image file build identification: "XAJT-0070500011" link date/time: 15-MAR-2007 09:50:06.38 linker identification: "A11-50" Overall Image Checksum: 2065621730 o [SYS$LDR]SYS$TUDRIVER.EXE (new image) Image Identification Information image name: "SYS$TUDRIVER" image file identification: "X-5" image file build identification: "XAJT-0070500011" link date/time: 15-MAR-2007 09:50:04.15 linker identification: "A11-50" Overall Image Checksum: 1949881709 o [SYSEXE]SYSBOOT.EXE (new image) Image Identification Information image name: "SYSBOOT" image file identification: "X-131" image file build identification: "XAJT-0070050001" link date/time: 23-MAR-2007 08:12:02.63 linker identification: "A11-50" Overall Image Checksum: 2392852607 o [SYSEXE]SYSGEN.EXE (new image) Image Identification Information image name: "SYSGEN" image file identification: "X-5" image file build identification: "XAJT-0070050000" link date/time: 12-APR-2007 10:50:59.98 linker identification: "A11-50" Overall Image Checksum: 1333472024 o [SYSEXE]SYSMAN.EXE (new image) Image Identification Information image name: "SYSMAN" image file identification: "X01-22" image file build identification: "XAJT-0070050009" link date/time: 12-APR-2007 10:51:04.00 linker identification: "A11-50" Overall Image Checksum: 2771274005 o [SYS$LDR]SYS$PEDRIVER.STB (new file) o [SYS$LDR]SYS$PEDRIVER_MON.STB (new file) Page 12 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 VMS82A_DRIVER-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 VMS82A_DRIVER[/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 Page 13 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=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 VMS82A_DRIVER-V0200 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS82A_DRIVER/PRODUCER=DEC/BASE=AXPVMS/VER=V2.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! Page 14 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. 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.