| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TDS Problems |
« View previous topic :: View next topic » |
| Author |
Message
|
| Kjell |
 Posted: Thu Sep 01, 2005 9:54 am Post subject: TDS Problems |
 |
|
Acolyte
Joined: 26 Feb 2002
Posts: 73
|
Problems again,
I have the following structure.
Seg01
----SegLength 4 ch
----SegNo 2 ch
----field 1 8 ch
----field 2 8 ch
----Seg11 occurs 0 - 4 times
--------------SegLength 4 ch
--------------SegNo 2 ch
--------------field 1 10 ch
--------------field 2 14 ch
----Seg12 occurs 0 - 8 times
--------------SegLength 4 ch
--------------SegNo 2 ch
--------------field 1 10 ch
--------------field 2 25 ch
--------------field 3 25 ch
As you can see, all segments are identified by the concatenation of Seglength and SegNo, however there's nothing in the preceding segment telling which
segment that comes next.
I am tryin to setup a TDS for this one, I set "fixed length" on the child segments and I then try to set ""tagged fixed length" on Seg01. This would
have worked if Seg01 contained the two child segments only, but now it contains both "own fields" and child segments and then the editor complaints, that I
need to tag all the fields in the seg, not only the child segments.
How to set up the TDS for a structure like this? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Sep 01, 2005 9:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You have some choices in this matter.
A good option would be to incldue Seg11, Seg12 and etc in a Group. Set the group composition to "Choice", and then include elements of each type in the group.
Then include an element of the Group in the Seg01 group.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kishoreraju |
| Posted: Thu Sep 01, 2005 9:07 pm Post subject: |
|
|
Disciple
Joined: 30 Sep 2004
Posts: 156
|
Jeff,
Can you tell why we have to use only choice. i am going through that pdf, but not qable get a clear idea on that. |
|
| Back to top |
|
|
| Kjell |
| Posted: Thu Sep 01, 2005 11:58 pm Post subject: |
|
|
Acolyte
Joined: 26 Feb 2002
Posts: 73
|
OK I followed your advise but I cannot have it work.
1 I Established a group, composition "choice", validation "closed".
2. I included the child segments in the group.
3. I Added the group to Seg01.
When I ran it in the debug it says "TDS General error" under the MRM domain in the flow debugger. No more info.
Also, when I usedd Tagged-Delimited, the SegLength and the SegNr fields were considered as taggs and did not appear in the message so I had to take away these two elements from the message definition and I don't want that.
* How can I use Tagged-Delimited and use the SegLength and SegNr as a TAG but all the same have them as elements in the message definition?
I cannot have it work. I have to change to "use data pattern" and then I got this TDS general error. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Sep 02, 2005 3:54 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You don't necessarily need to use choice. But if you don't know what order your different segments are going to come in, then you do need to use choice.
You can't have a tag appear as an element. But you know that the tag appeared if a field belonging to that tag appears.
You will need to use tags in order to have the parser resolve the choice for you.
You should be able to set each segment to be fixed length, and the choice to be tagged-fixed length.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
