RTR V3.1D RTRA210 RTR for Windows NT and Windows 95 V3.1D ECO Summary
TITLE: RTR V3.1D RTRA210 RTR for Windows NT and Windows 95 V3.1D ECO Summary
Copyright (c) Compaq Computer Corporation 1999. All rights reserved.
PRODUCT: Reliable Transaction Router (RTR) for Windows NT
and Windows 95 (Alpha)
OP/SYS: Windows NT or Windows 95
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: RTRA210
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 4640 Blocks
2375680 Bytes
Kit Applies To: RTR V3.1D
Windows NT V4.0
Windows 95 V4.0
System/Cluster Reboot Necessary: No
Installation Rating: INSTALL_UNKNOWN
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 RTR V3.1D on Windows NT or Windows 95 V4.0. This
kit addresses the following problems:
o Calls to rtr_start_tx() in the Windows platforms would fail with the
error condition INVFLAGS. Attempts to use the RTR V1.1 client API
rtr_error_text() would also fail. This problem is evident in RTR
V3.1D ECO6 and subsequent kits, but has now been corrected.
o RTR crash when ASYNC cable disconnected
Disconnecting a cable that was being used by an asynchronous DECnet
link to a remote machine could result in an ACP failure when the
transport marked the sockets as invalid. RTR has been changed to
handle this error by temporarily suspending all network activity on
the affected node. Network activity will resume as soon as the
network is found to be usable again.
o Router crash when link to Frontend disconnected
Router ACPs configured to accept anonymous clients could under
circumstances fail when handling a network link loss event. This has
been corrected.
o New environment variables for adjusting connection timeout parameter
Two new environment variables have been created to give operators
greater discretion in determining how long to wait before retrying a
network connection attempt.
The RTR_TIMEOUT_CONNECT variable controls how long a connecting node
will wait for a response from the connectee to its link initiation
request. This value defaults to 60 seconds.
If the RTR_TIMEOUT_CONNECT period expires without a response from
the connectee, RTR will wait an additional period determined by the
RTR_TIMEOUT_CONNECT_RELAX variable. This variable defaults to a
value of 90 seconds. The purpose of the "relax" period is to allow
the connector to accept a connection request from the connectee
node, if any are forthcoming. It is important not to set this value
too low on Backends and Routers, as such machines are likely to be
receiving connection requests from many other machines. On machines
configured to use only the Frontend role, however, you can safely
set RTR_TIMEOUT_CONNECT_RELAX to just a few seconds so that the node
can be free to attempt to connect to another router as quickly as
possible.
The minimum value for RTR_TIMEOUT_CONNECT is 5 and the minimum for
RTR_TIMEOUT_CONNECT_RELAX is 1.
The following restrictions apply to this kit:
o A temporary inconsistency in shadow server state can occur during
initial facility startup of a shadowed configuration. A shadow
server can erroneously remain in state "sec_act" until the rest of
the facility has been started.
o An application's wakeup routine may be called more often than
necessary.
INSTALLATION NOTES:
The Reliable Transaction Router V3.1D ECO installation procedure is the
same as the installation procedure for RTR V3.1D. Please refer to the
Installation Guide for further information.
All trademarks are the property of their respective owners.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
rtra210.README
rtra210.CHKSUM
rtra210.CVRLET_TXT
rtra210.zip
|
