Reliable Transaction Router
Application Design Guide

A
Abort
Accept processing
Accepting a transaction
ACCEPT_FORGET
Access key
API
Application programming interface
Authentication
Availability
B
Blocking receive
C
C++ API
and RTR Technology
Callout server
Changing transaction state
Channel
Channel identifier
Channel-open operation
Client/server application
Cluster
Clusters
Command line interface
Commit grouping
Commit sequence
Commit sequence number
Compound keys
Concurrent servers #1
Concurrent servers #2
Coordinating transactions
Create Facility command
Create Facility command
CSN
D
Data-content routing #1
Data-content routing #2
Data retention
Database
Deadly embrace
DECdtm
Design
C++ API
Dual-rail setup
E
Ending a transaction
Error conditions
Event numbers
Examples directory
Exception transaction handling
F
Failover #1
Failover #2
Firewall
Flags parameter
H
Hardware constraints
Host-based clusters
I
Identifying a transaction
Input logging
Inquorate
J
Journal #1
Journal #2
accessibility
K
Key range #1
Key range #2
Key segments
number of
L
Location transparency
Locks
M
Management routines
Message
processing sequence
reception styles
status
types
Messaging #1
Messaging #2
middleware
Middleware
MS DTC
mt.rtr.event #1
mt.rtr.event #2
Multi-threading #1
Multi-threading #2
Multihome setup
Mutexes
N
Nested transactions #1
Nested transactions #2
Network card
O
Object-oriented design
OO Benefits
Oracle database
Oracle SQL
P
Partition #1
Partition #2
Partition #3
Partitioning #1
Partitioning #2
Point-to-point broadcast messaging
Polled receive #1
Polled receive #2
Pseudo-clusters
Q
Quorate
Quorum node
R
RAID
READONLY
Reason code
Recipient name
Recovery
Rejecting a transaction
Release Notes
REPLYDIFF option
Resource managers
Router configuration
Row contention
RTR$DEFAULT_FACILITY
rtr_accept_tx() call
rtr_close_channel
rtr_error_text call
RTR_EVTNUM #1
RTR_EVTNUM #2
RTR_EVTNUM_SRPRIMARY
RTR_EVTNUM_USERDEF
RTR_F_OPE_CLIENT
RTR_F_OPE_EXPLICIT_ACCEPT #1
RTR_F_OPE_EXPLICIT_ACCEPT #2
RTR_F_OPE_EXPLICIT_PREPARE #1
RTR_F_OPE_EXPLICIT_PREPARE #2
RTR_F_OPE_NOCONCURRENT flag
RTR_F_OPE_NOSTANDBY
RTR_F_OPE_SERVER #1
RTR_F_OPE_SERVER #2
RTR_F_OPE_SHADOW flag
RTR_F_SEN_EXPENDABLE flag
RTR_F_SEN_RETTOSEND flag
rtr_get_tid() call
rtr_mt_msg1_uncertain messages
rtr_mt_prepare
rtr_mt_prepare message type
RTR_NO_ACCESS
RTR_NO_NUMSEG
RTR_NO_PKEYSEG
RTR_NO_RCPNAM
RTR_NO_RCPSPC #1
RTR_NO_RCPSPC #2
rtr_reject_tx() call
rtr_reply_to_client() call
rtr_send_to_server
rtr_set_wakeup
rtr_start_tx
RTR_STS_COMSTAUNO
RTR_STS_DLKTXRES
RTR_STS_FELINLOS
RTR_STS_INVFLAGS
RTR_STS_NODSTFND
RTR_STS_REPLYDIFF
RTR_STS_SRVDIED #1
RTR_STS_SRVDIED #2
RTR_STS_SRVDIED #3
RTR_STS_SRVDIEDCOM
RTR_STS_SRVDIEDVOT
RTR_STS_TIMOUT
S
Security
Semaphores
Sequence number
commit
Serialization #1
Serialization #2
Server
callout
Servers
concurrent #1
concurrent #2
standby #1
standby #2
standby support
Setup:dual-rail
Setup:multihome
Signaled receive
Single input
Single resource
SMP environment
SQL
Standby
Standby support
Starting a transaction
Storage device failure
Strikes
three #1
three #2
Symmetric Multiprocessing (SMP) systems
T
Threads
multiple
Three strikes #1
Three strikes #2
Tie-breaker node
Tight coupling
Time-to-failover
Transaction
concepts
ID
identifying
processing
recovery
serialization and partitioning #1
serialization and partitioning #2
Transaction family
child
parent
siblings
Transaction processing
Transaction state
changing #1
changing #2
Transaction timeout
server-side
Transactional
message processing
messages
Transactions
accepting
committing
coordinating
nested
sending
starting
uncertain
True clusters