Lab HYI9511

Lab HYI9511 

IBM MQ V8: Implementing Overlapping 

Clusters 

z

February 2016 edition 

NOTICES 

This information was developed for products and services offered in the USA. 

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM 

representative for information on the products and services currently available in your area. Any reference to an IBM product, program, 

or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent 

product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's 

responsibility to evaluate and verify the operation of any non-IBM product, program, or service. 

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this 

document does not grant you any license to these patents. You can send license inquiries, in writing, to: 

IBM Director of Licensing 

IBM Corporation 

North Castle Drive, MD-NC119 

Armonk, NY 10504-1785 

United States of America 

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local 

law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF 

ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 

NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of 

express or implied warranties in certain transactions, therefore, this statement may not apply to you. 

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; 

these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) 

and/or the program(s) described in this publication at any time without notice. 

Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an 

endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those 

websites is at your own risk. 

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. 

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other 

publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other 

claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those 

products. 

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, 

the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to 

the names and addresses used by an actual business enterprise is entirely coincidental. 

TRADEMARKS 

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many 

jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM 

trademarks is available on the web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml. 

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems 

Incorporated in the United States, and/or other countries. 

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used 

under license therefrom. 

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and 

Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. 

IT Infrastructure Library is a Registered Trade Mark of AXELOS Limited. 

ITIL is a Registered Trade Mark of AXELOS Limited. 

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. 

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and 

other countries. 

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. 

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, 

or both. 

UNIX is a registered trademark of The Open Group in the United States and other countries. 

© Copyright International Business Machines Corporation 2016. 

This document may not be reproduced in whole or in part without the prior written permission of IBM. 

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents 

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 

Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 

Creating the cluster queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 

Enabling the automatic creation of transmission queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 

Creating an overlapping cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 

Putting messages across the clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 

© Copyright IBM Corp. 2016 iii 

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Contents 

iv 

Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 

© Copyright IBM Corp. 2016

Introduction 

In this lab, you construct an IBM MQ cluster that uses multiple transmission queues to separate the 

workload. You then add more complexity by creating overlapping clusters that share full repository 

queue managers. 

In Part 1 of this exercise, you start the queue managers and cluster, create the cluster queues, and 

configure an existing cluster to use multiple transmission queues. 

In Part 2 of this exercise, you update the cluster to use multiple transmission queues. You also use 

the dspmqrte command to verify that the messages are routed through the dynamically created 

transmission queue. 

In Part 3 of this exercise, you create overlapping clusters that share a full repository queue 

manager. 

In Part 4 of this exercise, you configure the cluster so that you can put messages across the 

clusters. 

After completing this exercise, you should be able to: 

• Use multiple transmission queues to separate the workload 

• Use the IBM MQ display route command (dspmqrte) to verify the transmission queues 

• Create overlapping clusters 

This lab is taken from the three-day IBM course WM252, Designing, Implementing, and Managing 

IBM MQ V8 Clusters. 

The estimated time for this lab is 1.5 hours. 

Log in to the VMware image for this lab by using the following credentials: 

User name: Administrator 

Password: web1sphere 

Attention: This lab assumes that you have basic experience with IBM MQ system administration 

on distributed operating systems and IBM MQ Explorer. 

© Copyright IBM Corp. 2016 1 


Exercise 

Exercise 

In this exercise, you use a cluster that is named CLUS1. The cluster, queue managers, and 

channels are already configured for you in the VMWare image for this lab exercise. 

The cluster components for this exercise are shown in the figure below. 

Cluster = CLUS1 

QMC3 (9013) 

SALES 

CLUS1.QMC1 

QMC1 (9011) 

Full repository 

QMC4 (9014) 

CLUS1.QMC2 

MARKETING 

CLUS1.QMC2 

QMC5 (9015) 

QMC2 (9016) 

CLUS1.QMC1 

MARKETING 

CLUS1.QMC2 

Full repository 

