|
ECNs, Exchanges
< Previous Next >
re: Suspension
James Michuda / OptiMark Technologies, Inc.
19 May 1998 1:41PM ETI know we've talked about this before, but wouldn't it be better to add another OrdStatus (say, Unsuspend) so that anyone explicitly wanting to reactivate an order would need to specify the instruction? I think it's potentially dangerous to implement a method where the absence of one thing implies another (i.e. reactivating an order by sending a cancel/replace w/o the suspend instruction).
> > > Does anyone have suggestions or ideas, or even better, already support this via FIX? I am not so sure that '39=9' (OrdStatus Suspended) means the same thing as in the case of an ECN...
>
> It's currently supported through the Suspend
> order instruction. You would send this on a
> cancel/replace. To reactivate, you would send
> another cancel/replace w/o the suspend instruction.
>
> An execution with OrdStatus == Suspended means the
> order has been suspended(as you suggest).
>
> > >
> > > Suspend orders message should allow firms to suspend orders for the entire firm, a security or specific user or group of users.
>
> There is currently no support for this in the spec
> although things like suspension and cancel for a
> SenderCompID would be useful and has been discussed in the past for inclusion in a future rev.
>
> >
>
re: Suspension Cromwell Coulson / National Quotation Bureau, LLC 19 May 1998 12:35PM ET re: Suspension John Armstrong / Morgan Stanley Dean Witter 19 May 1998 12:45PM ET re: Suspension
James Michuda / OptiMark Technologies, Inc. 19 May 1998 1:41PM ET re: Suspension Ryan Pierce / Townsend Analytics Ltd. / Archipelago LLC 19 May 1998 2:30PM ET re: Suspension Ryan Pierce / Townsend Analytics Ltd. / Archipelago LLC 19 May 1998 3:43PM ET re: Suspension John Armstrong / Morgan Stanley Dean Witter 19 May 1998 4:17PM ET re: Suspension James Michuda / OptiMark Technologies, Inc. 19 May 1998 2:55PM ET re: Suspension James Michuda / OptiMark Technologies, Inc. 19 May 1998 3:03PM ET
|
