Off top of my head I believe the MQOO_INPUT_EXCLUSIVE option needs to be set in the Open options. This stops any other apps getting while you have it open.
As for an exclusive put, Idon't think that is an option. Why do you need this? Could you control this through your application?
Goto Documentation->AP Guide or AP Reference up above on this sites menu bar to double check - I would however I'm on a sloooooooooow dial up!
When I set the mode as MQOO_INPUT_EXCLUSIVE then can't open the queue handle in the input from other application. But I can open it for the OUTPUT mode. This does not suffices my purpose. I would like to lock the queue.
Posted: Tue Apr 01, 2003 12:14 pm Post subject: HELLO???
Centurion
Joined: 28 Jan 2003 Posts: 109 Location: Colorado
There is only a certain level of granularity that MQ allows for I/O actions... Locking the queue is not a valid option.. Either you open it exclusivly to read from it or you share it with the world to read.. You can't tell MQ that you want to be the only process reading from the queue except for process X. Choose one or the other because you can't have both.
Get or Put disabeling the queue probably isn't going to do what you want either because it does essentially what you are doing by setting EXCLUSIVE read or write.
A broader idea of why you can't control who is accessing your queue would be helpful. It sounds like an application architecture probelm more than an technical problem.
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