Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
DEC-VAXVMS-RTR-V0401-332 Reliable Transaction Router (VAX) ECO Su
*RTR V4.1] DEC-VAXVMS-RTR-V0401-332 Reliable Transaction Router (VAX) ECO Summary
New Kit Date: 26-JUL-2002
Modification Date: Not Applicable
Modification Type: NEW KIT
Copyright (c) Compaq Computer Corporation 2001,2002. All rights reserved.
PRODUCT: Reliable Transaction Router V4.1 for OpenVMS VAX
OP/SYS: OpenVMS VAX
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: DEC-VAXVMS-RTR-V0401-332
DEC-VAXVMS-RTR-V0401-332-1.PCSI
ECO Kits Superseded by This ECO Kit: DEC-VAXVMS-RTR-V0401-303-1.PCSI
ECO Kit Approximate Size: 16,480 Blocks
Kit Applies To: Reliable Transaction Router V4.1
OpenVMS VAX V6.2,V7.1,V7.2 and V7.3
System/Cluster Reboot Necessary: Information Not Available
Rolling Re-boot Supported: Information Not Available
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:
This ECO includes all corrections from RTR V4.1 ECO1. For a detailed
description of the corrections, please see the RTR V4.1 ECO1
Release Notes.
The following changes and corrections have been made in RTR V4.1 ECO3
for all platforms.
o 14-5-304 Journal file locked by isolated RTR backend
This release contains code to resolve a problem where an
RTR backend, that becomes isolated from the network, can
block access to its journal by other cluster members,
thereby defeating RTR standby takeover.
In V4.1 ECO3, this feature must be explicitly enabled
through the following environment variable definition:
Variable: RTR_JNL_RETAIN_MODE
Value: 1
This implementation resolves the journal access conflict
by shutting down RTR on the isolated node. A more
complete implementation allowing for recovery from
the isolation condition will be made available with a
subsequent release.
The following changes and corrections have been made in RTR
V4.1, ECO3 for the OpenVMS platform.
o 14-3-442 Extraneous TCP related RTR daemon process when
running only DECnet
Introduction
When installing RTR the following installation output
appears, (for "V4.x", x is replaced with the minor version
number):
DEC AXPVMS RTR V4.x: Reliable Transaction Router for
OpenVMS
Insert the following line in SYS$MANAGER:SYSTARTUP_VMS.COM:
@sys$startup:rtr$startup.com
Insert the following line in SYS$MANAGER:SYSHUTDWN.COM:
@sys$manager:rtr$shutdown
________________________ Note ________________________
The following section describes P1 usage.
______________________________________________________
P1 Usage
Within RTR$STARTUP.COM, the symbol RTR_PREF_PROT is used to
define the preferred network protocol.
The four choices are:
- RTR_DNA_FIRST (DECnet first)
- RTR_DNA_ONLY (DECnet only)
- RTR_TCP_FIRST (TCP/IP first)
- RTR_TCP_ONLY (TCP/IP only)
By default the link protocol preference is:
RTR_DNA_FIRST if SYS$NODE is defined (indicating DECnet
is installed)
RTR_TCP_ONLY if SYS$NODE is undefined (indicated DECnet
is not installed)
________________________ Note ________________________
This default behavior remains unchanged and is
backward compatible with previous versions of RTR.
______________________________________________________
Formerly, the RTR system manager was allowed to override
the default behavior by removing the comment character
(!) from the appropriate DEFINE statement within
RTR$STARTUP.COM. This is no longer valid, available or
supported.
To override the default behavior, insert the following line
in SYS$MANAGER:SYSTART_VMS.COM:
@sys$startup:rtr$startup.com P1
Optional parameter P1 is one of the following values:
- RTR_DNA_FIRST (DECnet first)
- RTR_DNA_ONLY (DECnet only)
- RTR_TCP_FIRST (TCP/IP first)
- RTR_TCP_ONLY (TCP/IP only)
Example:
@sys$startup:rtr$startup.com RTR_TCP_FIRST
Advantages
1. Previously, overriding the default behavior by modifying
RTR$STARTUP.COM required the RTR system manager to
change the RTR$STARTUP.COM file on each system after
every RTR upgrade or install. (This was necessary
because each install/upgrade created a new, unmodified
copy of RTR$STARTUP.COM).
Using the P1 parameter option eliminates this overhead
as the required value passed into RTR$STARTUP.COM within
SYS$MANAGER:SYSTARTUP_VMS.COM is left unchanged by an
RTR install or upgrade.
2. RTR$SHUTDOWN.COM logic is designed to internally detect
which P1 value was passed into RTR$STARTUP.COM and shuts
RTR down accordingly.
3. In the unlikely circumstances where RTR$SHUTDOWN.COM
cannot properly detect the preferred protocol preference
value of RTR_PREF_PROT (passed to P1 during RTR startup)
the RTR system manager can explicitly pass this value
to RTR$SHUTDOWN.COM to ensure proper RTR shutdown as
follows:
Insert the following line in SYS$MANAGER:SYSHUTDOWN.COM:
@sys$startup:rtr$shutdown.com P1
Optional parameter P1 is one of the following values:
- RTR_DNA_FIRST (DECnet first)
- RTR_DNA_ONLY (DECnet only)
- RTR_TCP_FIRST (TCP/IP first)
- RTR_TCP_ONLY (TCP/IP only)
Example:
@sys$startup:rtr$shutdown.com RTR_TCP_FIRST
________________________ Note ________________________
This behavior is not expected and would occur only if
the symbol RTR_PREF_PROT and/or the system logical
"SYS$NODE" were externally modified in a way not
expected under normal and usual operating conditions.
This Option is provided as a workaround to an
unexpected and unlikely scenario in order to keep
RTR startup and shutdown operations robust and
predictable.
______________________________________________________
Bug Fix
Under certain circumstances, running RTR$SHUTDOWN.COM to
shut down RTR created an extraneous TCP-related RTR daemon
process when running only DECnet. This behavior has been
corrected along with the P1 parameter modifications.
Known Problems with Workarounds
-------------------------------
There are no known problems with workarounds that are specific to
this platform.
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool. If you are not familiar with how to request
kits electronically, open the DIA, WIS or DSNLINK database and
review the article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
INSTALLATION NOTES:
The Reliable Transaction Router Version 4.1 ECO3 installation
procedure is the same as the installation procedure for RTR Version
4.1. Refer to the Installation Guide for further information.
All trademarks are the property of their respective owners.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| RTR.EXE |%XB1E56211| V4.1(332)ECO3 | 11-JUL-2002 |
| | | 13:14:08.65 |
+----------------------------+----------+-----------------+--------------+
| RTRV2MSG.EXE |%X6AE8D8E3| VERSION 0.1 | 11-JUL-2002 |
| | | 13:14:32.42 |
+----------------------------+----------+-----------------+--------------+
|
