[This message was posted by eric kou of Yuanta Security <[email protected]> to the "4.2 Changes" discussion forum at http://fixprotocol.org/discuss/5. You can reply to it on-line at http://fixprotocol.org/discuss/read/d8361aca - PLEASE DO NOT REPLY BY MAIL.]
The key is to have 20 = cancellation or correction. 151 is populated with "Restated", "rejected" or "cancelled" and 39 will be filled with what the order status are at the time the message is generated. > Hello Kou, > > > Tag 20 and tag 38 should also be taken into account in your cases. > > Ok, no problem with these tags when busting an execution. > > > > See D19, D20 and D21 for examples on unsolicited cancel, replace and > > and reduction. > > Ok, but these examples don't have "busted executions". They appear in > D34 and D35, where tag 150 (ExecType) seems to follow the same value of > tag 39 (OrderStatus). > > One of our FIX partners told me that ExecType would be *aways* 150=4 > when the Execution Report is busting an execution -- but I'm not sure > about that. > > Could anyone help? [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 -~----------~----~----~----~------~----~------~--~---
