MQSeries.net :: View topic

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQGet Node

MQGet Node

« View previous topic :: View next topic »

Author

Message

bobbee

Posted: Fri Jan 09, 2009 6:40 am Post subject: MQGet Node

Knight

Joined: 20 Sep 2001
Posts: 545
Location: Tampa

I have a flow with an MQGET Node. When I run through the node the first time it returns the one and only message on the queue. I have the MQGET node set to 'BROWSE' on subsequent executions of the flow it returns a 2033. After the flow and if I have it set at breakpoints before and after the node I can use RFHUTIL to read the message. I then thought 'maybe' there was a lock on a browse pointer. So I added an MQHeader node just prior to the MQGET node and initialized the MsgId and CorrellId fields to 'none' and pointed the MQGET node to that MQMD in InputRoot.MQMD.

Same 2033 after the first read.

Vitor

Posted: Fri Jan 09, 2009 6:46 am Post subject: Re: MQGet Node

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

bobbee wrote:

I then thought 'maybe' there was a lock on a browse pointer. So I added an MQHeader node just prior to the MQGET node and initialized the MsgId and CorrellId fields to 'none' and pointed the MQGET node to that MQMD in InputRoot.MQMD.

Same 2033 after the first read.

Resetting the header information doesn't alter the fact the 1st MQGet has a browse lock on the message so it's unavailable.

If you need the same message twice in the same flow, copy the details someplace (Environment? Database? Somewhere better I've not thought of?) and reference it later.
_________________
Honesty is the best policy.
Insanity is the best defence.

bobbee

Posted: Fri Jan 09, 2009 9:16 am Post subject:

Knight

Joined: 20 Sep 2001
Posts: 545
Location: Tampa

Wow, like Zed the wizard sez all the time "Nothing ever easy"

Put a compute node befor the MQGET node with this one liner in it...

set OutputLocalEnvironment.MQ.MQGET.MQGMO.Options = MQGMO_BROWSE_FIRST;

The I set the MQ Input Parameters Location field on the MQGET Node to this....

InputLocalEnvironment.MQ.MQGET

It now rereads as expected. So it would seem the MQGET node is set up by default for looping through a queue in a Message flow. Not sure if that would be my choise for default processing but hey who am I to argue. I drink Coors not English beer!!! Thanks everyone for your suggestions.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQGet Node

Jump to:

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

Protected by Anti-Spam ACP