|
|
RTR V4.1 RTRVVME01041 Reliable Transaction Router VAX ECO Summary
|
TITLE: RTR V4.1 RTRVVME01041 Reliable Transaction Router VAX ECO Summary
Modification Date: 29-NOV-2001
Modification Date: 21-MAR-2002
Modification Type: kit has been moved back to Public area
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
For OpenVMS savesets, the name of the compressed saveset
file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
saveset is copied to your system, expand the compressed
saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
For PCSI files, once the PCSI file is copied to your system,
rename the PCSI file to kitname.pcsi-dcx_axpexe, then it can
be expanded by typing RUN kitname.pcsi-dcx_axpexe. The resultant
file will be the PCSI installation file which can be used to install
the ECO.
Copyright (c) Compaq Computer Corporation 2001. 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: RTRVVME01041
DEC-VAXVMS-RTR-V0401-303-1.PCSI
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 16,112 Blocks
Kit Applies To: Reliable Transaction Router V4.1
OpenVMS VAX V6.2,V6.2-0HF,V7.0,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:
An ECO kit exists for Reliable Transaction Router V4.1 on OpenVMS
VAX V6.2 through V7.3.
The following changes and corrections have been made for
RTR V4.1, ECO1 for all platforms.
o 14-1-1766, 14-8-406 BE losing quorum
In some cases, a backend might lose quorum when
comparing failed and unreachable routers with the number
of routers in a facility. This has been fixed. However,
when a TRIM FACILITY command is used to remove a role
on a backend, the backend will lose quorum for a moment.
In the interval, an SRSTANDBY event may be visible,
indicating that the application does not have an active
role at that moment. This is expected behavior because
changing a role redefines the facility and RTR must
re-calculate quorum.
o 14-3-403, 14-8-372, 14-8-386 A rogue master may retain
old quorum info
A rogue master may keep old quorum information, causing
the quorate count in MONITOR QUORUM to be incorrect.
This has been fixed.
o 14-5-219, 14-8-348, 14-8-390 Router failure when unable
to create a network object
RTR could not create a facility that used multiple nodes
in a TCP/IP-only environment. This has been fixed.
o 14-5-244 Pass facility and link names with NCF-based RTR
events
Certain RTR events are now accompanied by a message
naming the affected facility and node. Should this
additional data disrupt an existing application,
the feature can be disabled by defining the variable
RTR_NO_NCF_EVENT_DATA in the environment of all ACP
processes in the configuration. The following events are
subject to this behavior: FACREADY, FACDEAD, FERTRLOSS,
FERTRGAIN, RTRBEGAIN, RTRBELOSS, BERTRGAIN, BERTRLOSS,
RTRFEGAIN, RTRFELOSS.
For example, a server channel may subscribe to these
events and use this information to maintain a database
of who is connected. The following is an example (in
script) of these events being received on a server
channel:
RTR> call rece
%RTR-S-OK, normal successful completion
channel name: RTR$DEFAULT_CHANNEL
msgsb
msgtype: rtr_mt_rtr_event
msglen: 34
evtnum: 107 (RTR_EVTNUM_RTRFELOSS)
message
facility: RTR$DEFAULT_FACILITY
link: 16.47.196.81
RTR> call rece
%RTR-S-OK, normal successful completion
channel name: RTR$DEFAULT_CHANNEL
msgsb
msgtype: rtr_mt_rtr_event
msglen: 34
evtnum: 106 (RTR_EVTNUM_RTRFEGAIN)
message
facility: RTR$DEFAULT_FACILITY
link: 16.47.196.81
The events only broadcast connectivity changes. On
startup, the server may need to initialize its database
of who is currently connected. Depending on the
requirements, it may suffice to have a server solicit
this information with a broadcast when it starts up.
All clients receiving the broadcast would respond with
a registration message allowing the servers to learn if
they are connected.
o 14-8-401 Failed node journal not released
RTR no longer hangs when attempting to access the
journal held by a failed node.
o 14-8-405 RTR BE node failure resolution
A wrong check on message size at the time of shadow
recovery could cause a node to fail. The problem can
occur during fast recovery when message size reaches
maximum size. This is now fixed.
o 14-8-409 RTR process using up CPU time
RTR could consume a large amount of CPU time if the RTR
CLI process encountered an EIO or unrecoverable error
while reading from the terminal.
RTR no longer does this; it now exits instead of
retrying when the RTR CLI encounters an unrecoverable
error. The operator log will contain the error status
that caused the CLI to exit.
o 14-8-411 SHOW FACILITY
SHOW FACILITY now more accurately displays V2 format.
The following changes and corrections have been made in RTR
V4.1, ECO1 for the OpenVMS platform.
o 14-3-424, 14-8-410 RTR does not set the $status system
variable on OpenVMS, SHOW FACILITY, SHOW LINK exit
status
When processing SHOW FACILITY and SHOW LINK commands,
the RTR utility now sets its exit status if either the
specified item is absent or no instances of the item
class exist. Command parsing errors now cause a correct
exit status severity to be set. These changes restore
functionality found in earlier versions of RTR.
With RTR V2, this command returns %X100B8E22 and the
message %RTR-E-NOFACILIT, no facilities have been
defined. With RTR V4, there is no error, and the status
is successful.
o 14-8-402 TCP/IP NULL Alias Names
On OpenVMS systems it was possible for an alias name
to be NULL when running TCP/IP. This caused RTR to
associate an incorrect hostname/IP address pair. RTR
now skips NULL alias names when looking up the alias
address.
Known Problems with Workarounds
-------------------------------
The following known problem with workaround applies to all
platforms.
o 14-3-235 Changing system time may cause problems
RTR may experience internal problems if the system
time is changed in large increments. Compaq recommends
changing the system clock in increments no larger than
five minutes until the desired system time is achieved.
INSTALLATION NOTES:
The Reliable Transaction Router Version 4.1 ECO1 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.
Files on this server are as follows:
|
»dec-vaxvms-rtr-v0401-303-1.README
»dec-vaxvms-rtr-v0401-303-1.CHKSUM
»dec-vaxvms-rtr-v0401-303-1.pcsi-dcx_vaxexe
»rtrvvme01041.CVRLET_TXT
|