hp Reliable Transaction Router
Application Design Guide

A
Abort
Accept processing
Accepting a transaction
ACCEPT_FORGET
Access key
ACID compliance #1
ACID compliance #2
Application programming interface
Authentication
Availability
B
Batch procedures
Blocking receive
Broadcast
messaging #1
messaging #2
messaging #3
processes
RTR events
user events
recovery
sequencing
C
C++ API
and RTR Technology
Callout server #1
Callout server #2
Changing transaction state
Channel identifier
Channel-open operation
Channels
Client/server application
Cluster #1
Cluster #2
Command line interface
Commit grouping
Commit sequence
Commit sequence number
Compound keys
Concurrent servers #1
Concurrent servers #2
Concurrent servers #3
Concurrent servers #4
Concurrent servers #5
Coordinating transactions
Create Facility command
Create Facility command
CSN
D
Data-content routing #1
Data-content routing #2
Data marshalling
Data retention
Database
Database locks
Deadly embrace
DECdtm
Design
C++ API
for performance
Dual-rail setup
Refer to the RTR System Manager's Manual
E
Ending a transaction
Error codes
Error conditions
Event numbers
Events
RTR
user
Examples directory
Exception transaction handling
F
Failover #1
Failover #2
server
Failure
node
router
server
Firewall
Flags parameter
Flow control
H
Hardware constraints
Host-based clusters
I
Idempotency
Identifying a transaction
Input logging
Inquorate
J
Journal #1
Journal #2
accessibility
sizing
Journal sizing
Refer to the RTR System Manager's Manual.
K
Key range #1
Key range #2
Key segments
number of
L
Location transparency
Locks
using #1
using #2
M
Management routines
Marshalling
data
Message
fan-out
processing sequence
reception styles
status
types #1
types #2
Messaging #1
Messaging #2
broadcast #1
broadcast #2
broadcast #3
middleware
Middleware
MS DTC
mt.rtr.event #1
mt.rtr.event #2
Multithreading #1
Multithreading #2
Mutexes
N
Node failure
O
Object-oriented design
OO Benefits
Oracle database
Oracle SQL
P
Partition #1
Partition #2
Partition #3
Partitioning #1
Partitioning #2
Performance tests #1
Performance tests #2
Point-to-point broadcast messaging
Polled receive #1
Polled receive #2
Procedures
batch
Protocol
XA
Pseudo-clusters
Q
Quorate
Quorum node
R
RAID
READONLY
Reason code
Receive model
See message reception styles.
Recipient name
Recovery
broadcast
transaction
Rejecting a transaction
Release Notes
REPLYDIFF option
Resource managers
Router
configuration
failure
placement
Row contention
RTR$DEFAULT_FACILITY
RTR events
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
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
failover
failure
Servers
callout
concurrent #1
concurrent #2
concurrent #3
concurrent #4
concurrent #5
concurrent #6
shadow #1
shadow #2
shadow #3
standby #1
standby #2
standby #3
standby #4
standby support
Shadow server
Shadow servers
Signaled receive
Single input
Single resource
SMP environment
SQL
Standby
Standby server
Standby servers
Standby support
Starting a transaction
Storage device failure
Strikes
three #1
three #2
Symmetric Multiprocessing (SMP) systems