FIX Trading Community

 

 Remember me

Register  |   Lost password?

FIX Semantics

Discussions > FIX Semantics > Stop/Limit ExecutionReport

Stop/Limit ExecutionReport

Complete message thread from old site

Gustav Okeiff
1762 days ago,(2009/06/26)

I am testing an app using another company’s simulator - ther simulator is not very good.

What is the OrderStatus (or other pertinent field values) retuned in the ExecutionReport after submitting a Stop, Limit or StopLimit?

Hanno Klein
1760 days ago,(2009/06/29)

OrdStatus (39) would typically always be "New" for an order that has been validated and accepted by the receiver. If a stop order or an order with a more complex trigger is provided then the additional field WorkingIndicator (636) can be used to convey that the trigger condition has not been met and the order is not active yet. A later ExecutionReport with ExecType (150) value "L" can be used to explicitly convey the activation.

> I am testing an app using another company’s simulator - ther simulator
> is not very good.
>
> What is the OrderStatus (or other pertinent field values) retuned in the
> ExecutionReport after submitting a Stop, Limit or StopLimit?

Gustav Okeiff
1759 days ago,(2009/06/29)

Thank You!

,...Gustav

> OrdStatus (39) would typically always be "New" for an order that has
> been validated and accepted by the receiver. If a stop order or an order
> with a more complex trigger is provided then the additional field
> WorkingIndicator (636) can be used to convey that the trigger condition
> has not been met and the order is not active yet. A later
> ExecutionReport with ExecType (150) value "L" can be used to explicitly
> convey the activation.
>
> > I am testing an app using another company’s simulator - ther
> > simulator is not very good.
> >
> > What is the OrderStatus (or other pertinent field values) retuned in
> > the ExecutionReport after submitting a Stop, Limit or StopLimit?