|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
XML -> TDS message failure |
« View previous topic :: View next topic » |
Author |
Message
|
Captain_EMO |
Posted: Tue May 15, 2007 5:26 am Post subject: XML -> TDS message failure |
|
|
 Newbie
Joined: 08 Feb 2007 Posts: 4 Location: St. Louis, Missouri
|
I am having a sticky issue in converting an XML message to TDS and would like some friendly advice if possible.
I have four complex message types defined:
DETAIL - (DES) fixed length, group indicator "D", group terminator <CR><LF>
BIN - (DES) fixed length, group indicator "B", group terminator <CR><LF>
QUALTIY - (DES) fixed length, group indicator "Q", group terminator <CR><LF>
ZBRLYSHPREC - (DES) fixed length and comprised of DETAIL, BIN and QUALITY (note, BIN and QUALITY min occurs = 0 max occurs = 99)
When I run my message flow in debug I see the MRM create one DETAIL structure, two BIN structures and 4 QUALITY structures which agrees with the inbound XML. There is no ESQL error, etc. and all fields in these are populated correctly.
However, the messge flow fails at the MQOutput node with a parser error stating that a mandatory field (which happens to be the first field in each structure) does not have a default value nor is populated.
All I'm trying to do is get a message in the following format (basically, a flat file structure with each line terminated with <CR><LF>):
D - data - <CR><LF>
B - data - <CR><LF>
B - data - <CR><LF>
Q - data - <CR><LF>
Q - data - <CR><LF>
Q - data - <CR><LF>
Q - data - <CR><LF>
Also note that as stated earlier, only the DETAIL record is required. The BIN and QUALITY are optional and possibly multiple in instance.
Thanks in advance. I'm hoping it is something very simple that I am not grasping. |
|
Back to top |
|
 |
kimbert |
Posted: Tue May 15, 2007 6:47 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Hard to advise you without more details about the structure of your message definition. This is probably caused by your message tree not matching your message definition. If you switch on user trace ( and you're on v6 ) you will probably see warnings about self-defining fields in your message - that's a sure sign that your message definition does not match your message tree. |
|
Back to top |
|
 |
Captain_EMO |
Posted: Wed May 16, 2007 4:46 am Post subject: |
|
|
 Newbie
Joined: 08 Feb 2007 Posts: 4 Location: St. Louis, Missouri
|
Thanks, Kimbert. I appreciate the fact you took the time to respond.
I have gone ahead and rebuilt my message set for CWF. I added in the necessary binary integer elements so that the repeatable "B"in and "Q"uality records (types) would work. I then converted that to BLOB, stripped out my binary integer references then spliced in the <CR><LF> accordingly. Ugly, inelegant...but, hey, it works.
If I get a chance to put the message set back as TDS as I had it then I'll try to replicate the issue and provide further information. I know that doing this through a simple XML to TDS flow would be less overhead, etc.
Thanks, again. |
|
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
|
|
|
|