Table of Contents
Advertisement
This informs the system administrator that port number 46000/tcp is reserved
for RTR. (Note that the RTR daemon is started by RTRACP and not by
inetd
2.9.3 Interoperation with RTR Version 2 Using DECnet
Reliable Transaction Router is interoperable with RTR Version 2.2D ECO3 or
later when running on a platform that supports DECnet; that is OpenVMS,
Compaq Tru64 UNIX, SUN, Windows 95 or Windows NT.
Note that it is not possible to mix Version 2 and Version 3 routers and backends;
all router and backend nodes in a facility must be either Version 2 or Version 3.
Frontend nodes may be either Version 2 and Version 3.
Defining the facility:
•
On RTR Version 2 node(s):- There are no special requirements for including a
V3.x frontend in a V2 facility definition. Simply add the name of the frontend
to the node-list specified by the /FRONTEND qualifier.
•
On RTR Version 3 node(s):-
The default network transport for RTR Version 3.2 is TCP/IP.
Version 2 uses DECnet (only), you must specify that your RTR Version 3
nodes use the DECnet protocol. This is achieved by prefixing the RTR V2
nodename with the string ''dna.''.
For example, to specify the facility ''FAX1'' on the RTR V3 frontend ''v3fe'' for
which the two V2 routers ''VMS1'' and ''VMS2'' are defined, use the following
command:-
RTR> create facility FAX1 /frontend=v3fe /router=(dna.VMS1,dna.VMS2)
•
Note that the facility name should contain only UPPER-CASE letters on all
nodes if the facility includes nodes running RTR V2.
The use of the ''dna.'' prefix assumes that the default network transport is
TCP/IP. The default network transport can be changed to DECnet by setting the
environment variable RTR_PREF_PROT. On Windows 95 and Windows NT, you
can use one of the following statements in your
set RTR_PREF_PROT=RTR_TCP_FIRST
set RTR_PREF_PROT=RTR_TCP_ONLY
set RTR_PREF_PROT=RTR_DNA_FIRST
set RTR_PREF_PROT=RTR_DNA_ONLY
These set the choice of network transport to TCP/IP with fallback to DECnet,
TCP/IP only, DECnet with fallback to TCP/IP or DECnet only.
For Reliable Transaction Router Version 3.2 for OpenVMS, refer to Section 2.10
for further information))
Trouble-shooting network connections:-
If the RTR V3 frontend fails to connect with the RTR V2 router node, then you
can make a basic check by executing a
OpenVMS router node. If this fails, consult your Network Manager. (For Compaq
Tru64 UNIX machines, ensure that the DECnet library is installed as
/libdna.so
1
For Reliable Transaction Router Version 3.2 for OpenVMS, the default network transport
is DECnet.
).
).
Starting and Setting Up RTR
2.9 Network Transports
.
AUTOEXEC.BAT
from the RTR V3 node to the
dlogin
Starting and Setting Up RTR 2–15
1
Since RTR
/usr/shlib
Advertisement
Table of Contents
