Re: [Quickfix-developers] RE: "Value is incorrect (out of range) for this tag" error for proprietary field value

[Alvin W. <AW...@FF...>]

Hi Jim,

I am just thinking to make QF more configurable, flexible, and maybe more 
forgiving if needed. There would still be value of dictionary even if QF 
allow proprietary field value. On top of my mind, for example, data type 
checking. Another example, we built a translator to convert raw FIX 
message to a more human readable with dictionary, for the purpose of 
debugging and display.

Counterparty spec is a moving target... You will be surprised by some of 
them from time to time.

Thanks
Alvin






"James C. Downs" <jc...@co...>
Sent by: qui...@li...
06/07/2005 10:56 AM

 
        To:     "'Alvin Wang'" <AW...@FF...>, 
<qui...@li...>, 
<qui...@li...>
        cc:     <dav...@ma...>, "'Joerg Thoennes'" <Joe...@ma...>, 
"'Oren Miller'" <or...@qu...>, "'Yihu Fang'" 
<Yih...@re...>
        bcc: 
        Subject:        [Quickfix-developers] RE: "Value is incorrect (out of range) for this tag" 
error for    proprietary field value


Alvin,
Please forgive me but I guess I am a little unclear as to the new 
configuration feature you are requesting. Would it be a setting that tells 
QF not to check the field values for a particular field? All fields? If 
this is the case what is the purpose of the data dictionary (other then 
needing it for repeating groups)? Additionally, when connecting to a 
counter party there is typically an exchange of interface specifications 
that delineate the deviations form the standard FIX specification thus 
avoiding the apparent "test in production" scenario you described above.
 
 
Jim

From: qui...@li... 
[mailto:qui...@li...] On Behalf Of Alvin Wang
Sent: Tuesday, June 07, 2005 5:03 PM
To: qui...@li...; 
qui...@li...
Cc: dav...@ma...; Joerg Thoennes; Oren Miller; Yihu Fang
Subject: "Value is incorrect (out of range) for this tag" error for proprietary 
field value


Hi, 

Can we have a new configuration that allows proprietary field value for a 
tag.  For example, today we received a message with 
MessageEncoding(347)=UTF-8. However, in Quickfix dictionary, it is UTF_8 
(BTW, i believe UTF-8 is official according to FIX document). We had to 
manually edit FIX44.xml and restart our FIX engine. That means, each time 
counterparty has a proprietary field value, we have to manually add it 
into the dictionary, otherwise the message will be rejected by QF. 

Thanks 
Alvin 
********************************************************************** 
This e-mail message is intended solely for the use of the addressee. The 
message may contain information that is privileged and confidential. 
Disclosure to anyone other than the intended recipient is prohibited. If 
you are not the intended recipient, please do not disseminate, distribute 
or copy this communication, by e-mail or otherwise. Instead, please notify 
us immediately by return e-mail (including the original message with your 
reply) and then delete and discard all copies of the message. We have 
taken precautions to minimize the risk of transmitting software viruses 
but nevertheless advise you to carry out your own virus checks on any 
attachment to this message. We accept no liability for any loss or damage 
caused by software viruses. 
**********************************************************************