|
ECNs, Exchanges
< Previous Next >
re: Suspension
James Michuda / OptiMark Technologies, Inc.
19 May 1998 2:55PM ET> > I 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).
>
> The client never specifies the OrdStatus field. OrdStatus is something the Exchange/ECN/broker sets in an Execution message.
>
> Are you sure you don't mean adding an Unsuspend ExecInst for the customer to specify?
>
Yes, this is what I meant. I cut and pasted without checking for accuracy. Sorry.
> Each of the ExecInst values is generally a boolean. An order is All or None or it isn't. It is Not Held or it isn't, Similarly, it is Suspended or it isn't. I see no reason to create an Unsuspend ExecInst unless we create an Un-All or None, an Un-Not Held, etc.
>
>
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
|