Manually defined cluster-sender channels 

The cluster contains the following queue managers: 

• QMC1 is a full repository queue manager that is listening on port 9011 

• QMC2 is a full repository queue manager that is listening on port 9012 

• QMC3 is a partial repository queue manager that is listening on port 9013 and uses QMC1 for 

its full repository 


its full repository 


its full repository. 

2 

© Copyright IBM Corp. 2016 


V7.0 

Exercise 

Uempty 

In this lab, you use the IBM MQ Put sample program, amqsput, to represent two applications, which 

are identified in this exercise as SALES and MARKETING. A different clustered queue is used for 

each application. 

• The application SALES puts to a queue that is named SALES. 

• The application MARKETING puts to a queue that is named MARKETING 



Exercise 

Task 1 

Creating the cluster queues 

In this part of the exercise, you start the queue managers and cluster, create the cluster queues, 

and configure an existing cluster to use multiple transmission queues. 

1. Start IBM MQ Explorer by double-clicking the WebSphere MQ Explorer shortcut icon. 

2. Stop the queue managers in the PubSubClusterLab queue manager set by right-clicking 

PubSubClusterLab queue manager set in the MQ Explorer - Navigator view, and then 

clicking Stop Local Queue Managers. 

3. The queue managers for this lab are defined in the queue manager set that is named 

OverlappingClustersLab. 

Start the queue managers in the OverlappingClustersLab queue manager set by right-clicking 

OverlappingClustersLab in the MQ Explorer - Navigator view, and then clicking Start Local 

Queue Managers. Click OK to start the queue managers as created. 

4. Verify that the queue managers, listeners, and channels are running on QMC1, QMC2, QMC3, 

and QMC4. 

Attention: It might take a minute or two for the IBM MQ Explorer to update and show that the 

queue managers and cluster are active. 

4 



V7.0 

Exercise 

Uempty 

5. This exercise requires a cluster-queue that is named SALES on QMC3 and MARKETING on 

QMC4 and QMC5. 

a. Add the SALES cluster queue to QMC3. 

Using runmqsc for QMC3, type: 

DEFINE QL(SALES) CLUSTER(CLUS1) DEFBIND(NOTFIXED) 

b. Add the MARKETING cluster queue to QMC4. 


DEFINE QL(MARKETING) CLUSTER(CLUS1) DEFBIND(NOTFIXED) 

c. Add the MARKETING cluster queue to QMC5. 


DEFINE QL(MARKETING) CLUSTER(CLUS1) DEFBIND(NOTFIXED) 

Attention: Ensure that the listeners and channels are running before you continue. If a queue 

manager cannot communicate with other queue managers in the cluster, you might encounter 

errors in subsequent steps, such as the reason code 2085: MQRC_UNKNOWN_OBJECT_NAME. 

6. In a command window, use the Put sample amqsput to test the cluster. 

Send messages to the SALES and MARKETING cluster queues from the queue managers that 

are called QMC1 and QMC2. 

To send a message by using the amsput command, enter some text, such as “Hello World”, and 

press Enter. To end the application when you finished sending requests, press Enter without 

entering any text beforehand. 

a. Send messages to the SALES queue from QMC1. Run the following command: 

amqsput SALES QMC1 

b. Send messages to the MARKETING queue from QMC1. Run the following command: 

amqsput MARKETING QMC1 

c. Send messages to the SALES queue from QMC2. Run the following command: 


d. Send messages to the MARKETING queue from QMC2. Run the following command: 


7. Use IBM MQ Explorer to confirm that messages were delivered correctly. 

8. After you examine the messages, use IBM MQ Explorer to clear the SALES and MARKETING 

queues. Clearing the queues makes it easier to determine the outcome of subsequent steps 

that rerun the amqsput sample program. 



Exercise 

Task 2 

Enabling the automatic creation of transmission 

queues 

Now that you have created and verified the initial cluster configuration, you can update the cluster 

