You can send messages to remote queue objects by using the msgsend remote_qmgr option to specify the names of your remote queue managers when:
The local queue manager and the remote queue manager are in a single cluster, and the local queue manager stores the cluster queue manager definition of the remote queue manager.
There is a transmit queue on the local queue manager, and the name of the transmit queue is the same as the one on the remote queue manager.�
There is a queue manager alias on the local queue manager, and the name of the queue manager alias is the same as the one on the remote queue manager.�
Adaptive Server sets the remote queue manager as the
target queue manager, and sets the queue as the target queue. As
soon as Adaptive Server sends a message to the related transmit
queue, Adaptive Server returns with successful status, even though
it has not yet sent a message to the target queue.�
For more information on how WebSphere MQ transfers messages between queue managers, see your IBM documentation.
After a message is placed in the transmit queue, the local queue manager looks for the remote queue manager definition in its own subnet. If the local queue manager is:
The full repository of the cluster – the local queue manager should contain a definition for the remote cluster queue manager.
A partial repository – the local queue manager might not know where the remote definition is, in which case WebSphere MQ returns an error. When this happens, however, the local queue manager does not then ask for the location of the remote queue manager.
If the local queue manager finds the remote queue manager definition, the local queue manager sends a message to the remote queue manager thorough the cluster transmit queue, after which the remote queue manager sents a message to the target queue. This way, the operation succeeds even though the target queue is not a cluster queue.
For other circumstances, the channel of the related transmit queue receives messages and sends them to the queue manager that the channel connects to. If no such channel exists or the channel has not been started, the transmit queue stores the messages until the channel is started.�
