|
|
 |
OpenVMS VAXDDTM02_062 VAX V6.2 DECdtm ECO Summary
|
TITLE: OpenVMS VAXDDTM02_062 VAX 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, 1999. All rights reserved.
Modification Date: 03-JUN-99
Modification Type: Updated Kit Supersedes VAXDDTM01_062
PRODUCT: OpenVMS VAX
COMPONENT: DEC Distributed Transaction Manager
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXDDTM02_062
ECO Kits Superseded by This ECO Kit: VAXDDTM01_062
VAXDDTM01_070 (For VAX
V6.2 *ONLY*)
ECO Kit Approximate Size: 288 Blocks
Kit Applies To: OpenVMS VAX V6.2
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 DECdtm on OpenVMS VAX V6.2.
Problems addressed in VAXDDTM02_062:
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.
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.
Problems addressed in VAXDDTM01_062:
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 $TRNLM)
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.
Problems Addressed in VAXDDTM01_070 for OpenVMS V6.2 ONLY:
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.
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.
All trademarks are the property of their respective owners.
|
Files on this server are as follows:
|
»vaxddtm02_062.README
»vaxddtm02_062.CHKSUM
»vaxddtm02_062.CVRLET_TXT
»vaxddtm02_062.a-dcx_vaxexe
»vaxddtm02_062.CVRLET_TXT
|
