SEARCH CONTACT US SUPPORT SERVICES PRODUCTS STORE
United States    
COMPAQ STORE | PRODUCTS | SERVICES | SUPPORT | CONTACT US | SEARCH
gears
compaq support options
support home
software & drivers
ask Compaq
reference library
support forum
frequently asked questions
support tools
warranty information
service centers
contact support
product resources
parts for your system
give us feedback
associated links
.
} what's new
.
} contract access
.
} browse patch tree
.
} search patches
.
} join mailing list
.
} feedback
.
patches by topic
.
} DOS
.
} OpenVMS
.
} Security
.
} Tru64 Unix
.
} Ultrix 32
.
} Windows
.
} Windows NT
.
connection tools
.
} nameserver lookup
.
} traceroute
.
} ping
OpenVMS ALPDDTM04_062 Alpha V6.2 DECdtm ECO Summary

TITLE: OpenVMS ALPDDTM04_062 Alpha V6.2 DECdtm ECO Summary NOTE: An OpenVMS saveset or PCSI installation file is stored on the Internet in a self-expanding compressed file. The name of the compressed file will be kit_name-dcx_vaxexe for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha. Once the file is copied to your system, it can be expanded by typing RUN compressed_file. The resultant file will be the OpenVMS saveset or PCSI installation file which can be used to install the ECO. Copyright (c) Compaq Computer Corporation 1998. All rights reserved. Modification Date: 14-Aug-1998 Modification Type: Updated ECO Kit - Supersedes ALPDDTM03_062 PRODUCT: OpenVMS Alpha COMPONENT: DEC Distributed Transaction Manager (DECdtm) SOURCE: Compaq Computer Corporation ECO INFORMATION: ECO Kit Name: ALPDDTM04_062 ECO Kits Superseded by This ECO Kit: ALPDDTM03_062 ALPDDTM03_070 (V6.2 only) ALPDDTM02_070 (V6.2 only) ALPDDTM01_070 (V6.2 only) ALPDDTM02_062 ALPDDTM01_062 AXPDDTM01_061 ECO Kit Approximate Size: 1894 Blocks Saveset A - 1872 Blocks Kit Applies To: OpenVMS Alpha V6.2 through V6.2-1H3 System/Cluster Reboot Necessary: Yes Rolling Re-boot Supported: Yes Installation Rating: 3 - To be installed on all systems running the listed versions of OpenVMS which are experiencing the problems described. Kit Dependencies: The following remedial kit(s) must be installed BEFORE installation of this kit: None In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: None ECO KIT SUMMARY: An ECO kit exists for DEC Distributed Transaction Manager (DECdtm) on OpenVMS Alpha V6.2 through V6.2-1H3. This kit addresses the following problems: 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. 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 editted): 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. 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. 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. 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 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. 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. 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. INSTALLATION NOTES: The images in this kit will not take effect until the system is rebooted. If there are other nodes in the VMScluster, 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.



This patch can be found at any of these sites:

Colorado Site
Georgia Site



Files on this server are as follows:

alpddtm04_062.README
alpddtm04_062.CHKSUM
alpddtm04_062.CVRLET_TXT
alpddtm04_062.a-dcx_axpexe

privacy and legal statement