Unsolicited Cancel/Replace - Tag41

, ,
1

Imported from previous forum

2

[ original email was from Shakir Kagzi - shakir.kagzi@ftindia.com ]
Hi,

With respect to sending Unsolicited Cancel/Replace response from our sell side OMS (FIX 4.2), I have some questions:

  1. Should Tag41 be sent in the response?
  2. If yes, then what should be the value in Tag41?
  3. What should be the value in Tag11?

Thanks

3

Do you mean an unsolicited ExecutionReport informing about the change/cancellation of an order? That would be ExecType=Restated with ExecRestatementReason explaining what was changed (or cancelled).

The spec foresees tag 41 (OrigClOrdID) to echo the ClOrdID of a Cancel[/Replace] request (the last accepted ClOrdID value). It is conditionally required for a solicited response to a cancel or replace request, so you can use tag 11 (ClOrdID) or tag 37 (OrderID) to tell the receiver which order is being restated.

The order identification value does not change for fills (and restatements). A new ClOrdID is needed for order changes as it also serves as a message identifier matching request and response in these cases. Both fields (ClOrdID and OrigClOrdID) are only needed when sending back the previous as well as the new order identification value of the client.

Hope this helps,
Hanno.

Hi,

With respect to sending Unsolicited Cancel/Replace response from our
sell side OMS (FIX 4.2), I have some questions:

  1. Should Tag41 be sent in the response?
  2. If yes, then what should be the value in Tag41?
  3. What should be the value in Tag11?

Thanks