Home
Task 2b: Adding a new queue manager to a cluster — using DHCP
The following example makes use of the following:
- the ability to omit the CONNAME value on a CLUSRCVR definition.
- the ability to use +QMNAME+ on a CLUSSDR definition.
Neither of these are possible on z/OS.
Scenario:
- The INVENTORY cluster has been set up as described in Task 1: Setting up a new cluster. It contains two queue managers, LONDON and NEWYORK, which both hold full repositories.
- A new branch of the chain store is being set up in Paris and you want to add a queue manager called PARIS to the cluster.
- Queue manager PARIS will send inventory updates to the application running on the system in New York by putting messages on the INVENTQ queue.
- Network connectivity exists between all three systems.
- The network protocol is TCP.
- The PARIS queue manager system uses DHCP, which means that the IP addresses may change on system restart.
- The channels between the PARIS and LONDON systems are named according to a defined naming convention, which involves the queue manager name of the full repository queue manager on LONDON.
- Administrators of the PARIS queue manager have no information about the name of the queue manager on the LONDON repository, or the name of the queue manager on the LONDON repository is subject to change.
Parent topic:
First tasks
qc10630_
Home