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: remove new line failed in case of optional types

Post new topic  Reply to topic
 TDS: remove new line failed in case of optional types « View previous topic :: View next topic » 
Author Message
dick spaans
PostPosted: Tue Jun 15, 2004 12:40 am    Post subject: TDS: remove new line failed in case of optional types Reply with quote

Newbie

Joined: 15 Jun 2004
Posts: 1
Hello,

I have created a message set in TDS for messages to be outputted. Its type is built up of "lower level" types. These "lower level" types are optional.
These "lower level types" have the following characteristics:
1. Under "messages" on the TDS-tab: Repeating Element Delimiter=<LF>
2. Under "types" on the TDS-tab: Data Element Seperation=Fixed Length

The consequence of this is - in case one of the optional "lower level" types is missing - a blank line in the resulting message between two "lower level" types. This blank line must be removed. But how???

I tried it by converting to BLOB and change 0d0a0d0a by 0d0a using the ESQL POSITION and LENGTH-functions, but that does not seem to work.

Can I solve the problem within the messageset itself?
Or by repairing it in BLOB on another way?

thanks already, Dick Spaans
_________________
Dick Spaans
Software Developer WMQI
Fortis ASR the Netherlands
Back to top
View user's profile Send private message Send e-mail
fiona
PostPosted: Fri Jun 25, 2004 6:59 am    Post subject: Reply with quote

Newbie

Joined: 25 Jun 2004
Posts: 1
Hello

I'm a little bit lost here.... what's your outer separation tpe containing the optional types?

If you'r using AED, then delimiter suppression will mean the parser expects all the REDs to be present. Does that help?

Thanks for any more information,
Fiona
Back to top
View user's profile Send private message
wooda
PostPosted: Fri Jun 25, 2004 7:36 am    Post subject: Reply with quote

Master

Joined: 21 Nov 2003
Posts: 265
Location: UK
I think what you are saying is that you have a message consisting of a number of different optional records (lines).
Now if these "lower types" as you call them are not identified in any way then and you have missing intermediate lines then you have an ambiguos model unless the extra newlines are added to show the missing lines.
How can the parser know which line it is parsing? (Is it line2 or is line2 missing and the second line is line3 etc.)

Q. Does your message have any way of identifying which line of data matches which structure in the model ?

Tags, identifiers or even a specific length or pattern of data ?

If the answer to the above is Yes then there is a light at the end of the tunnel.
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: remove new line failed in case of optional types
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.