[This message was posted by Hanno Klein of Deutsche Börse Systems <hanno.kl...@deutsche-boerse.com> 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/ba774af2 - PLEASE DO NOT REPLY BY MAIL.]
In my view this is not compliant. TransactTime is intended to be a current business timestamp when submitting the request, not a historical one, e.g. at the time of order creation. It does not add value to the order modifications or deletions. The Executionreport has a repeating group for such timestamps, i.e. <TrdRegTimestamps>. The field TrdRegTimestampType reflects the nature of the timestamp. SendingTime (52) is a purely technical timestamp in the header, i.e. the "envelope" of the message. It is not intended to provide business functions such as the detection of stale messages to protect the order submitter. > > Thanks Dale for the clarification. But i would like to add one more > thing here that for GTC and GTD's i have seen different time stamps in > these tags while sending Cancel/Replaces or Cancel Requests. 52 > contained the current time and 60 had the time at which the original > order was made. > > I just wanted to check that whether this is complaint to fix protocol. > > Thanks, HAMMAD MALIK MIXIT Inc [You can unsubscribe from this discussion group by sending a message to mailto:unsubscribe+100932...@fixprotocol.org] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to fix-protocol@googlegroups.com To unsubscribe from this group, send email to fix-protocol+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
