**************************** ECO SUMMARY INFORMATION **************************** Release Date: 2-FEB-2006 Kit Name: DEC-AXPVMS-VMS732_MQ-V0400--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-2 Approximate Kit Size: 2048 blocks Installation Rating: INSTALL_2 Required Features: IBM MQseries Reboot Required: Yes - rolling reboot Superseded Kits: VMS732_MQ-V0300 Mandatory Kit Dependencies: VMS732_UPDATE-V0500 VMS732_PCSI-V0100 Optional Kit Dependencies: None VMS732_MQ-V0400.PCSI-DCX_AXPEXE Checksum: 3027605719 DEC-AXPVMS-VMS732_MQ-V0400--4.PCSI Checksum: 2851247465 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS732_MQ-V0400 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : To be installed by all customers using the following feature(s): - IBM MQseries 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: - VMS732_MQ-V0300 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_MQ-V0400 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 System Crash With SSRVEXCEPT Bugcheck 5.2.1.1 Problem Description: The system can crash with an SSRVEXCEPT bugcheck: Crashdump Summary Information: ------------------------------ Bugcheck Type: SSRVEXCEPT, Unexpected system service exception VMS Version: V7.3-2 Current Process: BME.MQP1_EC Current Image: DSA0:[SYS0.SYSCOMMON.] [SYSEXE]AMQZXMA0.EXE Failing PC: FFFFFFFF.80091B34 SMP$ACQUIREL_C+00024 Failing PS: 18000000.00000003 Module: SYSTEM_SYNCHRONIZATION_MIN (Link Date/Time: 1-OCT-2003 21:19:02.27) Offset: 00017B34 Signal Array: 64-bit Signal Array: Arg Count = 00000005 Arg Count = 00000005 Condition = 0000000C Condition = 00000000.0000000C Argument #2 = 00000000 Argument #2 = 00000000.00000000 Argument #3 = 00000014 Argument #3 = 00000000.00000014 Argument #4 = 80091B34 Argument #4 = FFFFFFFF.80091B34 Argument #5 = 00000003 Argument #5 = 18000000.00000003 R0 = 00000000.00000000 R1 = 00000000.0000013F R2 = FFFFFFFF.814E2E40 EXE$PSHARED_REGISTER R3 = 00000000.04A3A000 R4 = FFFFFFFF.8140A778 LCK$GQ_RESERVED2 R5 = FFFFFFFF.81408AC8 SMP$GL_FLAGS R6 = 00000000.001DEBF8 R7 = 00000000.7FF87FC0 Page 3 R8 = 00000000.0000000A R9 = 00000000.00000001 R10 = 00000000.00000001 R11 = FFFFFFFF.FFFFDE15 R12 = 00000000.00126250 R13 = FFFFFFFF.814B7B08 SMP_STD$ACQUIREL R14 = 00000000.00000000 R15 = 00000000.00000BB0 R16 = 00000000.00000000 R17 = FFFFFFFF.8140A940 EXE$GL_NONPAGED+00050 R18 = FFFFFFFF.81D211D0 R19 = 00000000.00000000 R20 = FFFFFFFF.80164864 EXE$PSHARED_REGISTER_C+00184 R21 = 00000000.00000043 R22 = FFFFFFFF.7FFF6490 R23 = FFFFFFFF.7FFF4000 R24 = FFFFFFFF.8227DE40 BUFIO AI = 00000000.00000001 RA = FFFFFFFF.80164864 EXE$PSHARED_REGISTER_C+00184 PV = FFFFFFFF.814B7B08 SMP_STD$ACQUIREL R28 = FFFFFFFF.81408000 EXE$GR_SYSTEM_DATA_CELLS FP = 00000000.7FF87C30 PC = FFFFFFFF.80091B34 SMP$ACQUIREL_C+00024 PS = 18000000.00000003 Kernel Mode, IPL 0 The keys are that the current image belongs to MQseries, failing virtual address is 0x14 and EXE$PSHARED_REGISTER is in R2. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_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) None. Page 4 5.2.1.3 Problem Analysis: Pshared support maintains a dynamic spinlock per global section and keeps the pointer to the pshared master and the corresponding spinlock address in an array. Two threads, executing in parallel, could create this dynamic spinlock structure and an atomic exchange used to store the spinlock address in the array. If the atomic update fails, it is assumed that another thread has created the spinlock, the new spinlock is deallocated and what is in the array continues to be used. However, in the case of the crash, neither thread has succeeded in updating the dynamic spinlock pointer and the first device_lock to use this zero spinlock address crashes the system. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2 5.2.1.5 Work-arounds: None. 5.2.2 Nonpaged pool memory leak. 5.2.2.1 Problem Description: A nonpaged pool memory leak can occur. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) QXCM1000240628 Page 5 5.2.2.2.2 QAR(s) None. 5.2.2.3 Problem Analysis: The memory leak can occur when an ACB, placed on the PCB$L_ACB_STALL_QUEUE, is not deallocated. 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2 5.2.2.5 Work-arounds: None. 5.2.3 Process Hangs 5.2.3.1 Problem Description: Customers can experience TDF releated process hangs. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_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) PMR 53782,370,000 Page 6 5.2.3.3 Problem Analysis: When the Time Differential Factor (TDF) is changed on a system, any pshared condition variables (CVs) that are waiting on a timeout do not get their time out adjusted. This can result in the CVs timing out at a much later time if the TDF is reduced or timing out immediately if the TDF is increased. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2 5.2.3.5 Work-arounds: None. 5.2.4 Process Hangs 5.2.4.1 Problem Description: Processes can hang. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) QXCM1000227600 5.2.4.2.2 QAR(s) None. Page 7 5.2.4.3 Problem Analysis: Kernel threads can hang when wake requests do not occur. 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2 5.2.4.5 Work-arounds: None. 5.2.5 Process Thread Hangs 5.2.5.1 Problem Description: Process threads could hang waiting for a pshared mutex. This problem will only occur if pshared condition variables and mutexes are used and processes holding a mutex get terminated (image rundown or process deletion). Currently, the only user is MQseries V5.3 Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 5.2.5.2 CLDs, and QARs reporting this problem: 5.2.5.2.1 CLD(s) QMCM1000306057 5.2.5.2.2 QAR(s) None. 5.2.5.3 Problem Analysis: If the process that owns the thread gets terminated, a locked mutex should be marked as abandoned but is not. Page 8 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2 5.2.5.5 Work-arounds: None. 5.2.6 System Crash With A SPLRELERR Bugcheck 5.2.6.1 Problem Description: A system could crash with a SPLRELERR bugcheck if the system parameter SYSTEM_CHECK is set to 1 and threaded processes are involved. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB 5.2.6.2 CLDs, and QARs reporting this problem: 5.2.6.2.1 CLD(s) None. 5.2.6.2.2 QAR(s) 75-109-1043,75-109-1062,75-109-1074,75-109-1089 5.2.6.3 Problem Analysis: Routine EXE$INFORM_TM_AST does not take into account that it can be called with the PCB spinlock held. If a blocked kthread needs to be woken up, and system check is turned on, additional sanity checking is done by the spinlock code. A ranking violation prevents simply acquiring and releasing the PCB spinlock. Page 9 5.2.6.4 Release Version of OpenVMS that will contain this change: Next release after OpenVMS Alpha V8.2 5.2.6.5 Work-arounds: None. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS732_MQ ECO kits can be found in the following files: o [SYSHLP]VMS732_MQ-V0300.RELEASE_NOTES o [SYSHLP]VMS732_MQ-V0200.RELEASE_NOTES o [SYSHLP]VMS732_MQ-V0100.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 VMS732_MQ/VERSION=V4.0- /DESTINATION= destination_directory o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS732_MQ/VERSION=V4.0 - /SELECT=[SYSUPD]release_note_name- /DESTINATION=destination_directory 7 FILES PATCHED OR REPLACED: o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT" image file identification: "X-4" image file build identification: "XA99-0060111033" link date/time: 18-JAN-2006 13:27:44.32 linker identification: "A11-50" Overall Image Checksum: 970907884 o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) Image Identification Information Page 10 image name: "PROCESS_MANAGEMENT_MON" image file identification: "X-4" image file build identification: "XA99-0060111033" link date/time: 18-JAN-2006 13:27:45.50 linker identification: "A11-50" Overall Image Checksum: 392166960 o [SYS$LDR]PROCESS_MANAGEMENT.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file) 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 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 VMS732_MQ-V0400.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 Page 11 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.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_MQ[/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. 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 Page 12 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=V4.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS732_MQ-V0400 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS732_MQ/PRODUCER=DEC/BASE=AXPVMS/VER=V4.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 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. Page 13 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.