| Author |
Message
|
| jefflowrey |
 Posted: Thu Apr 20, 2006 4:50 am Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| dazza wrote: |
| In the trace file, should I see all the DATA elements padded out to 256 characters? |
No. Padding is a physical property - the trace file shows the logical structure.
When you created your group - did you add it to your message type as an ELEMENT or as a TYPE?
Your message type should contain a single local element of your group's complex type.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Thu Apr 20, 2006 5:18 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Hi dazza,
You're up against a limitation in v5. This works in v6. However, we're investigating a workaround for you. I'll post again when I've got an answer. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Apr 20, 2006 5:52 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Try this:
- Move the DATA element back up into the complex type and delete the group which it was in
- Change 'Fixed Length' to 'Tagged Fixed Length' on the complex type
- Set Tag Length to 0 ( zero ) on the complex type
- Set maxOccurs to -1 on the DATA element.
I'm not able to try this out, because I don't have a v5 installation. However, I am assured that this approach can work, so if you hit further problems, just ask again. |
|
| Back to top |
|
|
| dazza |
| Posted: Fri Apr 21, 2006 12:10 am Post subject: |
|
|
Newbie
Joined: 18 Apr 2006
Posts: 9
|
Once again, thanks for your continuing help. I played around with your suggestion yesterday afternoon but I am still having problems.
When I try what you suggested I get the following 1 warning and 1 error:
| Code: |
Warning High Element 'DATA' does not have a Tag specified in a structure with Data Element Separation of 'TaggedFixedLength'. If it is used in a TDS message, that message will not parse successfully. Physical format: 'TDS1'. SeverfieldReeveOut.mxsd ASDEDI_SeverfieldReeve_Out_MsgSet/ASDEDI_SeverfieldReeve_Out_MsgSet
Error Element 'DATA' must have a Tag of length '0' to comply with its enclosing structure with Data Element Separation of 'TaggedFixedLength'. Physical format: 'TDS1'. SeverfieldReeveOut.mxsd ASDEDI_SeverfieldReeve_Out_MsgSet/ASDEDI_SeverfieldReeve_Out_MsgSet
|
Just to confirm, here are the current setting:
Complex type
Physical Properties -> TDS1 -> Complex Type -> Field Identification -> DES -> TaggedFixedLength
Distringuish tag & data values using -> Length of tag 0
Min and max occurs for the complex type are both set to 1
Data element
Mix occurs set to 1
Max occurs set to -1
Physical representation:
Type : Character
Length : 256
Justification : Left Justify
Padding : SPACE
I can get rid of the warning if I enter a value into the Physical properties -> TDS1 -> Local element -> Field Identification -> Tag text box.
The problem is I don't know what I should put in this text box as I don't have a tag in the output. Or, can this be set to NULL?
Cheers. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Apr 21, 2006 1:41 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
OK - we're getting closer to a solution. We need to get rid of the error 'Element DATA must have a Tag of length 0'. Here's how:
- Set the Tag for element DATA to something ( say 'A' )
- Save the .mxsd file
- Delete the Tag for element DATA ( i.e. set it to the empty string )
- Save the .mxsd file again
The error should now have disappeared. ( please don't ask why ). Let me know how you get on. |
|
| Back to top |
|
|
| dazza |
| Posted: Mon Apr 24, 2006 12:19 am Post subject: |
|
|
Newbie
Joined: 18 Apr 2006
Posts: 9
|
You were right!!! The error did go away. This left me with just the following warning:
| Code: |
Warning High Element 'DATA' does not have a Tag specified in a structure with Data Element Separation of 'TaggedFixedLength'. If it is used in a TDS message, that message will not parse successfully. Physical format: 'TDS1'. SeverfieldReeveOut.mxsd ASDEDI_SeverfieldReeve_Out_MsgSet/ASDEDI_SeverfieldReeve_Out_MsgSet
|
As this was only a warning I redeployed the new message set. I have done a quick test and it seems to have worked.
I will do a more advance test with actual data and let you know - but it is looking good!!
Thanks you so much for all your help. It is very much appreciated. Also, thanks to all you hepl, I feel that I really understand the whole tagged MRM concepts a lot better now. |
|
| Back to top |
|
|
| dazza |
| Posted: Mon Apr 24, 2006 4:26 am Post subject: |
|
|
Newbie
Joined: 18 Apr 2006
Posts: 9
|
I have just tested the set and flow using several huge production data files and it worked like a charm.
Once again, thank you so much for all your help. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Apr 24, 2006 6:00 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Glad it's working. Sorry it took a while. If your messages are huge, you might care about performance. If you do, v6 is well worth a look ( check out the comparitive performance benchmarks for TDS ). |
|
| Back to top |
|
|
|
|
