| Author |
Message
|
| nickkirk |
 Posted: Wed Oct 29, 2008 7:42 am Post subject: MQGet Node - Browse Only |
 |
|
Apprentice
Joined: 26 Sep 2008
Posts: 48
|
I am using an MQGet node to browse a queue, using WMB v6.1.
The node seems to only browse a message once ( i.e. next time it browses the queue with the same and only message, it thinks that there is no message and propogates out the 'No Message' terminal).
Does it mark the message as 'read' ?
I expect the MQGet node to propogate out the 'Out' terminal whenever there is a message in the queue, even if this queue is browsed more than once when the same message is in the queue.[/i] |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Oct 29, 2008 8:06 am Post subject: Re: MQGet Node - Browse Only |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| nickkirk wrote: |
Does it mark the message as 'read' ?
|
IIRC it move the browse cursor so it's past the message it's read. You might be able to get round this by browsing for the specific message id.
It also sounds like you're storing information in a queue like it's a database. This is not usually a good idea, for reasons often discussed in the forum. You may find other solutions (like using a database) easier / better in the long term.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| nickkirk |
| Posted: Wed Oct 29, 2008 8:26 am Post subject: |
|
|
Apprentice
Joined: 26 Sep 2008
Posts: 48
|
Yes, it does seem to be moving the browse cursor.
Is there a way to reset the curser to the beginning of the FIFO queue ?
BTW: Vitor, We are using a FAILURE queue to temporarily store messages. The solution requires knowledge of the existence of a message on this queue. If the browse functionality does not work as expected, the MQGet node may propogate the message out the 'No Message' terminal even when there is a message on the queue. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Oct 29, 2008 8:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| nickkirk wrote: |
| Is there a way to reset the curser to the beginning of the FIFO queue ? |
Not within the node AFAIK but I'll accept correction from anyone who knows better.
| nickkirk wrote: |
| BTW: Vitor, We are using a FAILURE queue to temporarily store messages. The solution requires knowledge of the existence of a message on this queue. |
Which is exactly what the MQInput node provides - readign a message as soon as it arrives on a queue. Why are you using an MQGet? If you provide more details of your requirements and how you've arrived at your solution we might be able to provide an alternative solution.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| nickkirk |
| Posted: Wed Oct 29, 2008 9:46 am Post subject: |
|
|
Apprentice
Joined: 26 Sep 2008
Posts: 48
|
Apparantly there might be a way using the MQGMO_BROWSE_FIRST field to reset the browse cursor ???
Something like ; OutputLocalEnvironment.MQ.GET.MQGMO.MQGMO_BROWSE_FIRST = ???? |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Oct 29, 2008 11:24 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| We've answered this one before. You can influence the MQGMO in a compute node, read the online help in the toolkit. |
|
| Back to top |
|
|
|
|
