Re: [Quickfix-users] New Order Single
Brought to you by:
orenmnero
From: Vincent P. <vpr...@ph...> - 2008-05-21 02:31:11
|
On May 20, 2008, at 2:58 PM, John Haldi wrote: > > If I understand your question, the answer is "it depends on the > other side's protocol implementation". > > For example, when I send a NewOrderSingle to ARCA, I initially get > an ExecutionReport back from ARCA with OrdStatus=A ("Pending New") > which means they got my order but it hasn't gone "live" in their > trading engine. Almost immediately afterwards I get another > ExecutionReport with OrdStatus=0 ("New") meaning my order is now > live. Every now and then I get OrdStatus=A and then I get > OrdStatus=8 ("Rejected"), which means 1) the FIX group got my > message, but 2) it was rejected for some reason (usually because > the stock is halted). > > As another example, one of the brokers we work with has their > system configured so that I don't get the OrdStatus=A messages. I > only get a notification once my order is rejected or it goes live. > > And then we have another broker who doesn't send anything back to > me when an order goes live. They only send me notifications when I > get filled, partially filled, or I cancel the order. > > It really just depends on what the other system is doing. If you > are building a test broker app, I would recommend that you try to > implement the more verbose scenario as described in the first example. We're building a trade match system. My test client is designed to make sure the match server works like it should. I used a number of STL containers to store the data sent to the match server, so it can make sure the responses from the match server are correct. -- Vincent |