Error handling for OrderStatusRequest

, ,
1

Imported from previous forum

2

If I send an OrderStatusRequest(H) (FIX 5.0 SP1) containing a ClOrdID that does not exist or refers to an order that I have not permission to see, what is the expected behavior of the FIX gateway?

Which of these possible strategies should we consider:

  1. Ignore the request

  2. Return an ExecutionReport having ExecType=I (Status Request)

  3. Return an ExecutionReport having ExecType=8 (Rejected)

I have not been able to find any guidelines in the FIX spec.

So what do you think?

/Erik

3

[ original email was from Harish Kamaley - harish.kamaley@wipro.com ]

Return an Execution Report 35=8 with following tags
150=I(Status)
39=8(Reject)
103=5(Unknown Order)
17=0
38=0
14=0
151=0
6=0

Please refer: fix-43_VOL-4_with_Errata_20020920.doc page no. 69, Order State Change Matrices, D29

Regards
Harish

If I send an OrderStatusRequest(H) (FIX 5.0 SP1) containing a ClOrdID
that does not exist or refers to an order that I have not permission to
see, what is the expected behavior of the FIX gateway?

Which of these possible strategies should we consider:

  1. Ignore the request

  2. Return an ExecutionReport having ExecType=I (Status Request)

  3. Return an ExecutionReport having ExecType=8 (Rejected)

I have not been able to find any guidelines in the FIX spec.

So what do you think?

/Erik

4

Thanks a lot. For FIX 5.0 SP1, the same info can be found in the FIX-5.0_SP1_VOL-4.doc document at page 82.

The spec is a bit contradictionary when it describes the purpose of OrdRejReason (103). This is what the spec above says at page 18:

103, OrdRejReason, For optional use with ExecType = 8 (Rejected).

Shouldn’t this say?

For optional use with ExecType = 8 (Rejected) or ExecType = I (Status)

/Erik

Return an Execution Report 35=8 with following tags 150=I(Status)
39=8(Reject) 103=5(Unknown Order) 17=0 38=0 14=0 151=0 6=0

Please refer: fix-43_VOL-4_with_Errata_20020920.doc page no. 69, Order
State Change Matrices, D29

Regards Harish

If I send an OrderStatusRequest(H) (FIX 5.0 SP1) containing a ClOrdID
that does not exist or refers to an order that I have not permission
to see, what is the expected behavior of the FIX gateway?

Which of these possible strategies should we consider:

  1. Ignore the request

  2. Return an ExecutionReport having ExecType=I (Status Request)

  3. Return an ExecutionReport having ExecType=8 (Rejected)

I have not been able to find any guidelines in the FIX spec.

So what do you think?

/Erik

5

[ original email was from Bivas Mishra - bivas.mishra@wipro.com ]
Hi,

Unless the specs need a relook for usage of Tag 103,

the alternative way to respond could be thus:

(150)ExecType=(I)Status
Ignore populating (103)OrdrejReason and provide a text in Tag 58 stating the reason that clOrdId not found.

Regards.

Thanks a lot. For FIX 5.0 SP1, the same info can be found in the FIX-5.0_SP1_VOL-
4.doc document at page 82.

The spec is a bit contradictionary when it describes the purpose of
OrdRejReason (103). This is what the spec above says at page 18:

103, OrdRejReason, For optional use with ExecType = 8 (Rejected).

Shouldn’t this say?

For optional use with ExecType = 8 (Rejected) or ExecType = I (Status)

/Erik

Return an Execution Report 35=8 with following tags 150=I(Status)
39=8(Reject) 103=5(Unknown Order) 17=0 38=0 14=0 151=0 6=0

Please refer: fix-43_VOL-4_with_Errata_20020920.doc page no. 69, Order
State Change Matrices, D29

Regards Harish

If I send an OrderStatusRequest(H) (FIX 5.0 SP1) containing a
ClOrdID that does not exist or refers to an order that I have not
permission to see, what is the expected behavior of the FIX gateway?

Which of these possible strategies should we consider:

  1. Ignore the request

  2. Return an ExecutionReport having ExecType=I (Status Request)

  3. Return an ExecutionReport having ExecType=8 (Rejected)

I have not been able to find any guidelines in the FIX spec.

So what do you think?

/Erik