[This message was posted by Javier Ibarra of Mexican Stock Exchange <[email protected]> to the "4.4 Changes" discussion forum at http://fixprotocol.org/discuss/17. You can reply to it on-line at http://fixprotocol.org/discuss/read/382c82e8 - PLEASE DO NOT REPLY BY MAIL.]
Hanno, Ok, that make sense, thanks a lot. Regards > Javier, > I assume you are still talking about public data, not private trade > information sent directly to the counterparties of the trade. If you need the > complete transactional capabilities for trades (add, modify, delete) then it > is better to use the MDIncrementalRefresh message to convey trades. There you > have MDUpdateAction which covers what you need. If you need to use > MDSnapshotFullRefresh then you can implement a modify by sending a cancel > (277=0) followed by another trade. 277 is not intended for transactional > semantics, it merely qualifies the trade in more detail. > Regards, > Hanno. > > > Hello Hanno, > > > > We are interested in that behavior, by using tag 277, to cancel and modify > > trades. I got the picture for cancelations, but I'm not sure about the > > specific value to use if we want to send a trade correction/modifcation. > > Could you help me? > > > > 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.
