ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » msg from MQOutput node carry same PutTime as in MQInput node

Post new topic  Reply to topic
 msg from MQOutput node carry same PutTime as in MQInput node « View previous topic :: View next topic » 
Author Message
pcelari
PostPosted: Thu Sep 13, 2007 11:18 am    Post subject: msg from MQOutput node carry same PutTime as in MQInput node Reply with quote

Chevalier

Joined: 31 Mar 2006
Posts: 411
Location: New York

I didn't realize this behavior until I log both input and output msg. It's a simple msgflow with one MQInput, three compute, and one MQOutput node. The compute nodes invokes three different remote stored procedures to get data and populate the output msg.

It is very fast, but it take over 100 ms to get the data, so in no way they can bear the same PutTime. But that's what the msg carry. I even explicily set the PutTime as Current_GMT, but everything is still the same.

Any idea what am I missing?

thanks for your insight.
_________________
pcelari
-----------------------------------------
- a master of always being a newbie
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Sep 13, 2007 11:22 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

CURRENT_GMT is always going to return the same time within a flow, no matter at what point in that flow you call it.

You can try clearing MQMD.PutTime before you output the message and make sure that you don't SetAll or SetContext.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
pcelari
PostPosted: Thu Sep 13, 2007 6:32 pm    Post subject: Reply with quote

Chevalier

Joined: 31 Mar 2006
Posts: 411
Location: New York

Could you explain what you mean by "clearing", I've got the set some value, or should I set it to 0?

I thought setAll means reset all, while passAll is keep original values.
_________________
pcelari
-----------------------------------------
- a master of always being a newbie
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Sep 13, 2007 7:41 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Yeah, maybe that didn't make as much sense as it could have.

The intent is to cause the qmgr to create a new PutTime. If you specify SetAll or SetContext, you're telling the qmgr not to do that. On the other hand, you're also telling broker to set the fields to, umm, what you've set them to.

I think what you should do is use Default instead of SetAll or SetContext or PassAll. Then clear as many of the MQMD fields as you can and still save the information you need - by setting them to Null. Default tells Broker to tell Qmgr to create a new MQMD.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » msg from MQOutput node carry same PutTime as in MQInput 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
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.