Redpaper - IBM Redbooks

More documents

Recommendations

Info

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
z/OS (MVSM0) DB2 (DFM0) (DSG - DSN710PM) QMGR (WMQ0) (QSG - MB01) Message Broker (WMQ0BRK) Execution Groups Message Flows IP13 Figure 4-2 Execution Group failover Coupling Facility Configuration Manager z/OS (MVSM2) The batch jobs provided work for the brokers for four minutes. Table 4-2 records the results from the SupportPac IP13 measurements and the Message Broker statistics. Table 4-2 SupportPac IP13 and Message Broker statistics IP13 Statistics MVSM0 MVSM2 Total Total Transactions 15212 14584 29796 IP13 Elapsed Time (seconds) 239.294 239.258 Application CPU Time (seconds) 17.172 18.454 Transaction Rate (trans/sec) 63.570 60.955 Round trip per msg (ms) 15.730 16.405 Average App CPU per msg (ms) 1.128 1.265 DB2 (DFM2) (DSG - DSN710PM)) QMGR (WQM2) (QSG - MB01) Message Broker (WMQ2BRK) Execution Groups Message Flows Chapter 4. Failover scenarios 39
Page 1: High Availability z/OS Solutions fo
Page 4 and 5: Note: Before using this information
Page 6 and 7: 3.7 Automatic Restart Management co
Page 8 and 9: Trademarks The following terms are
Page 10 and 11: From left: Dean, Steve, and Jon Dea
Page 12 and 13: Become a published author Join us f
Page 14 and 15: 1.1 Project overview This paper exp
Page 16 and 17: e compromised while the failing com
Page 18 and 19: Figure 1-2 Test environment topolog
Page 20 and 21: Message Broker is a WebSphere MQ an
Page 22 and 23: 2.1 Considerations when designing f
Page 24 and 25: Table 2-1 Advantages and disadvanta
Page 26 and 27: Advantages Disadvantages Uses the a
Page 28 and 29: In this instance, you should consid
Page 30 and 31: of messages making up a transaction
Page 32 and 33: 20 High Availability z/OS Solutions
Page 34 and 35: 3.1 High Availability configuration
Page 36 and 37: 3.3 The z/OS LPARs There are three
Page 38 and 39: ► Review actual structure sizes r
Page 40 and 41: pool is not available, errors occur
Page 42 and 43: 3.7 Automatic Restart Management co
Page 46 and 47: 4.1 Test environment setup As previ
Page 48 and 49: ► In a production environment, yo
Page 52 and 53: IP13 Statistics MVSM0 MVSM2 Total B
Page 58 and 59: z/OS DB2 (DSG) QMGR (QSG) Message B
Page 62 and 63: ARM policy Example A-1 displays the
Page 66 and 67: Using the Web material The addition
Page 70 and 71: How to get IBM Redbooks You can sea
Page 72: U UNIX System Services (USS) enviro

Redpaper - IBM Redbooks

Create successful ePaper yourself

Delete template?

Save as template?