Example 4–4 The following lines arrive at the client from RTR after the user enters
commands at the server.
%RTR-S-OK, normal successful completion
channel name: C
msgsb
msgtype:
rtr_mt_reply
msglen:
25
usrhdl:
0
tid:
63b01d10,0,0,0,0,2e59,43ea2002
message
offset bytes
000000 41 6E 64 20 74 68 69 73 20 69 73 20 6D 79 20 72 And this is my r
000010 65 73 70 6F 6E 73 65 2E 00
RTR> RTR_ACCEPT_TX/CHANNEL=C
%RTR-S-OK, normal successful completion
RTR> show transaction
Frontend transactions on node NodeA in group "username" at Mon Aug 28 15:17:45 2000
Tid
63b01d10,0,0,0,0,2e59,43ea2002
Router transactions on node NodeA in group "username" at Mon Aug 28 15:17:45 2000:
63b01d10,0,0,0,0,2e59,43ea2002
Backend transactions on node NodeA in group "username" at Mon Aug 28 15:17:45 2000:
63b01d10,0,0,0,0,2e59,43ea2002
RTR> RTR_RECEIVE_MESSAGE
%RTR-S-OK, normal successful completion
channel name: S
.
.
.
msgtype: rtr_mt_accepted
.
.
.
RTR> STOP RTR
Facility
FE-User
DESIGN
username.
DESIGN
username.
DESIGN
username.
RTR Management
text
esponse..
State
VOTING
VOTING
COMMIT
RTR Interfaces 4–15