Redpaper - IBM Redbooks

More documents

Recommendations

Info

3.3 The z/OS LPARs There are three LPARs in the sysplex running on a 9672 model XZ7 with an internal coupling facility. For simplicity, only two of the LPARs are used for the active-active configuration, as depicted in Figure 3-1 on page 23. One of the LPARs, MVSM0, is connected to two logical processors while the second, MVSM2, to just one. MVSM0 has 1536 MB of real storage configured, while MVSM2 has 1024 MB. Otherwise, the MVS images have similar configurations with RRS, DB2, WebSphere MQ, WebSphere Business Integration Message Broker, and TCP/IP all active. UNIX® System Services is running with shared Hierarchical File System (HFS). Both images are running z/OS 1.4. 3.4 The DB2 data sharing group configuration The DB2 subsystems are data sharing and accessible as an Open Database Connectivity (ODBC) data source via a Distributed Data Facility (DDF) that is using TCP/IP. The DB2 subsystems in data sharing group DSN710PM are DFM0 and DFM2, running on MVSM0 and MVSM2 respectively. Figure 3-2 displays the data sharing group. Figure 3-2 The DB2 data sharing group 24 High Availability z/OS Solutions for WebSphere Business Integration Message Broker V5
3.5 The WebSphere MQ queue sharing group configuration A queue manager is set up on each system and defined to a QSG. To create the QSG, we defined some new structures to the coupling facility. The procedure for this is described in the WebSphere MQ z/OS System Setup Guide, which can be found at: http://www-306.ibm.com/software/integration/mqfamily/library/manualsa/manuals/ platspecific.html#zos The queue managers in queue sharing group MB01 are WMQ0 and WMQ2, running on MVSM0 and MVSM2 respectively. Figure 3-3 shows the QSG. Figure 3-3 The queue sharing group 3.5.1 Queue sharing group configuration considerations Some things you should consider when configuring the QSG are: ► If you are using the z/OS Automatic Restart Management (ARM) to restart queue managers on different z/OS images, then: – Define every queue manager with a sysplex-wide, unique four character subsystem name that uses a command prefix string (CPF) scope of S. – Configure each queue manager with a different channel listener port. In the event of a system failure, this configuration is important if there is a requirement to restart the failing queue manager on another system in the sysplex that is already running a queue manager. ► Use the INITSIZE value of 10 MB as provided in the sample job CSQ4CFRM when you define the admin structure. Specify a larger amount than this for the SIZE value so that it can expand. You should also consider adding the ALLOWAUTOALT(YES) parameter to allow system-initiated alters (automatic-alter) for this structure. Chapter 3. Topology and system setup 25
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 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 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?