Filter
Top Products
RTR Management
Example 4–2 When the next command is issued, RTR waits for the message from the
client, which does not appear until after the client sends it (Example
4-3).
RTR> RTR_RECEIVE_MESSAGE/CHAN=S
%RTR-S-OK, normal successful completion
channel name: S
msgsb
msgtype: rtr_mt_msg1
msglen: 19
usrhdl: 0
Tid: 63b01d10,0,0,0,0,2e59,43ea2002
message
offset bytes text
000000 4B 61 74 68 79 27 73 20 74 65 78 74 20 74 6F 64 Kathy’s text tod
000010 61 79 00 ay.
reason: Ox00000000
RTR> RTR_REPLY_TO_CLIENT/CHAN=S "And this is my response."
%RTR-S-OK, normal successful completion
RTR> show transaction
Frontend transactions on node NodeA in group "username" at Mon Aug 28 15:12:10 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:12:10 2000:
63b01d10,0,0,0,0,2e59,43ea2002 DESIGN username. SENDING
Backend transactions on node NodeA in group "username" at Mon Aug 28 15:12:10 2000:
63b01d10,0,0,0,0,2e59,43ea2002 DESIGN username. RECEIVING
RTR> RTR_RECEIVE_MESSAGE/CHAN=S
%RTR-S-OK, normal successful completion
channel name: S
msgsb
msgtype: rtr_mt_prepare
[if OK, use: RTR_ACCEPT_TX
else, use: RTR_REJECT_TX]
RTR> RTR_RECEIVE_MESSAGE/TIME=0
RTR> STOP RTR [Ends example test.]
RTR Interfaces 4–13