Your program has to connect to the first queue manager. All the connection details for that need to be provided (if using a client type connection).
Your program opens the queue (which happens to be a remote queue definition). Strictly speaking only the queue name is needed for this - but if it requires a QM name you can use the one that you are connected to.
Your program puts to the queue.
MQ automagically sends it to the remote queue manager named in the remote queue definition, using the xmit queue named.
The xmit queue sends it to the intermediate queue manager, which will then forward it onto the final queue manager.
It is a basic MQ principle that you don't need to know (in the application) where the message is going to, it could be a local queue or a remote queue (and it might change later).
However MQ will not allow the application to open a remote queue for input or browse because this operation is illogical.
When your application opens a remote queue definition (for output) - what it is really doing is opening the transmit queue named (or defaulted).
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum