| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| FAIL_IF_QUIESCING - N/A for MQClients |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Thu Jan 20, 2005 1:09 pm Post subject: FAIL_IF_QUIESCING - N/A for MQClients |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
After years of always preaching that apps should code the FAIL_IF_QUIESCING option on puts gets and opens, I found it doesn't apply to MQClients! Whether I coded it or not, my MQClient apps would end their outstanding MQGET with waits immediatly. I brought this to IBM's attention, and they responded as below. They accepted my form to have the manuals be more explicit in this area - That FAIL_IF_QUIESCING is N/A for MQClients. No question really. Just some info.....
If I *DON'T* code MQC.MQGMO_FAIL_IF_QUIESCING, the MQGET *immediatly* returns the following:
2202-amqmdain end
2202-Right Click..Stop QM Controlled
2009-Right Click..Stop QM Immediate
Below is a quote from Karthik of IBM from PMR 20236 L6Q:
If the it is not a client application, then we wait till the agent has
finished with it's job ( in this case, we wait till the MQGET call
completes ) and then end the Qmgr. But if the MQGET is from an client,
the end command, first stops all the active channels on this queue
manager. During this stop, we call an internal function
lpiSPICancelWaiter, which cancels all pending wait requests on a queue
and returns 'MQRC_CONNECTION_QUIESCING' to the application.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
