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
RTR V3.1D RTRAVME08D Reliable Transaction Router Alpha ECO Summary

TITLE: RTR V3.1D RTRAVME08D Reliable Transaction Router Alpha ECO Summary *RTR V3.1D] RTRAVME08D Reliable Transaction Router (Alpha) ECO Summary Copyright (c) Compaq Computer Corporation 1998. All rights reserved. Modification Date: 02-FEB-99 Modification Type: Reloaded Binary file PRODUCT: Reliable Transaction Router V3.1D for OpenVMS Alpha (RTR) OP/SYS: DIGITAL OpenVMS Alpha COMPONENTs: RTR.EXE LIBRTR.EXE SOURCE: Compaq Computer Corporation ECO INFORMATION: ECO Kit Name: RTRAVME08D ECO Kits Superseded by This ECO Kit: None. ECO Kit Approximate Size: 6140 Blocks 3143680 Bytes Kit Applies To: RTR V3.1D for OpenVMS Alpha OpenVMS Alpha V6.1, V6.2, V7.0, V7.1 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 Reliable Transaction Router on OpenVMS Alpha V6.1 through V7.1. This kit addresses the following problems: o 14-8-144 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 14-8-154 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 14-8-155 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 14-1-285: 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 14-3-67: An application's wakeup routine may be called more often than necessary. INSTALLATION NOTES: The Reliable Transaction Router installation procedure uses the POLYCENTER Software Installation Utility (PCSI). For details on using PCSI, refer to the OpenVMS System Manager's Manual, Section "Installing with the POLYCENTER Software Installation Utility". The logical name PCSI$SOURCE is used to define the location of the software kits you want to install. For example, if the Reliable Transaction Router software is located in DISK1:[KITS], enter the following at the DCL prompt (or include the line in the system manager's login command file): $ DEFINE PCSI$SOURCE DISK1:[KITS] When running the installation procedure for Reliable Transaction Router, you can choose whether to install the ODBC Over RTR Oracle7 Server. This is an RTR server used for supporting ODBC-enabled applications on Windows. You should not install the ODBC Over RTR Oracle7 Server unless you already have Oracle7 installed. To start the installation, type the command: $ PRODUCT INSTALL RTR You will see a display similar to the following: The following product has been selected: DEC AlphaVMS RTR V3.1-D176 [Available] Do you want to continue? [YES] Press . You may safely accept the installation default options.



This patch can be found at any of these sites:

Colorado Site
Georgia Site



Files on this server are as follows:

dec-axpvms-rtr-v0301-d210-1.README
dec-axpvms-rtr-v0301-d210-1.CHKSUM
dec-axpvms-rtr-v0301-d210-1.CVRLET_TXT
dec-axpvms-rtr-v0301-d210-1.exe

privacy and legal statement