Amendments on OMS queued orders

Good day,

assume receipt of a queued order was confirmed by OMS using a “New” Exection Report sent back to the client.
Also assume, ExDestination Market is still closed (or the brokers still in bed) and a “Pending New” stating the “Queued” Status would not allow the client to amend the queued order. That is FIX convention.
And I really offer amendments including cancellations to the order queued in my OMS.
But I also want to signal the buy side that the order was routed
1.) STP to the exchange at the opening or
2.) someone takes care of it (the broker checks the inbound blotter)
What is the best way to achieve the amendment in the OMS and the status change of the order when it was taken off the queue nd released ?
Both cases may be covered by a different “solution” if any …

There have been suggestions in the forum before:
a.) Execution Report New with WorkingIndicator (tag 636) = “Y” does not fit as it is rather liaised with contingent orders and triggering.
b.) Restatement Reasons in a 150=D Execution Report unfortunantely do not cover our case.

Now how about this one:
ExecutionReport 150=N, probably underlined by 1796=N ? “N” is for “Released”. Was that the orignal purpose on status “N” ? I am afraid it is rather the opposite of “M”-Locked :slight_smile:

Thank you for your consideration and comments indeed!

Kind Regards
Uli

@111s you are right that ExecType(150) = “N” (released) is the counterpart of “M” (locked). It was added with EP131 for a US options exchange when orders might receive a better price at an away market. The market maker gets the order locked to him and has to try to get it filled at the better price at the away market. If unsuccessful, he will simply release the order (or remaining parts of it) into the home market again.

What is the basis for the FIX convention that an order in “pending new” state cannot be amended or cancelled? Anything in the current spec (https://www.fixtrading.org/online-specification/)? If the counterparty is able to accept an order for queuing, it should also be able to at least cancel the order again. Amendments are then just cancel+new if they are not supported natively.