MQSeries.net :: View topic - How to put a message to queue using BIND_ON_OPEN in WMB?

GregG · Posted: Wed Jul 06, 2011 7:12 am Post subject:

In the WBM Toolkit documentation, for the MQOutput node, it states the following:

For message flow output queues:

* WebSphere Message Broker always specifies MQOO_BIND_AS_Q_DEF when it opens a queue for output. If you expect segmented messages to be put to an output queue, or want a series of messages to be handled by the same process, you must specify DEFBIND(OPEN) when you define that queue. This option ensures that all segments of a single message, or all messages within a sequence, are put to the same target queue and are processed by the same instance of the receiving application.
* If you create your own output nodes, specify MQOO_BIND_AS_Q_DEF when you open the output queue, and DEFBIND(OPEN) when you define the queue, if you need to ensure message order, or to ensure a single target for segmented messages.

In the MQ Information Center, there is some other documentation that states:

MQOPEN

An option on the MQOPEN call, the MQOO_BIND_ON_OPEN option, allows you to specify that, when there are multiple instances of the same queue within a cluster, the target queue manager needs to be fixed. That is, all messages put to the queue specifying the object handle returned from the MQOPEN call must be directed to the same queue manager using the same route.

Can someone tell me why there is no option in the WMB to have the broker open the queue with BIND_ON_OPEN? I have searched for different posts and I do not see any simple way of doing this within the message flow in WMB. It seems it would be nice to have this as an option on the MQOutput node.

We use a message gateway to send segmented messages to external queues and the message arrive out of sequence and I do not have the ability to change the bind attribute on the queue. I am not 100 percent convinced that it would ensure the messages will be delivered in sequence if we did some custom node to do this, since I do not know the complete path thru our gateway.

Looking for some feedback to this issue from anyone that may have had some similar issue.

Thanks.