**************************** ECO SUMMARY INFORMATION **************************** Release Date: 21-DEC-2005 Kit Name: DEC-AXPVMS-VMS732_LAT-V0100--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-2 Approximate Kit Size: 560 blocks Installation Rating: INSTALL_2 Required Features: LAT Reboot Required: Yes - rolling reboot Superseded Kits: None Mandatory Kit Dependencies: VMS732_UPDATE-V0500 VMS732_PCSI-V0100 Optional Kit Dependencies: None VMS732_LAT-V0100.PCSI-DCX_AXPEXE Checksum: 2705417335 DEC-AXPVMS-VMS732_LAT-V0100--4.PCSI Checksum: 4220532212 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS732_LAT-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : To be installed by all customers using the following feature(s): - LAT 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 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS732_PCSI-V0100 - VMS732_UPDATE-V0500 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 VMS732_LAT-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Possible Pool Corruptor With Failed Connect To Dedicated LAT Service 5.2.1.1 Problem Description: When connecting to a dedicated LAT service, if the connection fails with the following error,the error cleanup deletes the IRP prematurely. %LAT-F-CONFAIL, connection to TEST_LAT not established -LAT-F-LRJINUSE, port or service in use Subsequent operations on the deallocated IRP could result in pool corruption and possibly lead to a bugcheck. Images Affected: - [SYS$LDR]SYS$LTDRIVER.EXE 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) QXCM1000091236 5.2.1.2.2 QAR(s) None. Page 3 5.2.1.3 Problem Analysis: There is no singular crash footprint because the general nature of the pool corruption. If the portion of corrupted pool can be found, the remnants of a LAT IRP may be found adjacent to the corruption with a function code of LAT$C_FC_PROCSTRT and an IRP$L_SAVD_RTN field pointing to the routine LT$COMPLETE_REMCON_REQ. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.1.5 Work-arounds: None. 5.2.2 System Crash With An INCONSTATE Bugcheck In SYS$LTDRIVER 5.2.2.1 Problem Description: The system can crash with an INCONSTATE bugcheck in SYS$LTDRIVER that maps to a routine called LT$CRASH. References to LT$RCV_RUN_NEWSLOT and LT$ACPT_CONNECT can be seen on the stack in SDA. Crashdump Summary Data ----------------------- Bugcheck Type: INCONSTATE, Inconsistent I/O data base VMS Version: V7.3-2 Current Process: NULL Current Image: Failing PC: FFFFFFFF.80706810 SYS$LTDRIVER+12810 Failing PS: 00000000.00000804 Module: SYS$LTDRIVER (Link Date/Time: 1-OCT-2003 21:19:20.51) Offset: 00012810 Failing Instruction: SYS$LTDRIVER+12810: BUGCHK Images Affected: - [SYS$LDR]SYS$LTDRIVER.EXE Page 4 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) QXCM1000225475 5.2.2.2.2 QAR(s) None. 5.2.2.3 Problem Analysis: There is an outstanding SOLICIT INFO message and it's associated session is in a "REQUEST INFO" state. While waiting, an inbound LAT RUN message arrives requesting the start of a new session. Because it has the same ID number, LTDRIVER attempts to match the incoming RUN message with the waiting solicit message. Based on the solicit state table, this results in a call to LT$CRASH. 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.2.5 Work-arounds: None. 6 FILES PATCHED OR REPLACED: o [SYS$LDR]SYS$LTDRIVER.EXE (new image) Image Identification Information image name: "SYS$LTDRIVER" image file identification: "X-4" image file build identification: "XA99-0060110010" link date/time: 2-MAY-2005 11:30:05.82 linker identification: "A11-50" Overall Image Checksum: 1759166168 7 INSTALLATION INSTRUCTIONS Page 5 7.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. 7.2 Compressed File 7.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 VMS732_LAT[/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. Page 6 7.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=V1.0 '[/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS732_LAT-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS732_LAT/PRODUCER=DEC/BASE=AXPVMS/VER=V1.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! Page 7 8 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.