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 » TDS message unable to parse

Post new topic  Reply to topic
 TDS message unable to parse « View previous topic :: View next topic » 
Author Message
wmqiadmin
PostPosted: Sun Aug 26, 2007 9:18 pm    Post subject: TDS message unable to parse Reply with quote

Disciple

Joined: 19 Jun 2005
Posts: 163
Location: epping UK

Hi All,

I am working with MB V6.01, Toolkit 6.02.

I have created TDS message set with delimeter message (*) and TDS tag (*), deployed the message flow and message set. When i debug the message i don't see any values in the message set message, in the out put node i get a blank message. Broker is unable to parse the message.

Any idea what is happening?

Thanks
wmqiadmin
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sun Aug 26, 2007 9:27 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

With that level for the toolkit shouldn't you be at 6.0.0.3 for the broker? and not 6.0.0.1 !
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
wmqiadmin
PostPosted: Sun Aug 26, 2007 9:33 pm    Post subject: Reply with quote

Disciple

Joined: 19 Jun 2005
Posts: 163
Location: epping UK

yes that is true brk is at V603

my data is data1*data2*data3 format and i have set delimeter as *, no group indicator or terminator, no length specification. and have set field Tag to *. still getting the same error, any idea what i am doing wrong??


ImbRecoverableException caught from worker->parseNext.


Last edited by wmqiadmin on Sun Aug 26, 2007 9:45 pm; edited 1 time in total
Back to top
View user's profile Send private message
MBExpert
PostPosted: Sun Aug 26, 2007 9:45 pm    Post subject: Reply with quote

Novice

Joined: 22 Aug 2007
Posts: 14

Hi wmqiadmin,

You would have to provide little more information on the message you are trying to parse and corresponding messageset properties.

And also, did you see in debugger if its giving some TDS parser error whicle passing through the node (that supplies the custom messageset properites)?

Regards
Back to top
View user's profile Send private message
wmqiadmin
PostPosted: Sun Aug 26, 2007 9:46 pm    Post subject: Reply with quote

Disciple

Joined: 19 Jun 2005
Posts: 163
Location: epping UK

just edited my previos post
Back to top
View user's profile Send private message
wmqiadmin
PostPosted: Sun Aug 26, 2007 9:56 pm    Post subject: Reply with quote

Disciple

Joined: 19 Jun 2005
Posts: 163
Location: epping UK

where do i see "All Elements Delimited" property in the message set?
Back to top
View user's profile Send private message
wmqiadmin
PostPosted: Sun Aug 26, 2007 10:05 pm    Post subject: Reply with quote

Disciple

Joined: 19 Jun 2005
Posts: 163
Location: epping UK

guys any idea about the error??
Back to top
View user's profile Send private message
elvis_gn
PostPosted: Sun Aug 26, 2007 10:22 pm    Post subject: Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi wmqiadmin,
wmqiadmin wrote:
where do i see "All Elements Delimited" property in the message set?
Once you've defined your complex type, go to Properties pane.

There in Physical Properties->TDS->Complex Type->Data Element Seperation.

In the list you'll find 'All Elements Delimited'.

What is your End of line delimiter ? If you have one...

Regards.
Back to top
View user's profile Send private message Send e-mail
kimbert
PostPosted: Mon Aug 27, 2007 10:17 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

- You have quoted a single error, which gives no information at all about the problem. If you set up your message flow correctly, you will get a chain of parsing exceptions ( including the one which you posted ). I find that the best way to get the full text of all parsing exceptions is to take a user trace while the message is being parsed.
- Your message set design is way off beam. You need to understand the difference between a tag and a delimiter. Your data is 'All Elements Delimited' so you certainly do not need tags.

You shouid review the v6 samples - there are example message sets for parsing delimited data in the samples gallery.
Back to top
View user's profile Send private message
MBExpert
PostPosted: Mon Aug 27, 2007 11:00 pm    Post subject: Reply with quote

Novice

Joined: 22 Aug 2007
Posts: 14

I agree with kimbert...

When you have "All Elements Delimited", you should not be specifying the tag at all.

If the data form is Data1*Data2*Data3 without any end of line character or not any specific beginning character, you just have to make All elements delimited and the Delimiter to be *. It should solve ur purpose.
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 » TDS message unable to parse
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.