Example IBM MQ configuration for all platforms
The configuration examples describe tasks performed to establish a working IBM MQ network. The tasks are to establish IBM MQ sender and receiver channels to enable bidirectional message flow between the platforms over all supported protocols.
To use channel types other than sender-receiver, see the DEFINE CHANNEL command.
Figure 1 is a conceptual representation of a single channel and the IBM MQ objects associated with it.
This example is a simple one, intended to introduce only the basic elements of the IBM MQ network. It does not demonstrate the use of triggering which is described in Triggering channels.
The objects in this network are:- A remote queue
- A transmission queue
- A local queue
- A sender channel
- A receiver channel
Appl1 and Appl2 are both application programs; Appl1 is putting messages and Appl2 is receiving them.
Appl1 puts messages to a remote queue. The definition for this remote queue specifies the name of a target queue manager, a local queue on that queue manager, and a transmission queue on this local queue manager.
When the queue manager receives the request from Appl1 to put a message to the remote queue, the queue manager determines from the queue definition that the destination is remote. It therefore puts the message, along with a transmission header, straight onto the transmission queue specified in the definition. The message remains on the transmission queue until the channel becomes available, which might happen immediately.
A sender channel has in its definition a reference to one, and one only, transmission queue. When a channel is started, and at other times during its normal operation, it looks at this transmission queue and send any messages on it to the target system. The message has in its transmission header details of the destination queue and queue manager.
The intercommunication examples describe in detail the creation of each of the preceding objects described, for various platform combinations.
On the target queue manager, definitions are required for the local queue and the receiver side of the channel. These objects operate independently of each other and so can be created in any sequence.
On the local queue manager, definitions are required for the remote queue, the transmission queue, and the sender side of the channel. Since both the remote queue definition and the channel definition refer to the transmission queue name, it is advisable to create the transmission queue first.
Network infrastructure in the example
The configuration examples assume that particular network infrastructures are in place for particular platforms:- z/OS communicates by using a 3745 network controller (or equivalent) that is attached to a token ring
- All other platforms are connected to a token-ring network
It is also assumed that, for SNA, all the required definitions in VTAM and network control program (NCP) are in place and activated for the LAN-attached platforms to communicate over the wide area network (WAN).
Similarly, for TCP, it is assumed that name server function is available, either by using a domain name server or by using locally held tables (for example a host file).
Communications software in the example
Working configurations are given in the examples for the following network software products:- SNA
- IBM Personal Communications for Windows V5.9
- IBM Communications Server for AIX, V6.3
- Hewlett-Packard SNAplus2
- IBM i
- Data Connection SNAP-IX Version 7 or later
- OS/390 Version 2 Release 4
- TCP
- Microsoft Windows
- AIX Version 4 Release 1.4
- IBM i
- TCP for z/OS
- NetBIOS
- SPX
- How to use the communication examples
The example-configurations describe the tasks that are carried out on a single platform to set up communication to another of the platforms. Then they describe the tasks to establish a working channel to that platform. - Example IBM MQ configuration for AIX
This section gives an example of how to set up communication links from IBM MQ for AIX to IBM MQ products. - Example IBM MQ configuration for IBM i
This section gives an example of how to set up communication links from IBM MQ for IBM i to IBM MQ products on other platforms. - Example IBM MQ configuration for Linux
This section gives an example of how to set up communication links from IBM MQ for Linux to IBM MQ products. - Example IBM MQ configuration for Windows
This section gives an example of how to set up communication links from IBM MQ for Windows to IBM MQ products on other platforms. - Example IBM MQ configuration for z/OS
This section gives an example of how to set up communication links from IBM MQ for z/OS to IBM MQ products on other platforms. - Example IBM MQ configuration for z/OS using QSGs
This section gives an example of how to set up communication links to a queue sharing group (QSG) from IBM MQ on Windows and AIX. We can also connect from z/OS to z/OS. - Example MQ configuration for z/OS using intra-group queuing
This section describes how a typical payroll query application, that currently uses distributed queuing to transfer small messages between queue managers, could be migrated to use queue sharing groups and shared queues.
Parent topic: Configuration reference
Related information