| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TDS Format Error |
« View previous topic :: View next topic » |
| Author |
Message
|
| msilva18 |
 Posted: Wed May 03, 2006 3:12 pm Post subject: TDS Format Error |
 |
|
Apprentice
Joined: 25 Aug 2004
Posts: 31
|
Hi All:
I have a problem, I need to put a message in a queue with TDS format, and the data separator between each field is "|", but I cannot put the message correctly in the queue, because the fields aren't separated with "|". I dont know if I need to configure something else. I'll try to find any manual of TDS but its not explicit of how to use this format.
Now Im trying only with one field and using Esql code, Im uniting all fields in one and Im putting the message in the queue, but when I get the message from the queue, the records in the message dont have an Enter at the end, and all records are together like in CWF format.
What can I do for separate the records with an Enter? Or How can I use correctly the TDS format using a lot of fields separated by "|" and with a lot of records separated by Enter.
Thanks a lot.
_________________
Ing. Manuel Silva Zaldivar |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed May 03, 2006 3:50 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The Model you use to parse the message on an Input queue has to match the format of the data on that queue. So if the input message is separated by "enter", which is either <LF>, or <CR><LF> then the MODEL has to indicate that this is how records are separated.
You can then change the MODEL you are using, and have an MQ Output node use that to CONSTRUCT the message based on that model.
So you can create a model that is separated by <CR><LF>, and a different model that is separated by "|", and wire a flow to change the properties of the message to indicate that the model has changed.
This, aside from the complexities of building the models with TDS, is basic useage of the product. You should have been taught that this is how things work in the training that of course you have had before you try and use a complicated and expensive product like WMB.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| msilva18 |
| Posted: Wed May 03, 2006 4:08 pm Post subject: |
|
|
Apprentice
Joined: 25 Aug 2004
Posts: 31
|
I understand you, but the flow is not that simple. The message in my MQ Input Node is in XML format, and I need to put the message in the MQ Output Node in TDS Format and each field in my input message must be separated by "|" in the Output Message.
And I didnt take a course of this product. I've been working with the product for two years and this is my first time that I used TDS Format, I usually used XML and CWF format.
_________________
Ing. Manuel Silva Zaldivar |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed May 03, 2006 7:49 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Input in format 1 mapped to output in format 2 is base use of the product.
Creating a TDS message set that uses "|" as a record delimiter is base use of the product.
I can tell that you haven't had training on this product. In my experience, anyone using this product should have training - I had training, and it helped a lot!
Modelling in TDS isn't significantly different than modelling in CWF. You just have to spend a little bit of time thinking about how the logical model of the tree should look. Then you have to spend a bit of time thinking about how the physical output message should look. Then you have to spend a little bit of time reading how the TDS modelling options work. Then you have to spend a little bit of time thinking about how to use the TDS modelling options to inform the logical model with the necessary properties of the physical output message model.
THEN you have to spend a little bit of time trying things, and seeing what happens, and understanding how the model you created relates to what you are seeing.
OR, you could provide a lot more information, in great and specific detail about individual fields and message structure and etc., about what you are actually trying to do, and hope that we are nice enough to help you solve this problem for free.
_________________
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
|
|
|
|
