Filter
Top Products
3
Architectural Changes
RTR Version 3 introduces certain process and other architectural changes. The
following sections highlight these changes.
3.1 RTR Daemon Process
In RTR Version 3, a new RTR daemon process (called RTRD) is used by the
RTRACP process to build TCP/IP connections for internode links. The RTR
daemon process is present only on systems with IP networking installed and with
IP enabled as an RTR transport (see Chapter 4, Network Issues, for information
on setting your network transport).
3.2 Command Server Process
The command server process name is RTRCSV_<username>.
In RTR Version 2, a command server was started for every user login invocation
to RTR to enter operator commands. With RTR Version 3 there is one command
server per node for each user logged in through a common user name.
Note
Command server timeouts are the same in RTR V3 as in RTR V2.
3.3 The Shared Library (LIBRTR.EXE)
In RTR Version 3, LIBRTR supersedes RTRSHR. This library module LIBRTR
contains most of the RTR code, in contrast with RTR Version 2, where only
RTR code specific to application context was contained in RTRSHR. All RTR
Version 2 binaries have been superseded by the two executables LIBRTR.EXE
and RTR.EXE, in RTR Version 3. Table 3–1 shows the executables of RTR
Version 2 and Version 3.
Table 3–1 RTR Executables
RTR Version 2 RTR Version 3
RTRSHR LIBRTR
RTR RTR
RTRCOMSERV Now part of LIBRTR.
RTRACP Now part of LIBRTR.
(continued on next page)
Architectural Changes 3–1