HP Reliable Transaction Router - Manual (Page 66)

RTR Management
Examples
Example 4–1 The user issues the following commands on the server application
where RTR is running on the backend.
$ RTR
Copyright 1994, 2003 Hewlett-Packard Development Company, L.P.
RTR> set mode/group
%RTR-I-STACOMSRV, starting command server on node NODEA
%RTR-I-GRPMODCHG, group changed from " " to "username"
%RTR-I-SRVDISCON, server disconnected on node NODEA
RTR> CREATE JOURNAL
%RTR-I-STACOMSRV, starting command server on node NODEA in group "username"
%RTR-S-JOURNALINI, journal
has been created on device D:
RTR> SHOW JOURNAL
Journal configuration on NODEA in group "username" at Mon Aug 28 14:54:11 2000:-
Disk: D:\ Blocks: 1000
RTR> start rtr
%RTR-I-NOLOGSET, logging not set
%RTR-S-RTRSTART, RTR started on node NODEA in group "username"
RTR> CREATE FACILITY DESIGN/ALL_ROLES=(NODEA)
[- or /all=NODEA,NODEB]
%RTR-S-FACCREATED, facility DESIGN created
RTR> SHOW FACILITY
Facilities on node NODEA in group "username" at Mon Aug 28 15:00:28 2000:
Facility
Frontend Router Backend
DESIGN yes yes yes
RTR> CREATE PARTITION des_1/FACILITY=DESIGN
%RTR-I-PRTCREATE, partition created
RTR> CREATE PARTITION des_2/FACILITY=DESIGN
%RTR-I-PRTCREATE, partition created
RTR> rtr_open/server/accept_explicit/prepare_explicit/chan=s/fac=DESIGN/part=des_1
%RTR-S-OK, normal successful completion
RTR> RTR_RECEIVE_MESSAGE/CHAN=S
%RTR-S-OK, normal successful completion
channel name: S
.
.
.
msgtype:
rtr_mt_opened
.
.
.
status:
normal successful completion
4–12 RTR Interfaces