
RTR Management
Example 4–3 Commands and system response at client.
$ RTR
RTR> START RTR
%RTR-S-RTRSTART, RTR started on node NODEA in group "username"
RTR> RTR_OPEN_CHANNEL/CHANNEL=C/CLIENT/fac=DESIGN/partition=des_1
%RTR-S-OK, normal successful completion
RTR> RTR_RECEIVE_MESSAGE/CHANNEL=C/tim
[to get mt_opened or mt_closed]
%RTR-S-OK, normal successful completion
channel name: C
msgsb
msgtype:
rtr_mt_opened
msglen:
8
message
status:
normal successful completion
reason:
Ox00000000
RTR> RTR_START_TX/CHAN=C
%RTR-S-OK, normal successful completion
RTR> RTR_SEND_TO_SERVER/CHAN=C "Kathy’s text today." [text sent to the server]
%RTR-S-OK, normal successful completion
RTR> show transaction
Frontend transactions on node NodeA in group "username" at Mon Aug 28 15:05:43 2000
Tid
Facility
FE-User
State
63b01d10,0,0,0,0,2e59,43ea2002
DESIGN
username.
SENDING
Router transactions on node NodeA in group "username" at Mon Aug 28 15:06:43 2000:
63b01d10,0,0,0,0,2e59,43ea2002
DESIGN
username.
SENDING
Backend transactions on node NodeA in group "username" at Mon Aug 28 15:06:43 2000:
63b01d10,0,0,0,0,2e59,43ea2002
DESIGN
username.
SENDING
RTR> RTR_RECEIVE_MESSAGE/TIME=0/CHAN=C
4–14 RTR Interfaces