| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TDS message modeling / flat to XML and vice verse |
« View previous topic :: View next topic » |
| Author |
Message
|
| sebastian |
 Posted: Thu Jun 24, 2004 10:10 am Post subject: TDS message modeling / flat to XML and vice verse |
 |
|
Centurion
Joined: 12 Nov 2003
Posts: 110
Location: Philadelphia
|
I am using MQSI v2.1
I created a message set that has physical formats of TDS and XML. I can use a compute node and use ESQL of...
SET OutputRoot = InputRoot;
SET OutputRoot.Properties.MessageFormat='XML';
THis transforms the message from input TDS to XML fine. What I am having a problem with is changing the data in the other direction using the same message set.
I changed my input node from message format of XML to TDS. I also changed the comput node to read
SET OutputRoot = InputRoot;
SET OutputRoot.Properties.MessageFormat='TDS';
Since I am using the same XML that was generated as ouput earlier, I do not see what the problem is. I get the error " BIP545
2E: Mandatory Element EL_1 has no value or default value set." I looked at the input data and I see a value for the EL_1 tag.
Any feedback is appreciated,
Seb
_________________
sebastian signature |
|
| Back to top |
|
 |
| kimbert |
| Posted: Fri Jun 25, 2004 1:52 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
So your TDS message has Data Element Separation of 'Fixed-Length'?
It sounds as if there is an element missing from the message tree. The TDS parser is looking to use a default value, but that is not set either. I cannot comment on why an element would be missing - if you have simply put the output XML back into your message flow, I would have expected all the elements to be present.
In this situation, you need to see the message tree after the parse. If you are using v5.0, use the debugger to inspect the message tree before and after the compute node. If you are using 2.1, insert a trace node before and after the Compute node. |
|
| Back to top |
|
|
| wooda |
| Posted: Fri Jun 25, 2004 8:04 am Post subject: |
|
|
Master
Joined: 21 Nov 2003
Posts: 265
Location: UK
|
Check that the message set does indeed have an XML layer defined.
Check that it is called "XML".
Check the domain,set,type and format are correctly defined for the input XML message.
It is possible that for some reason (like any of the above) that you are not using the XML layer defined to the messageset. This would mean it writes ok in XML using default XML properties but when it is parsed the elements will not match the model although as it is XML it will happily parse them as self-defined element. So when you output in TDS all the expected fields would be missing.
Also check that the XML message contains all the fields you expect it to contain. |
|
| 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
|
|
|
|
