Introduction to distributed queue management
Distributed queue management (DQM) is used to define and control communication between queue managers.
Distributed queue management:
- Enables you to define and control communication channels between queue managers
- Provides you with a message channel service to move messages from a type of local queue, known as a transmission queue, to communication links on a local system, and from communication links to local queues at a destination queue manager
- Provides you with facilities for monitoring the operation of channels and diagnosing problems, using panels, commands, and programs
Channel definitions associate channel names with transmission queues, communication link identifiers, and channel attributes. Channel definitions are implemented in different ways on different platforms. Message sending and receiving is controlled by programs known as message channel agents (MCAs), which use the channel definitions to start and control communication.
The MCAs in turn are controlled by DQM itself. The structure is platform-dependent, but typically includes listeners and trigger monitors, together with operator commands and panels.
A message channel is a one-way pipe for moving messages from one queue manager to another. Thus a message channel has two end-points, represented by a pair of MCAs. Each end point has a definition of its end of the message channel. For example, one end would define a sender, the other end a receiver.
For details of how to define channels, see:For message channel planning examples, see:
- Monitor and controlling channels on UNIX, Linux, and Windows
- Monitor and controlling channels on z/OS
- Monitor and controlling channels on IBM i
- Message channel planning example for UNIX, Linux , and Windows
- Message channel planning example for IBM i
- Message channel planning example for z/OS®
- Message channel planning example for z/OS using queue sharing groups
For information about channel exits, see Channel-exit programs for messaging channels.