| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MRRTY = 0 |
« View previous topic :: View next topic » |
| Author |
Message
|
| KeeferG |
 Posted: Wed Aug 10, 2005 2:21 am Post subject: MRRTY = 0 |
 |
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
Hi.
Nice and simple query. I assume that setting MRRTY(O) will send the message straight to the DLQ (if defined) as soon as it fails to put the message to the target queue. I just want to confirm that any exit in the MREXIT field is NOT called when MRRTY = 0;
Thanks
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Wed Aug 10, 2005 2:46 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
how about a rtfm?
from the intercommunication guide:
| Quote: |
Message retry count (MRRTY)
This is the number of times the channel will retry before it decides it cannot deliver the message.
This attribute controls the action of the MCA only if the message-retry exit name is blank. If the exit name is not blank, the value of MRRTY is passed to the exit for the exit’s use, but the number of retries performed (if any) is controlled by the exit, and not by this attribute.
The value must be in the range 0 to 999 999 999. A value of zero means that no retries will be performed.
This parameter is only valid for receiver, cluster-receiver, and requester channels. It is not supported on WebSphere MQ for z/OS. |
so... the exit is called when specified, no matter what mrrty you specified. you have to wipe out the exit name.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| KeeferG |
| Posted: Wed Aug 10, 2005 2:50 am Post subject: |
|
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
Cheers,
I was looking in the the MQSC manual for usage and didn't check anywhere else 
So this must mean that it passes the value 0 to the message retry exit and that the MRRTY updates after the retry attempt
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Aug 10, 2005 9:24 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Hi Keith, the exit receive the MQCXP structure which includes the "retry count"for this message. Presumable, the exit would compare that against the channel setting in the passed MQCD.
For experimenting with channel exit behavior, I strongly recommend having a look at Morag's supportpac MD0B. Its a wonderful tool for learing about all channel exits.
_________________
-wayne |
|
| Back to top |
|
|
| KeeferG |
| Posted: Thu Aug 11, 2005 1:49 am Post subject: |
|
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
Hi Wayne,
Hows things. Been a while.
Morags stuff was fairly useful. I had a play with it before writing the exit and perhaps should have another go to see what happens.
My exit doesn't actually check the retry count as it put-disables the queue first time it is called and returns MQXCC_SUPPRESS_FUNCTION.
The reason for my original question is that I have a PMR open as my exit does not work in a CLUSRCVR channel so as a temporary measure I am reducing the MRRTY count to 1. The count of 0 means that no retry attempt is made however the text from the intercomms guide suggest that the MRRTY is ignored if using an exit.
I'll have an experiment when i get a free moment and post the results.
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| 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
|
|
|
|
