New Features and Problems Fixed
1.2 RTR Version T5.2 EFT1
When the
MONITOR
command is executed on a transaction router node, the
monitor picture displays all the front-ends currently connected to the router.
The
MONITOR
command for trtofe.mon supports a new qualifier,
PERFACILITY
that displays the connected front-ends at the facility level.
For example,
$ RTR MONITOR TRTOFE /PERFACILITY=TEST
• HP Reliable Transaction Router for Microsoft Windows x86_64
RTR (32-bit) is now qualified on Windows x86_64 operating system.
• RTR’s scalability to overcome network bandwidth constraints
In an RTR configuration that comprises of several systems with transaction
routers and back-end nodes, the network must have sufficient bandwidth to
carry the RTR management messages and application payloads. Insufficient
network bandwidth will result in RTR buffering the data, which may
eventually lead to its failure because of the non availability of memory.
To overcome this problem, RTR selectively compresses the data packets
to reduce the load on the network. This feature is available through an
environment variable,
RTR_COMPRESS_PCKT
, which takes Boolean value. By
default, this feature is disabled.
To increase the efficiency of compression, you can also use the environment
variable,
RTR_COMPRESS_PCKT_THRESHOLD
to select the minimum size of the
packet that has to be compressed. The packets with size greater than or equal
to
RTR_COMPRESS_PCKT_THRESHOLD
will be compressed and smaller packets
will not be compressed.
• HP Reliable Transaction Router supports 64-bit library on OpenVMS
(Integrity servers)
RTR is enhanced to extend the memory allocation capacity of RTR processes
by supporting 64-bit pointers.
The 32-bit applications that use V3/V2 API does not require recompilation or
relinking to work with the 64-bit RTR library. An existing application, based
on V3/V2 API, that is compiled with a 32-bit and linked with an old RTR
library can work seamlessly with the 64-bit library.
To make use of the 64-bit pointers, the applications will require recompilation
with the
pointer_size=64
qualifier of the C/C++ compiler.
Restriction
Applications that use V2 API cannot be compiled with the
pointer_size=64
qualifier because RTR does not support this API in the 64-bit format.
Applications will have to migrate to V3 API to make use of 64-bit pointers on
OpenVMS.
1.2.2 Problems Fixed
This section describes the problem fixed in this release:
• When the
RTR$SNAPSHOT
command procedure is executed, the RTRCLI crashes
with an ACCVIO error.
This problem has been fixed in this release.
• In a rare failover condition, the back-end transactions in the DONE state are
not cleaned up because of the pending forget message from the transaction
router.
New Features and Problems Fixed 1–3
(28 Seiten)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern