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 » Issues with NEON formats and Input Node Convert

Post new topic  Reply to topic
 Issues with NEON formats and Input Node Convert « View previous topic :: View next topic » 
Author Message
mcatama
PostPosted: Thu Apr 11, 2002 6:21 am    Post subject: Reply with quote

Novice

Joined: 10 Apr 2002
Posts: 17

We have message flows developed in MQSI 2.0.2 using NEON formats and are experiencing strange behaviour when we turn the Convert option on in the Input node.

In the flows we have compute nodes where we do not change the actual body of the message so we're using OutputRoot = InputRoot to pass the message through the node. This node is then followed by the output node. This works fine and the message is output correctly when input convert is off. When it is turned on the message fails on output with the error "Output format ITS_IC_PF not in database". However ITS_IC_PF is the name of our NEON input format. It appears to me as though MQSI thinks that the message body has changed and expects it to be in an output format? But this does not make any sense as it works fine without the convert option turned on and we have not changed the message body.

I can get around this first problem by forcing the mapping of input to output format in the compute node.

However, there is a second problem. We have a NEONRules node in the flow. If the message fails in this node an error is thrown, caught at the input node and the original message is passed to the output node. Once again this functionality works fine in the message flow without the convert option, but when convert is turned on the message again fails at the output node with whatever parsing error the NEONRules node generated.

We can recreate this behaviour on both NT and Sun Solaris.

Has anyone seen anything like this before? Is there anything obvious that we are missing related to turning on convert on the input node? Any help would be greatly appreciated.

Thanks
Alison

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 » Issues with NEON formats and Input Node Convert
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.