ECO NUMBER: VAXDDTM02_062 PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: VAXDDTM02_062 2 KITS SUPERSEDED BY THIS KIT: VAXDDTM01_062 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) 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 should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS VAX V6.2 4.2 Files patched or replaced: o [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE (new image) o [SYSEXE]TPSERV.EXE (new image) 5 PROBLEMS ADDRESSED IN VAXDDTM02_062 KIT o The VAXDDTM01_062 remedial kit included SYS$IPC_SERVICES.EXE to fix an SCS problem. Since this problem is IPC specific, it is being removed from the DDTM kit and moved to the IPC-specific remedial kit, VAXIPC01_062. This remedial kit has no new problem corrections. It is simply a re-packaging. If you have installed the VAXDDTM01_062 kit, then this VAXDDTM02_062 kit does not need to be installed. -- COVER LETTER -- Page 2 27 May 1999 o The DTI$SHARE.EXE image is included in the VAXDDTM01_062 kit, but it is not needed. Consequently it is not included in this kit. 6 PROBLEMS ADDRESSED IN VAXDDTM01_062 KIT o System bootup cannot start TP_SERVER. Manually starting it with DECDTM$STARTUP failed with an STR-F-ERRFREDYN error. 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): 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 -- COVER LETTER -- Page 3 27 May 1999 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. 7 PROBLEMS ADDRESSED IN VAXDDTM01_070 KIT FOR OPENVMS VAX V6.2 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. 8 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_3 : To be installed by customers experiencing the problems corrected. 9 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 VAXDDTM02_062 [location of the saveset] The saveset location may be a tape drive, CD, or a disk directory that contains the kit saveset. The images in this kit will not take effect until the system is rebooted. 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. -- COVER LETTER -- Page 4 27 May 1999 Copyright (c) Compaq Computer Corporation, 1999 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Compaq Computer Corporation. 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.