Use the CRTMQMQ panel to define the queue with queue type *RMT, using one of the following online methods:
The use of remote queues is described in detail in WebSphere MQ Intercommunication.
This section describes how to define a remote queue for each of the three uses. We use the CRTMQMQ command in the examples; you can, of course, do the same thing from the WRKMQMQ panel.
This is the most straightforward use of remote queues. It is used to direct messages to a local queue on a remote queue manager, through a transmission queue.
To create a remote queue for this use:
If you do not specify a transmission queue name, the transmission queue with the same name as the remote queue manager is used.
Queue manager alias definitions can be used to remap the queue manager name specified in the MQOPEN call. This enables you to alter the target queue manager without changing your applications.
See WebSphere MQ Intercommunication for further information.
To define a remote queue as a queue manager object:
If you do not specify a transmission queue name, the transmission queue with the same name as the remote queue manager is used.
An application can name a reply-to queue when it puts a message on a queue. The reply-to queue name is used by the application that gets the message from the queue to send reply messages. To define an alias to a reply-to queue, define a remote queue with the same name as the reply-to queue.
See WebSphere MQ Intercommunication for further information.
To create a remote queue as an alias to a reply-to queue:
This must be the same as the reply-to queue named by the putting application.
This is the name of the queue to which you want the reply-to messages sent.
This is the name of the queue manager to which you want the reply-to messages sent.
If you do not specify a transmission queue name, the transmission queue with the same name as the remote queue manager is used.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
reqcrt |