[This message was posted by Bernt Sanden of Cinnober Financial Technology <[email protected]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/682353c3 - PLEASE DO NOT REPLY BY MAIL.]
Hi, I can think of the following ways of handling unsupported optional fields: 1) Silently ignore the field. 2) Send a business level reject, for example an ExecutionReport to reject a New Order Single, indicating that the field is not supported. 3) Exclude the non supported field in our FIX repository which will have the effect that we send a session level reject instead with 373=3 (undefined tag) as we do not recognize that tag. Please advise Regards, Bernt [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]]
-- You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en.
