ECO NUMBER: ALPDDTM06_062 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V6.2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V6.2 COVER LETTER 1 KIT NAME: ALPDDTM06_062 2 KITS SUPERSEDED BY THIS KIT: ALPDDTM05_062 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: None. 3.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V6.2 4.2 Files patched or replaced: o [SYSLIB]DTI$SHARE.EXE (new image) o [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE (new image) o [SYSEXE]TPSERV.EXE (new image) o [SYS$LDR]SYS$IPC_SERVICES.EXE (new image) 5 PROBLEMS ADDRESSED IN ALPDDTM05_062.RNO KIT o If the user had installed the ALPDDTM04_062 ECO kit, the images in the ALPDDTM05_062 ECO kit would not install. The user would see the following error message for all DDTM images: Applying [IMAGE_NAME] will result in a regression in the -- COVER LETTER -- Page 2 18 November 2002 bugfix level while maintaining the same level of layered product functionality. Note that if you successfully installed the ALPDDTM05_062 ECO kit, you do nto need to install this ALPDDTM06_062 kit. Images Affected: - [SYSLIB]DTI$SHARE.EXE - [SYS$LDR]SYS$IPC_SERVICES.EXE - [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE 6 PROBLEMS ADDRESSED IN ALPDDTM05_062 KIT o The system can crash with SSRVEXCEPT in TPSERV.EXE. The failing instruction is INSQUEL. Crashdump Summary: ------------------ Crash Time: 20-AUG-1998 01:07:16.89 Bugcheck Type: CSLBUG, CSL has detected an invalid condition Node: KKBH01 (Clustered) CPU Type: AlphaServer 8400 Model 5/300 VMS Version: V6.2-1H3 Current Process: TP_SERVER Current Image: DSA2982:[SYSO.SYSCOMMON.] [SYSEXE]TPSERV.EXE;5 Failing PC: 00000000 00023210 Failing PS: 20000000 00000001 Module: TPSERV Offset: 00023210 Images Affected: - [SYSEXE]TPSERV.EXE o The TP_SERVER process can loop consuming CPU cycles. Images Affected: - [SYSEXE]TPSERV.EXE -- COVER LETTER -- Page 3 18 November 2002 7 PROBLEMS ADDRESSED IN ALPDDTM04_062 KIT o The image SYS$IPC_SERVICES.EXE should have been included in the ALPDDTM03_062 remedial kit. It was not. Customers who installed the ALPDDTM03_062 kit did not get all the problem corrections listed in the documentation. 8 PROBLEMS ADDRESSED IN ALPDDTM03_062 KIT o An RDB/ACMS application was ported from OpenVMS VAX V6.2 to OpenVMS Alpha V6.2. When the full user load was on the nodes, they imtermittently crash about once a day due to nonpaged pool corruption of 128 byte packets. o System bootup cannot start TP_SERVER. Manually starting it with DECDTM$STARTUP failed with STR-F-ERRFREDYN. Two failure scenarios were present: 1. If the DECdtm journal file did not exist, the TP_SERVER process crashed with a STR-F-ERRFREDYN error. The OPCOM message, normally generated when the journal file is not present, appeared normal: $ @sys$startup:decdtm$startup %%%%%%%%%%% OPCOM 16-SEP-1997 10:00:25.06 %%%%%%%%%%% Message from user SYSTEM on K Warning: DECdtm log file not found (SYS$JOURNAL: SYSTEM$K.LM$JOURNAL) %RMS-E-FNF, file not found TP server process waiting However, there was no TP_SERVER process. The TP_SERVER_ERROR.LOG contained (slightly edited due to space constraints here): %STR-F-ERRFREDYN, error freeing dynamic string when returned to LIB$FREE_VM %TRACE-F-TRACEBACK, symbolic stack dump follows Image Name Module Name Routine Name Line Number TPSERV DTIS_ENVIRONMEN DTI$CHECK_ENVIR 400 TPSERV LM_SERVER MAIN 599 2. If the DECdtm journal file did exist, TP_SERVER stack dumped into the TP_SERVER_ERROR.LOG with STR-F-ERRFREDYN, but no process dump was generated. In this instance, no OPCOM message relative to "file not found" would be generated (because the journal file did exist). The TP_SERVER_ERROR.LOG contained (again, slightly edited): -- COVER LETTER -- Page 4 18 November 2002 Image Name Module Name Routine Name Line Number TPSERV DTIS_ENVIRONMEN DTI_TRNLNM 1106 TPSERV DTIS_ENVIRONMEN DTI$CHECK_ENVIR 418 TPSERV LM_SERVER MAIN 599 Regarding the use of string descriptors in the module DTIS_ENVIRONMEN, dynamic string descriptors were being used for calls to system services ($GETMSG, $FAO, and $TRLNM) that expected fixed length string descriptors. In addition, the lengths of the strings were being manipulated by the TPSERV code, which is strongly cautioned against in the OpenVMS documentation that discusses the various types of string datatypes. When STR$FREE1_DX was called to free the memory consumed by the string, the illegal manipulation that had been done in the TPSERV code, caused STR$FREE1_DX to fail. o Nonpaged pool expands constantly, filling with hundreds of thousands of DDTM_NDCB structures until it reaches maximum and the machine hangs or crashes. This problem has only been seen on ALPHAs. 9 PROBLEMS ADDRESSED IN ALPDDTM03_070 KIT FOR OPENVMS V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 ONLY o The actions of a transaction log open and a transaction log close can conflict causing the system to crash with a DDTMBUG bugcheck. o Non-paged pool may fill with LMTRCBs. This only happens when distributed transactions are being used inside a cluster. o System crash from user mode if $END_TRANS is called in the sub-process of process where $START_TRANS was called. 10 PROBLEMS ADDRESSED IN ALPDDTM02_070 KIT FOR OPENVMS V6.2-1H1 ONLY o The ALPDDTM01_070 remedial kit did not install on systems running OpenVMS Alpha V6.2-1H1, as it should have. 11 PROBLEMS ADDRESSED IN ALPDDTM01_070 KIT FOR OPENVMS V6.2, V6.2-1H1 ONLY o There was a problem in the way DECdtm wrote Resource Manager (RM) Log IDs to the Transaction Manager (TM) log. The values written to the TM log were different from those found in the transaction data structures. DECdtm was, in other words, corrupting RM Log IDs when it wrote them to the log. This -- COVER LETTER -- Page 5 18 November 2002 problem was fixed for OpenVMS Alpha V6.1 and 6.2. However, there are customers in possession of older TM logs, i.e. logs generated by older incorrect versions of the facility which contain corrupted RM log ID entries. These customers are experiencing problems when trying to recover/rollback the transactions recorded in these logs. The recovery process fails with a SS$_NOSUCHPART error. This is a workaround for this problem. o When a new transaction is about to be started, the system, already operating under a heavy transaction load, crashes with the contents of the kernel stack invalid. 12 PROBLEMS ADDRESSED IN ALPDDTM02_062 KIT FOR OPENVMS V6.2, V6.2-1H1 ONLY o DECdtm was corrupting RM Log IDs when it wrote them to the log. The values written to the TM (Transaction Manager) log were different from those found in the transaction data structures. o SYS$TRANSACTION_SERVICES causes memory leaks. o After a transient SCS failure, and as the two communicating machines attempt to recover from it, one (or often both) of those machines crashes with an access violation. The crash may occur, depending on the exact timing of the failure with respect to the messaging activity at the time, at a number of accesses to the structures that SCA maintains. o When an attempt to initiate a new SCS block transfer fails (because the target node is unreachable), the sender node crashes shortly afterwards. o During a block transfer, the receiver node crashes with an ACCVIO failure. 13 PROBLEMS ADDRESSED IN ALPDDTM01_062 KIT FOR OPENVMS V6.2, V6.2-1H1 ONLY o With the loss of a virtual circuit connection established between two cluster nodes, there is the potential for a restarting message transfer to result in a machine crash. -- COVER LETTER -- Page 6 18 November 2002 14 KIT INSTALLATION RATING: The following kit 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) INSTALLATION RATING: INSTALL_1 : To be installed by all customers. 15 INSTALLATION INSTRUCTIONS: Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL ALPDDTM06_062 [location of the saveset] The saveset location may be a tape drive, CD, or a disk directory that contains the kit saveset. No reboot is necessary after successful installation of the kit. Copyright (c) Compaq Computer Company, 2002 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. COMPAQ, the COMPAQ logo, VAX, Alpha, VMS, and OpenVMS are registered in the U.S. Patent and Trademark Office. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from COMPAQ are 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. COMPAQ shall not 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 COMPAQ 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 COMPAQ 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.