[MQ 9.2.3 Jul 2021][UNIX, Linux, Windows, IBM i]

Streaming to remote and alias queues

It is possible to stream messages to remote queues and alias queues. For example, Q1 might be configured with STREAMQ(MY.REMOTE.Q) where MY.REMOTE.Q is a remote queue definition.

Streaming to remote queues

By streaming messages from a local queue to a remote queue, the duplicate messages can be sent to a queue on another queue manager in your IBM® MQ network as shown in the following illustration:
Illustration showing how the duplicate messages can be sent to a queue on another queue manager in your IBM MQ network.

Streaming to alias queues

By streaming messages to an alias queue, it is possible to send the duplicate messages to the target of the alias queue. Since the target of an alias queue can also be a topic, it is therefore possible to send the duplicate messages to a publish/subscribe topic. Any subscribers to the alias topic will receive a copy of the duplicate message. In this way, you can create multiple copies of the original message. However, the existing rules for publish/subscribe message are applied to the duplicated message. This means that the messages that are sent to subscribers will not be identical to the original message, including:
  • Having a new message ID.
  • Having a generated correlation ID, depending on the configuration of the subscription.
  • The UserIdentifier field being set to the user the queue manager is running as, not the user who put the message.
  • The PutApplName showing the name of the queue manager, not the name of the putting application.
Notes:
  1. It is not possible to configure the STREAMQ attribute on remote queues or alias queues themselves. You can only stream messages to them, not from them.
  2. If messages are being streamed to a queue alias, the target of the queue alias cannot have its STREAMQ attribute set.