Advanced tasks

This chapter shows some advanced tasks that extend the cluster created in Task 1: Setting up a new cluster and Task 2a: Adding a new queue manager to a cluster.

These tasks are:

The chapter then goes on to demonstrate the following five tasks:

You can perform these tasks, and the two described in First tasks, without stopping your existing cluster queue managers or disrupting your existing network in any way.

Much of the information you need to achieve these tasks is documented elsewhere in the WebSphere MQ(R) library. This chapter gives pointers to that information and fills in details relating specifically to work with clusters.

Notes:
  1. Throughout the examples in this chapter and First tasks, the queue managers have illustrative names such as LONDON and NEWYORK. Don't forget that on WebSphere MQ for z/OS, queue-manager names are limited to 4 characters.
  2. The names of the queue managers imply that each queue manager is on a separate machine. You could just as easily set up these examples with all the queue managers on the same machine.
  3. The examples in these chapters show WebSphere MQ Script Commands (MQSC) as they would be entered by the system administrator at the command console. For information about other ways of entering commands, refer to Using WebSphere MQ commands with clusters.