[This message was posted by Jim Northey of The LaSalle Technology Group <[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/ec8811c2 - PLEASE DO NOT REPLY BY MAIL.]
I wonder why SecondaryTransactTime never made it into the spec - maybe because of the TrdRegTimestamps block. Although the TrdRegTimestamps was added specifically to address regulatory timestamps required for computerized trade reconstruction as mandated by the CFTC for US markets. > Later versions of FIX have a TrdRegTimestamps component block that would > work. > http://www.fixprotocol.org/FIXimate3.0/en/FIX.5.0SP2/body_49485048.html > > But it might just be easier to use custom tag : > > 5164 SecondaryTransactTime Time of execution at the exchange level when > TransactTime is already used by the broker order management system. > > > > > We are on our own bastardized 4.1 but we can add any from other > > versions that might have this. > > > > > > > What version of FIX are you using? > > > > Hi, > > > > > > > > we provide an OMS to both buy-side and sell-side clients. We > > > > generated our own ExecID(tag 17) and TransactTime(tag 60) when we > > > > match buyside to sellside and that is what is publish out onto > > > > fix. some of our buy side firms want to also provide their own > > > > ExecID and TransactTime fields. We want to use > > > > SecondaryExecID(527) for client contributed ExecID. > > > > > > > > What are ya'll recommendations as the best field to use for the > > > > secondary TransactTime that clients want to contribute ? if indeed > > > > there is anything to use. We might have to do custom fields. > > > > > > > > thanks [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.
