Redpaper - IBM Redbooks

The batch jobs provided work for the brokers for two minutes. The results from
the SupportPac IP13 measurements and the Message Broker statistics recorded
are displayed in Table 4-1.
Table 4-1 SupportPac IP13 and Message Broker statistics
IP13 Statistics MVSM0 MVSM2 Total
Total Transactions 9884 9568 19450
Elapsed Time (seconds) 119.942 119.615
Application CPU Time (seconds) 9.419 11.479
Transaction Rate (trans/sec) 82.406 79.973
Round trip per msg (ms) 12.134 12.504
Average App CPU per msg (ms) 0.952 1.199
Broker Statistics WMQ0BRK WMQ2BRK
Total Number Input Messages 9234 10216 19450
Total Elapsed Time (seconds) 96.401 98.762
Total CPU Time (seconds) 31.590 33.167
Conclusions
From the results, we concluded the following:
► The total number of transactions processed by the SupportPac IP13
applications on both systems equals the total number of messages processed
by each of the two brokers.
► A greater number of SupportPac IP13 application transactions are processed
by the MVSM0 LPAR, while a greater number of messages are processed by
the broker on MVSM2. This slight imbalance is due to the different resources
available to each system.
4.3 Scenario 2 - Execution group failover
In the second scenario the execution group for WMQ2BRK was made to fail by
issuing a cancel command (C SAMPLE2) to the MVS console, as illustrated in
Figure 4-2 on page 39. Message Broker execution groups are automatically
recovered by the Message Broker, so no action is required by ARM. For this and
all subsequent tests, Coordinated Transaction was selected in the deployment
descriptor of the .bar file.
38 High Availability z/OS Solutions for WebSphere Business Integration Message Broker V5