to use multiple transmission queues. Messages are sent only from queue manager QMC1 and 

QM2, so these managers are the only queue managers that must be updated. 

1. Modify QMC1 and QMC2 to automatically define a permanent-dynamic queue for the cluster 

sender channel. This queue has the name SYSTEM.CLUSTER.TRANSMIT.ChannelName 

a. Using runmqsc for QMC1, type the following command: 

ALTER QMGR DEFCLXQ(CHANNEL) 

b. Using runmqsc for QMC2, type the following command: 

ALTER QMGR DEFCLXQ(CHANNEL) 

2. You must restart each cluster-sender channel that sends application messages on QMC1 and 

QMC2 for the configuration change to become effective. 

a. Using runmqsc for QMC1, type the following commands: 

STOP CHANNEL(CLUS1.QMC3) 



START CHANNEL(CLUS1.QMC3) 



b. Run the same commands for QMC2 to stop and start the cluster-sender channels. 

Attention: In Part 1 of this exercise, the cluster configuration was verified by sending messages. 

If you did not put several messages (at least 10), a channel might not be created between every 

pair of queue managers. When you try to stop the channels, one or more of the commands might 

fail because the channel does not exist. Ignore this error; when a channel is created, it recognizes 

the value of the DEFCLXQ attribute. 

3. Confirm the use of multiple cluster transmission queues by displaying the status of the 

cluster-sender channels. 

a. Using runmqsc for QMC1, type 

DISPLAY CHSTATUS(*) WHERE(CHLTYPE EQ CLUSSDR) 

6 



V7.0 

Exercise 

Uempty 

This command should return results that are similar to the following example. 

1 : DISPLAY CHSTATUS(*) WHERE(CHLTYPE EQ CLUSSDR) 

AMQ8417: Display Channel Status details. 

CHANNEL(CLUS1.QMC2) CHLTYPE(CLUSSDR) 

CONNAME(127.0.0.1(9012)) CURRENT 

RQMNAME(QMC2) 

STATUS(RUNNING) 

SUBSTATE(MQGET) 

XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE) 




RQMNAME(QMC3) 



XMITQ(SYSTEM.CLUSTER.TRANSMIT.CLUS1.QMC3) 




RQMNAME(QMC4) 







RQMNAME(QMC5) 




When the status information for active channels is displayed, the XMITQ attribute identifies 

the transmission queue that is each channel uses. 

The example shows that the channels CLUS1.QMC3, CLUS1.QMC4, and CLUS1.QMC5 

are using a dynamically created transmission queue. In the example, CLUS1.QMC2 is still 

using the SYSTEM.CLUSTER.TRANSMIT.QUEUE transmission queue because it was not 

restarted. 

b. Using runmqsc for QMC2, verify that the cluster-sender channels are using the dynamically 

created transmission queues. Type: 

DISPLAY CHSTATUS(*) WHERE(CHLTYPE EQ CLUSSDR) 

4. To ensure that messages are still delivered correctly within the cluster, put several messages to 

the queues SALES and MARKETING by using the amqsput command. Use IBM MQ Explorer to 

confirm that messages were delivered correctly. 

a. Send messages to the SALES queue from QMC1. Run the following command: 


b. Send messages to the MARKETING queue from QMC1. Run the following command: 




Exercise 

c. Send messages to the SALES queue from QMC2. Run the following command: 


d. Send messages to the MARKETING queue from QMC2. Run the following command: 


5. To verify that messages were routed through the dynamically created transmission queues, run 

the dspmqrte command and examine the results. Type: 

dspmqrte -m QMC1 -q MARKETING -ac -v outline 

The dspmqrte program should return results similar to the following example, which shows that 

the message was put on the SYSTEM.CLUSTER.TRANSMIT.CLUS1.QMC4 queue. 

AMQ8653: DSPMQRTE command started with options '-m QMC1 -q MARKETING -ac -v 

outline'. 

