I'm designing a application using MQ Client support. I want to be able to put messages from N clients to a single remote queue. (Not a problem) I also want to be able to get the reply message from a single/common local queue on the server QMGR.
Can I do this wihtout having to browse the messages and read the headers in the common queue to see if it is the right reply message?
I'm trying to avoid having a seperate reply queue for every client.
If you get your server-side application to copy the incoming MQ msgid to the outgoing MQ correlid when it replies, then the client application can simply get it's own reply message specifying that correlid on the MQGET (the client application will know the correlid value since it can set the msgid of the request or find out what value MQ generated for the msgid).
All clients can then share the same request and reply queue.
This is a standard design and works fine.
You should code an expiry time for the reply messages in case the client does not retrieve them due to a failure.
I recommend always coding CONVERT on the MQGET so that clients can be on different platforms if needed (eg you can move your application to a mainframe from UNIX). Also specify a WAIT time to avoid an indefinite wait if the server does not respond.
[ This Message was edited by: zpat on 2002-01-09 02:28 ]
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