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 » Problem with optional segment in TDS

Post new topic  Reply to topic
 Problem with optional segment in TDS « View previous topic :: View next topic » 
Author Message
vadivel
PostPosted: Thu Jan 15, 2004 10:24 pm    Post subject: Problem with optional segment in TDS Reply with quote

Voyager

Joined: 05 Aug 2002
Posts: 79
Location: US

Hi,

I have a TDS message set with multiple records (segments) in it. The elements within each segment are delimited and the segments are again delimited by <CR><LF>.
All the segments in the message are optional, they can occur 0 or more times. For this I've given the min occurs to 0 and max occurs to 9999 in the connection tab.
The problem is, when I create a message with 1st and 4th segment only, I get 3 <CR><LF> characters between the 1st and 4th segment.
Can anyone please tell me how to avoid this.

This is how my Message set looks like:
Message (All elements delimited by <CR><LF>)
Segment1 (All elements delimited by <HT>, Connection min 0, max 999)
Segment2 (All elements delimited by <HT>, Connection min 0, max 999)
Segment3 (All elements delimited by <HT>, Connection min 0, max 999)
Segment4 (All elements delimited by <HT>, Connection min 0, max 999)

Thanks & Regards

Vels
Back to top
View user's profile Send private message Yahoo Messenger
kimbert
PostPosted: Fri Jan 16, 2004 2:09 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

How do you identify the segments? If they are not tagged, then you need the extra delimiters...otherwise, if Segment2 and Segment3 are missing, Segment4 will appear where we expect Segment 2. The TDS writer is doing the right thing, as far as I can see.
Back to top
View user's profile Send private message
wooda
PostPosted: Fri Jan 16, 2004 2:17 am    Post subject: Reply with quote

Master

Joined: 21 Nov 2003
Posts: 265
Location: UK

kimbert is right you have to have someway of telling whats a segment2 and whats a segment 4 etc.
they could be tagged or prefixed with a simple indentifer for if there is
something in the data which will identifiy them thenyou can use a datapattern separtion technique. This would allow you to have no tages but instead use a regular expresion to identify them.
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 » Problem with optional segment in TDS
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.