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 » Optional field in TDS

Post new topic  Reply to topic
 Optional field in TDS « View previous topic :: View next topic » 
Author Message
leongor
PostPosted: Mon Sep 01, 2003 4:00 am    Post subject: Optional field in TDS Reply with quote

Master

Joined: 13 May 2002
Posts: 264
Location: Israel

When using TDS format I can set some compound type to be optional.
Can I set some field to be optional inside a compound type ?
_________________
Regards.
Leonid.

IBM Certified MQSeries Specialist.
Back to top
View user's profile Send private message
Craig B
PostPosted: Tue Sep 02, 2003 7:09 am    Post subject: Reply with quote

Partisan

Joined: 18 Jun 2003
Posts: 316
Location: UK

Generally TDS supports optional elements and you do not have to make settings to make use of these. The Connection tab in the MRM model allows you to specify minOccurs and maxOccurs, but when considering optional elements, these are only used for validation purposes. So if you have not enabled message validation then any element can be optional irrespective of what you have set for these values.

However, some TDS data element seperation techniques do not support optional elements. An element can only be allowed to be optional if the TDS parser can calculate that it is missing and continue parsing the message with this element missing. Therefore data element separation techniques that are tagged or delimited, the parser can calculate which elements are present and which are not, and therefore optional elements can be used. However, when dealing with Fixed Length data element separation techniques, then it is not possible to have optional elements. This is because the parser is dependent on a certain numbers of characters being present and in the correct order.

Therefore in an element was optional, the bitstream would not be of the correct length and will not be in the correct order.
_________________
Regards
Craig
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 » Optional field 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.