[This message was posted by Gustav OKeiff of T-Rex Trader <[email protected]> to the "5.0 Feedback" discussion forum at http://fixprotocol.org/discuss/47. You can reply to it on-line at http://fixprotocol.org/discuss/read/01154804 - PLEASE DO NOT REPLY BY MAIL.]
Thank You! ,...Gustav > OrdStatus (39) would typically always be "New" for an order that has > been validated and accepted by the receiver. If a stop order or an order > with a more complex trigger is provided then the additional field > WorkingIndicator (636) can be used to convey that the trigger condition > has not been met and the order is not active yet. A later > ExecutionReport with ExecType (150) value "L" can be used to explicitly > convey the activation. > > > I am testing an app using another company’s simulator - ther > > simulator is not very good. > > > > What is the OrderStatus (or other pertinent field values) retuned in > > the ExecutionReport after submitting a Stop, Limit or StopLimit? [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 -~----------~----~----~----~------~----~------~--~---
