Redpaper - IBM Redbooks

More documents

Recommendations

Info

IP13 Statistics MVSM0 MVSM2 Total Broker Statistics WMQ0BRK WMQ2BRK Total Number Input Messages 17051 12010 29061 Total Elapsed Time (seconds) 181.542 124.319 Total CPU Time (seconds) 61.153 42.033 Conclusions From the results, we concluded the following: ► At first glance, it would seem as though messages were lost under this test, but this is not the case for this or any other test scenario. When the execution group is cancelled, the statistics message is dumped by the broker. Upon successful execution group startup, a new statistics message is created, the interval time is reset, and accounting starts fresh. Since the execution group was cancelled very close to the beginning of the test and it recovered quickly, there are 735 messages that WMQ2BRK processed that are not accounted for in the above table. ► The high number of messages consumed by WMQ2BRK underscores the speed of the execution group recovery. ► The higher number of messages consumed by WMQ0BRK compared to transactions completed on MVSM0 illustrates how broker 0 processes messages from the SupportPac IP13 batch jobs on both systems, taking the extra load while the execution group is down on MVSM2. 4.4 Scenario 3 - Message Broker failover The third scenario tests the failure of WMQ2BRK Message Broker. The failure was simulated by issuing a MVS cancel command (C WMQ2BRK,ARMRESTART), as illustrated in Figure 4-3 on page 41. The ARM policy in effect ensures the broker restarts immediately. You can find the policy details in Appendix A, “Sample code” on page 49. 40 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-3 Message Broker failover Coupling Facility Configuration Manager z/OS (MVSM2) The batch jobs provided work for the brokers for four minutes. Table 4-3 records the results from the SupportPac IP13 measurements and the Message Broker statistics. Table 4-3 SupportPac IP13 and Message Broker statistics IP13 Statistics MVSM0 MVSM2 Total Total Transactions 20564 9608 30172 IP13 Elapsed Time (seconds) 239.539 239.721 Application CPU Time (seconds) 21.363 9.934 Transaction Rate (trans/sec) 85.847 41.912 Round trip per msg (ms) 46572 88645 Average App CPU per msg (ms) 1045 1034 DB2 (DFM2) (DSG- DSN710PM) QMGR (WMQ2) (QSG - MB01) Message Broker (WMQ2BRK) Execution Groups Message Flows Chapter 4. Failover scenarios 41
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 50 and 51: The batch jobs provided work for th
Page 54 and 55: IP13 Statistics MVSM0 MVSM2 Total B
Page 56 and 57: 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?