[This message was posted by Mike Chan of NIL <[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/c3638fb1 - PLEASE DO NOT REPLY BY MAIL.]
Hi, I am building a FIX application where new order and subsequent order amendment(s) will be auto-accepted first before market opens. And when the market opens, the system will route only the new order (with order attributes following the amendment(s)) to the exchange. By auto-accept, we will return NEW execution report (150=0) to the buy-side. For any amendment to the order before we route the order out to the exchange, we will also auto-accept and return REPLACE execution report (150=5). After the order has been accepted into the exchange, the system won't further acknowledge the buy-side I am stucked by the case where the order is rejected by the exchange. Since the order has been auto-accepted (execution report of 150=0 and 150=5 are sent before to the buy-side), if the order is actually rejected by the exchange, how should I update the buy-side? Is unsolicited cancel execution report (150=4) a good idea to reject in this case? or should we still send reject execution report (150=8), even the order has been replaced before? I understand that reject execution report can still be replied after new execution report is provided earlier. However, I also note that by the order Status change matrix specified in FIX 4.2, ordStatus transition from REPLACE(5) to REJECTED(8) is not a valid transition. In advance, Thanks very much for your expert opinion ! [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.
