Redpaper - IBM Redbooks

More documents

Recommendations

Info

IP13 Statistics MVSM0 MVSM2 Total Broker Statistics WMQ0BRK WMQ2BRK Total Number Input Messages 25460 11019 36479 Total Elapsed Time (seconds) 224.761 119.003 Total CPU Time (seconds) 84.247 36.560 Conclusions From the results, we concluded that the statistics message is lost prior to the queue manager restart since statistics gathering is a WebSphere MQ Pub/Sub function. The statistics shown for WMQ2BRK are after the WMQ2 queue manager restart. WMQ2BRK processed about 30% of the total messages. This is due to the length of time it takes the queue manager to restart and the broker to reconnect. 4.6 Scenario 5 - DB2 failover There is a known issue with the Message Broker in that if DB2 should fail while it is active, it does not dynamically reconnect as is the case with a queue manager failure, as illustrated in Figure 4-5 on page 45. So, while ARM restarts DB2, the Message Broker requires a manual restart to resume work. The DB2 connection is not actively managed by the Message Broker and, in fact, it would not realize the DB2 had failed until there was a need to access a database. This issue is being addressed in APAR PQ92596. As such, there were no statistics produced for this test. 44 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 Figure 4-5 DB2 failover 4.7 Scenario 6 - z/OS system failover IP13 Coupling Facility Configuration Manager z/OS (MVSM2) Message Broker (WMQ2BRK) Execution Groups Message Flows The final scenario tests the failure of MVSM2. The failure was simulated by removing MVSM2 from the sysplex with a system reset from the hardware console, as illustrated in Figure 4-6 on page 46. ARM restarts the DFM2 DB2 subsystem in light mode on MVSM0 to release any locks retained. It then restarts queue manager, WMQ2, and broker, WMQ2BRK, on the surviving system, MVSM0. IP13 DB2 (DFM2) (DSG- DSN710PM) QMGR (WMQ2) (QSG - MB01) Chapter 4. Failover scenarios 45
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 52 and 53: IP13 Statistics MVSM0 MVSM2 Total B
Page 54 and 55: 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
show all

Redpaper - IBM Redbooks

Create successful ePaper yourself

Delete template?

Save as template?