AMQ8659: DSPMQRTE command successfully put a message on queue 

'SYSTEM.CLUSTER.TRANSMIT.CLUS1.QMC4', queue manager 'QMC1'. 

AMQ8674: DSPMQRTE command is now waiting for information to display. 

------------------------------------------------------------------------- 

Activity: 

ApplName: 'Sphere MQ\bin64\dspmqrte.exe' 

Operation: 

OperationType: Put 

QMgrName: 'QMC1 

' 

QName: 'MARKETING 

' 

ResolvedQName: 'SYSTEM.CLUSTER.TRANSMIT.CLUS1.QMC4 

' 

RemoteQName: 'MARKETING 

' 

RemoteQMgrName: 'QMC4 

' 

------------------------------------------------------------------------- 

Activity: 

ApplName: 'Sphere MQ\bin64\amqrmppa.exe' 

Operation: 

OperationType: Get 


QName: 'SYSTEM.CLUSTER.TRANSMIT.CLUS1.QMC4 

ResolvedQName: 'SYSTEM.CLUSTER.TRANSMIT.CLUS1.QMC4 

' 

' 

' 

Operation: 

OperationType: Send 



ChannelName: 'CLUS1.QMC4 

' 

ChannelType: ClusSdr 

XmitQName: 'SYSTEM.CLUSTER.TRANSMIT.CLUS1.QMC4 

' 

' 

' 

8 



V7.0 

Exercise 

Uempty 

------------------------------------------------------------------------- 

Activity: 

ApplName: 'Sphere MQ\bin64\amqrmppa.exe' 

Operation: 

OperationType: Receive 



ChannelName: 'CLUS1.QMC4 

ChannelType: ClusRcvr 

' 

' 

' 

Operation: 

OperationType: Discard 


' 

QName: 'MARKETING 

' 

Feedback: NotDelivered 

------------------------------------------------------------------------- 

AMQ8652: DSPMQRTE command has finished. 

6. Two queue managers in the cluster (QMC4 and QMC5) contain the MARKETING cluster 

queue. 

Run the dspmqrte command again and verify that this time the message is routed to the 

transmission queue for the other queue manager. 

For example, if the first dspmqrte command shows that the message is routed to QMC4 on 

SYSTEM.CLUSTER.TRANSMIT.CLUS.QMC4 then the second dspmqrte command should 

show that the message is routed to QMC5 on SYSTEM.CLUSTER.TRANSMIT.CLUS.QMC5. 

7. After you examine the messages, use IBM MQ Explorer to clear the SALES and MARKETING 

queues on QMC3, QMC4, and QMC5. 

Clearing the queues makes it easier to determine the outcome of subsequent steps that rerun 

the amqsput sample program. 



Exercise 

Task 3 

Creating an overlapping cluster 

In this part of the exercise, you create a new cluster that is named CLUS2. As shown in the figure, 

CLUS2 uses the full repository queue managers from CLUS1 (QMC1 and QMC2) and two new 

partial repository queue managers that are named QMCA and QMCB. 

In this part of the exercise, the amqsput sample program is used to send messages to a queue that 

is called ACCOUNTING, which is on QMCA and QMCB. 

CLUS1 

QMC3 (9013) QMC1 (9011) 

CLUS1.QMC1 

CLUS2 

CLUS2.QMC1 

QMCA (9016) 

SALES 

CLUS1.QMC1 

CLUS1.QMC3 

NAMELIST(CLUSTER) + 

NAMES(CLUS1,CLUS2) 

ALTER QMGR REPOSNL(CLUSTER) 

CLUS2.QMC1 

CLUS2.QMCA 

ACCOUNTING 

QMC4 (9014) 

CLUS1.QMC2 

CLUS2.QMC2 

MARKETING 

CLUS1.QMC2 

CLUS1.QMC4 

QMC5 (9015) 

CLUS1.QMC2 

CLUS1.QMC1 

