**************************** ECO SUMMARY INFORMATION **************************** Release Date: 8-FEB-2007 Kit Name: DEC-AXPVMS-VMS82A_DDTM-V0200--4.PCSI$COMPRESSED Kit Applies To: OpenVMS ALPHA V8.2 Approximate Kit Size: 645 blocks Installation Rating: INSTALL_2 Required Features: Users of DECDTM, RDB , ACMS AND XA Reboot Required: Yes - rolling reboot Superseded Kits: VMS82A_DDTM-V0100 Mandatory Kit Dependencies: VMS82A_UPDATE-V0500 or later VMS82A_PCSI-V0100 or later Optional Kit Dependencies: None Checksums: VMS82A_DDTM-V0200.ZIPEXE Checksum: 3174025767 DEC-AXPVMS-VMS82A_DDTM-V0200--4.PCSI$COMPRESSED Checksum: 458457719 VMS82A_DDTM-V0200.ZIPEXE MD5 Checksum: 8DC813B9AA5072A727CF033A986B67AF DEC-AXPVMS-VMS82A_DDTM-V0200--4.PCSI$COMPRESSED MD5 Checksum: DF264637F644E7A9CB5B30464EDEB309 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS82A_DDTM-V0200 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : To be installed by all customers using the following feature(s): - Users of DECDTM, RDB , ACMS AND XA 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: No 3 KITS SUPERSEDED BY THIS KIT: - VMS82A_DDTM-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-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 VMS82A_DDTM-V0200 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Client Application Hang 5.2.1.1 Problem Description: Restarting the DDTM Gateway Server can sometimes cause transactions that were rolled back to reappear in the transaction log. When this happens, if a client tries to rollback the same transaction, it can lead to the client application hanging. Images Affected: - [SYSEXE]DDTM$XG_SERVER.EXE 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-13-1547 5.2.1.3 Problem Analysis: When a client calls xa_rollback, the type of the packet message is XG_REQ_ROLLBACK. During the execution, the thread should change the message type to 'XG_REQ_ROLLBACK_VOTED', indicating rollback completion, and requeue on the domains work queue. This thread eventually changes the type to 'XG_REQ_ROLLBACK_COMPLETE' and calls the CompleteXaService' function. Page 3 The hang occurs because, on completion, the xa_rollback function does not call the CompleteXaService function. The message type is not changed to type XG_REQ_ROLLBACK_VOTED and the thread is not woken up. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.1.5 Work-arounds: None. 5.2.2 SYS$DECLARE_RM(W) Returns ACCVIO 5.2.2.1 Problem Description: SYS$DECLARE_RM(W) returns ACCVIO if you do not specify the optional RM_NAME parameter in a call to SYS$DECLARE_RM. This happens with either a zero parameter or a null descriptor (one with dsc$a_pointer and dsc$w_length set to zero). Images Affected: - [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) None. 5.2.2.2.2 QAR(s) 75-13-1577 5.2.2.3 Problem Analysis: This problem occurs because the SYS$DECLARE_RM service does not check for a zero or null value for the RM_NAME argument (the eighth parameter). It directly tries to access the memory address given in this parameter with out checking the whether the value is a valid descriptor or zero. If the value is zero, it $probes the zeroes and returns SS$_ACCVIO to the client. Page 4 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.2.5 Work-arounds: None. 5.2.3 OCI Service Fails to Start 5.2.3.1 Problem Description: When running RDB SQL Services, the OCI Service fails to start. Images Affected: - [SYSEXE]DDTM$XG.EXE 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-115-131,75-13-1583 5.2.3.3 Problem Analysis: The xa_open service requires SYSPRV to create a user profile. When a client without SYSPRV calls xa_open, it returns a success status instead of failure. The subsequent function xa_start catches the error and returns a status of -6, resulting in the failure. With this change, xa_open will return a a status of -5, enabling the client to proceed further based on the status. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 Page 5 5.2.3.5 Work-arounds: None. 5.2.4 System Can Crash With INVEXCEPTN bugcheck at SYS$TRANSACTION_SERVICES+10480 5.2.4.1 Problem Description: The system can crash with "INVEXCEPTN, Exception while above ASTDEL" bugcheck at SYS$TRANSACTION_SERVICES+10480: Crashdump Summary Information ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL VMS Version: V8.2 Current Image: $1$DGA2:[SYS1.SYSCOMMON.] [SYSEXE]LSEDIT.EXE Failing PC: FFFFFFFF.80384480 SYS$TRANSACTION_SERVICES+10480 Failing PS: 20000000.00000802 Module: SYS$TRANSACTION_SERVICES (Link Date /Time: 27-SEP-2005 08:11:51.52) Offset: 00010480 Stack Pointers: KSP = 00000000.7FF87BD8 ESP = 00000000.7FF8C000 SSP = 00000000.7FF9CBA0 USP = 00000000.7AAF7B30 Failing Instruction: SYS$TRANSACTION_SERVICES+10480: LDL R27,#X0010(R11) Images Affected: - [SYSEXE]SYS$TRANSACTION_SERVICES.EXE 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) None. 5.2.4.2.2 QAR(s) 75-13-1742 Page 6 5.2.4.3 Problem Analysis: During run down, the DDTM Default Transaction Cleanup routine is invoked to deallocate all the memory it had allocated for DDTM data structures such as XDCB, XSCB and XCB. The code checks to see if the XDCB and XSCB structures have already been deallocated but the same check does not happen before deallocating XCB. 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. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS82A_DDTM ECO kits can be found in the following files: o VMS82A_DDTM-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_DDTM/VERSION= - /DESTINATION= destination_directory o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS82A_DDTM/VERSION= V2.0 - /SELECT=[SYSUPD]release_note_name/DESTINATION=destination_directory 7 FILES PATCHED OR REPLACED: o [SYSLIB]DDTM$XG.EXE (new image) Image Identification Information image name: "DDTM$XG" image file identification: "V2.1-X035-XAJT" image file build identification: "XAJT-0070050008" link date/time: 29-NOV-2006 11:19:50.53 linker identification: "A11-50" Overall Image Checksum: 1319309805 Page 7 o [SYSEXE]DDTM$XG_SERVER.EXE (new image) Image Identification Information image name: "DDTM$XG_SERVER" image file identification: "V2.1-X035-XAJT" image file build identification: "XAJT-0070050008" link date/time: 29-NOV-2006 11:19:51.40 linker identification: "A11-50" Overall Image Checksum: 2819435396 o [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE (new image) Image Identification Information image name: "SYS$TRANSACTION_SERVICES" image file identification: "V2.1-X035-XAJT" image file build identification: "XAJT-0070050008" link date/time: 29-NOV-2006 11:19:47.42 linker identification: "A11-50" Overall Image Checksum: 3122416656 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. Page 8 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_DDTM-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_DDTM[/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 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 Page 9 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_DDTM-V0200 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS82A_DDTM/PRODUCER=DEC/BASE=AXPVMS/VER=V2.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2006 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 Page 10 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.