[This message was posted by Hanno Klein of Deutsche Börse Systems <[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/031028d8 - PLEASE DO NOT REPLY BY MAIL.]
I would argue that this depends on your market model and "per day" is more like a minimum. If you have orders that can be valid for more than a single day, a re-use of ClOrdID after one day will cause problems. Another aspect is whether you want ClOrdID to be unique for a given sender across all products. This might create an artficial bottleneck for the receiving system so that you prefer uniqueness to be restricted to a single orderbook (tradable entity). The scope of uniqueness can thus not be defined in general and might differ across FIX usage environments. The issue has been discussed for exchange environments in a paper compiled by the FIX Global Exchanges & Markets Committee, chapter 3.1.1 (http://www.fixprotocol.org/documents/3005/EEWG%20Recommended%20Best%20Practices%20-%20Phase%201%20V1.0.pdf). Regards, Hanno. > > A very basic and stupid question: Within a single trading day, the > > uniqueness of client order id (tag 11/tag41), should it be maintained > > within a single FIX session (/sendercompID) or within > > SenderCompID+OnBehalfOfCompID? > > > > Thank you for any advice. > > It has to be unique per FIX session (SenderCompID + TargetCompID) per > day. [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 -~----------~----~----~----~------~----~------~--~---