QMC2 (9012) 

CLUS2.QMC1 

CLUS2.QMC2 

QMCB (9017) 

MARKETING 

CLUS1.QMC2 

CLUS1.QMC4 

NAMELIST(CLUSTER) + 

NAMES(CLUS1,CLUS2) 

ALTER QMGR REPOSNL(CLUSTER) 

CLUS2.QMC2 

CLUS2.QMCB 

ACCOUNTING 

Manually defined channels 

In this part of the exercise, you revise the configuration to add the following objects: 

QMC1 

• Cluster-receiver channel for CLUS2 

• Cluster-sender channel to QMC2 for CLUS2 

• Repository for CLUS1 and CLUS2 

QMC2 



• Repository for CLUS1 and CLUS2 

10 



V7.0 

Exercise 

Uempty 

QMCA 

• Listener on 9016 



• Local queue that is called ACCOUNTING for CLUS2 

QMCB 

• Listener on 9017 



• Local queue that is called ACCOUNTING for CLUS2 

1. Using IBM MQ Explorer, create the queue managers QMCA (on 9016) and QMCB (on 9017). 

2. After you create the queue managers, verify that the listeners are running. 

3. Configure the queue managers to be full repositories for CLUS1 and CLUS2. 

a. Using runmqsc for QMC1, type: 

DEFINE NAMELIST(CLUSTER) NAMES(CLUS1, CLUS2) 

ALTER QMGR REPOS(' ') REPOSNL(CLUSTER) 

b. Using runmqsc for QMC2, type: 

DEFINE NAMELIST(CLUSTER) NAMES(CLUS1, CLUS2) 

ALTER QMGR REPOS(' ') REPOSNL(CLUSTER) 

4. Configure the channels between the queue managers in cluster CLUS2. 

a. Using runmqsc for QMC1, type: 

DEFINE CHANNEL(CLUS2.QMC1) CHLTYPE(CLUSRCVR) + 

TRPTYPE(TCP) CONNAME('localhost(9011)') CLUSTER(CLUS2) 

DEFINE CHANNEL(CLUS2.QMC2) CHLTYPE(CLUSSDR) + 


b. Using runmqsc for QMC2, type: 

DEFINE CHANNEL(CLUS2.QMC2) CHLTYPE(CLUSRCVR) + 




c. Using runmqsc for QMCA, type: 

DEFINE CHANNEL(CLUS2.QMCA) CHLTYPE(CLUSRCVR) + 






Exercise 

d. Using runmqsc for QMCB, type: 

DEFINE CHANNEL(CLUS2.QMCB) CHLTYPE(CLUSRCVR) + 




5. Add the queue ACCOUNTING to the partial repositories (QMCA and QMCB) in CLUS2. 

Using runmqsc for QMCA and QMCB, type the following command: 

DEFINE QL(ACCOUNTING) CLUSTER(CLUS2) DEFBIND(NOTFIXED) 

6. Check that the cluster changes that you created with the previous steps are propagated though 

the cluster. 

a. Using runmqsc for QMC1 (a full repository queue manager), type the following command 

and examine the results. 

DIS CLUSQMGR(*) 

You should see that there are two entries for QMC1 and QMC2: one entry for CLUS1 and 

one entry for CLUS2. You should also see the two new partial repository queue managers 

for CLUS2 (QMCA and QMCB). 

b. Using runmqsc for QMC1, type the following command to verify that the ACCOUNTING 

cluster queue is defined correctly on QMCA and QMCB. 

DIS QCLUSTER(ACCOUNTING) 

c. View the cluster in IBM MQ Explorer. You should now see two clusters (CLUS1 and 

CLUS2). QMC1 and QMC2 should be listed as full repository queue managers for both 

clusters. 

12 



V7.0 

Exercise 

Uempty 

7. Use amqsput sample program on QMC1 and QMC2 to put messages to the ACCOUNTING 

cluster queue on QMCA and QMCB. 

