[This message was posted by Hanno Klein of Deutsche Börse Systems <[email protected]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/207b1924 - PLEASE DO NOT REPLY BY MAIL.]
The broker will not wait to see if further requests come in and process each request as it comes. Unless there are rejections or fills in between, the immediacy of Cancel/Replace requests should not matter. However, if the first Cancel/Replace request is rejected, then Y does not become a valid ClOrdID. Equally, if 1000 are filled prior to the first Cancel/Replace request (or 900 prior to the second), then the qty cannot be reduced to the desired value. Have a look at the spec Volume 4, message scenarios C and D, starting on page 52, specifically D.2 starting on page 61. Hope you find enough answers there. Details can get quite complex. > Hi, > > FIX4.4 I've got the following use case: > > client: NewOrder(X), qty=1000 client: OrderCancelReplaceRequest(Y,X), > qty=900 client: OrderCancelReplaceRequest(Z,Y), qty=800 broker: ?????? > > Q1: does client send the correct chain of requests? > Q2: if Q1 is "yes" then what are the possible responses from the server? > > Thanks in advance. [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.
