| Author |
Message
|
| Angel |
 Posted: Fri Mar 24, 2006 4:31 am Post subject: Problem with TDS message set |
 |
|
Newbie
Joined: 24 Mar 2006
Posts: 6
|
Hello,
I am trying to create a TDS message set according to the below message:
8=FIX.4.3<SOH>
9=278<SOH>
35=B<SOH>
49=SSMB<SOH>
56=CSFB<SOH>
34=1<SOH>
52=20020214-12:05:08<SOH>
148=KPN Qwest files for bankruptcy<SOH>
33=1<SOH>
58=Dutch telecoms outfit KPNQwest filed for bankruptcy this afte...<SOH>
10=079<SOH>
Tagged delimited:
Tag: numberic identifier (such as 8, 9....)
Tag Data Separator: =
Data delimiter: <SOH>
It seems as if <SOH> is not accepted as a delimiter. When I am replace the <SOH> with a space the message is parsed correctly.
Does anyone know why <SOH> doesn't work as a delimiter?
Appreciate some help.
/Rama |
|
| Back to top |
|
 |
| kimbert |
| Posted: Fri Mar 24, 2006 4:39 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| It seems as if <SOH> is not accepted as a delimiter. |
What goes wrong when you use <SOH>? Do you get a parsing exception, or just the wrong data in the tree? |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Fri Mar 24, 2006 4:41 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi ramaksedd,
I could understand that <SOH> did not work, it could have been <SOH> + <CR><LF>(i dont mean literally use this)
What i dont understand how it worked with a space....do u mean u replaced all the <SOH> by a space and made space the delimiter in the message set......or u simply used space as delimiter in the message set,without changing the input message 
Regards. |
|
| Back to top |
|
|
| Angel |
| Posted: Fri Mar 24, 2006 4:51 am Post subject: Problems with TDS message set |
|
|
Newbie
Joined: 24 Mar 2006
Posts: 6
|
Hi,
I don't get any exceptions, the message is parsed as if everything is the first tag, like below:
tag 1 = FIX.4.3<SOH>9=278<SOH>35=B<SOH>49=SSMB<SOH>56=CSFB<SOH>34=1<SOH>52=20020214-12:05:08<SOH>148=KPN Qwest files for bankruptcy<SOH>33=1<SOH>58=Dutch telecoms outfit KPNQwest filed for bankruptcy this afte...<SOH>10=079<SOH>
instead of
tag 1= FIX.4.3
tag 2= 278
tag 3= B
.
.
Seems to me that it doesn't understand that <SOH> is the delimiter.
I did replace the <SOH> as delimiter in the message set to space and changed the input message. Just to verify that I have build the message set correctly.
The input message I use is as below:
8=FIX.4.3<SOH>9=278<SOH>35=B<SOH>49=SSMB<SOH>56=CSFB<SOH>34=1<SOH>52=20020214-12:05:08<SOH>148=KPN Qwest files for bankruptcy<SOH>33=1<SOH>58=Dutch telecoms outfit KPNQwest filed for bankruptcy this afte...<SOH>10=079<SOH>
So, the <CF><LF> may not work either. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Mar 24, 2006 5:38 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
Can I just check something? In your input message, is <SOH> a single byte with the value 0x01, or is it the 5-character string "<SOH>"?
FYI, the TDS parser will assume that you mean 0x01, because <SOH> is a defined TDS mnemonic character. |
|
| Back to top |
|
|
| dsriksha |
| Posted: Fri Mar 24, 2006 5:40 am Post subject: Re: Problems with TDS message set |
|
|
Voyager
Joined: 27 Feb 2005
Posts: 95
|
| ramaksedd wrote: |
Hi,
So, the <CF><LF> may not work either. |
You need to try<CR><LF> |
|
| Back to top |
|
|
| Angel |
| Posted: Fri Mar 24, 2006 6:21 am Post subject: |
|
|
Newbie
Joined: 24 Mar 2006
Posts: 6
|
Hi again,
Yes, "<SOH>" is the single byte with the value 0x01. So the TDS parser understand that <SOH> is 0x01 because I have written explicitly <SOH> as 5-character string in the delimiter section. Or do I have to use other characters to tell the parser that the delimiter is 0x01?
Thanks, |
|
| Back to top |
|
|
| Angel |
| Posted: Fri Mar 24, 2006 6:27 am Post subject: |
|
|
Newbie
Joined: 24 Mar 2006
Posts: 6
|
Hi again,
Sorry, I missunderstood your question.
In the input message the <SOH> is used as 5-character string. But it is the x0x1 that is the delimiter. Aha, now I understand. So my input message is wrong? 
Which characters should I use then in my input message?
Regards, |
|
| Back to top |
|
|
| Angel |
| Posted: Fri Mar 24, 2006 6:30 am Post subject: Re: Problems with TDS message set |
|
|
Newbie
Joined: 24 Mar 2006
Posts: 6
|
| dsriksha wrote: |
| ramaksedd wrote: |
Hi,
So, the <CF><LF> may not work either. |
You need to try<CR><LF> |
I have just discovered that my input message may be wrong, but I will try this also...
Thanks, |
|
| Back to top |
|
|
| dsriksha |
| Posted: Fri Mar 24, 2006 6:36 am Post subject: |
|
|
Voyager
Joined: 27 Feb 2005
Posts: 95
|
| Quote: |
| Which characters should I use then in my input message? |
Its good to build the message set according to the message, until and unless you have a right to change the message format. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Mar 24, 2006 6:36 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| Which characters should I use then in my input message? |
The same ones as you are using now, but replace every occurrence of <SOH> with a single byte 0x01. It's up to you how you do that. Personally, I find perl's pack() function really useful  |
|
| Back to top |
|
|
| Angel |
| Posted: Fri Mar 24, 2006 6:39 am Post subject: |
|
|
Newbie
Joined: 24 Mar 2006
Posts: 6
|
| kimbert wrote: |
| Quote: |
| Which characters should I use then in my input message? |
The same ones as you are using now, but replace every occurrence of <SOH> with a single byte 0x01. It's up to you how you do that. Personally, I find perl's pack() function really useful |
Thanks, I will try it... |
|
| Back to top |
|
|
|
|