Examples: 

amqsput ACCOUNTING QMC1 

amqsput ACCOUNTING QMC2 

8. Use IBM MQ Explorer to verify that the messages arrived on QMCA and QMCB, which confirms 

that working cluster exists. 

Task 4 

Putting messages across the clusters 

In this part of the exercise configure the cluster so that queues can be referenced in both clusters. 

First you create a cluster queue on QMC1 that is shared by both CLUS1 and CLUS2. 

Next, you create a queue alias so that you can put a message from QMCA on CLUS2 to the SALES 

queue on QMC3 in CLUS1. 

1. Create a cluster queue that is named SHAREQ on QMC1 that is shared in both clusters. 


DEF QL(SHAREQ) CLUSNL(CLUSTER) 

2. Verify that you can put messages to SHAREQ by using the amqsput sample program. 

a. To verify that you can put to SHAREQ from a queue manager that is in CLUS1, type: 

amqsput SHAREQ QMC3 

b. To verify that you can put to SHAREQ from a queue manager that is in CLUS2, type: 

ampsput SHAREQ QMCA 

3. On QMC1 (a bridge queue manager), create a queue alias so that you can put a message from 

QMCA on CLUS2 to the SALES queue on QMC3 in CLUS1. 

On QMC1, create an queue alias that is named MYSALES that targets the SALES queue on 

QMC3 and shares it with CLUS2. Type: 

DEF QA(MYSALES) TARGQ(SALES) CLUSTER(CLUS2) DEFBIND(NOTFIXED) 

Attention: When you open a queue, you need to set DEFBIND to either NOTFIXED or QDEF. If 

DEFBIND is left as the default, OPEN, the queue manager resolves the alias definition to the bridge 

queue manager that hosts it. The bridge does not forward the message. 

4. Verify that you can put a message from QMCA in CLUS2 to QMC3 in CLUS1 by using the alias 

queue MYSALES. Type: 

amqsput MYSALES QMCA 



Exercise 

5. Using IBM MQ Explorer, verify that the message that you typed in Step 4 is on the SALES 

queue on QMC3. 

Exercise clean-up 

Using IBM MQ Explorer, stop the queue manager set OverlappingClustersLab. 

End of exercise 

14 



V7.0 

Exercise 

Uempty 

Exercise review and wrap-up 

In this exercise, you: 

• Configured a cluster to use multiple transmission queues to separate the workload. 

• Use the dspmqrte command to verify the transmission queues. 

• Created and tested an overlapping cluster 



Highlights 

 

 

 

 

 

Align skills with personal and business 

goals 

Technology advances at an accelerated pace, from frequent innovaons 

in Soware and Hardware to the rapid emergence of 

technical soluons. Organizaons and their staff must keep 

pace, staying compeve and driving faster return on investment 

(ROI) through enablement and engagement ed to 

business outcomes. Companies today need a learning strategy 

that’s economical, scalable and flexible, and — above all — effec- 

ve. 

World–class IBM content, worldwide 

delivery 

A recognized skills leader, IBM Training has evolved to ensure 

technology soluons relate to your personal goals and the 

needs of the business. IBM authorized content is current, 

accurate, reliable and consistent, whether off–the– shelf or 

custom designed. When delivered by a handful of specially 

chosen Global Training Providers with a vast network of loca- 

ons and innovave delivery methods, we take learning to 

the next level with an end–to–end training soluon. 

Drive business success with the experts 

IBM–selected, expert skills providers offer a superior value 

versus other training opons. They offer personalized services 

and guidance, from charng a career path and planning 

for cerficaon to choosing courses and the best format for 

an individual or the full enterprise. With more locaons and a 

higher volume of course offerings, building skills and contribu- 

ng to the success of the organizaon is more convenient. 

Connect with your Global Training Provider: 

 

To learn more, visit:

V7.0 

Uempty

z

Lab HYI9511

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

Delete template?

Save as template?