Imported from previous forum
Hi,
I need to know what should happen in below case.
Day 1 11=1 52= day 1 + 10:00:00
Day 2 11=1 43=Y 122=day 1 + 10:00:00 52=day2 + 11:00:00(this is a dup of order on day 1).
Day 2 11=1 52=day 2 + 12:00:00 --> at this step, should this order get accepted or rejected?
So, the question is - if you already have processed a dup order of earlier day, should you accept new order with same clorderid, sendingTime and source.
Thanks in advance.
Hi,
I need to know what should happen in below case.
Day 1 11=1 52= day 1 + 10:00:00
Day 2 11=1 43=Y 122=day 1 + 10:00:00 52=day2 + 11:00:00(this is a dup of order on day 1).Day 2 11=1 52=day 2 + 12:00:00 → at this step, should this order get accepted or rejected?
So, the question is - if you already have processed a dup order of earlier day, should you accept new order with same clorderid, sendingTime and source.
Thanks in advance.
Hi,
Yes the order get accepted in below scenario
I observed scenario which works as below
Order entered on day1(sure will be GTC/GTD) with Tag11(as 1) on following day(day2) Execution report will be returned as unsolicited/restated state so tag 11 will have the value of Tag37.
On Day1:
35=D,11=1,59=1
35=8,11=1,59=1,…,37=X,39=0,150=0
On Day2: after logon
35=8,11=X(same as Tag 37),377=N,37=X,150=D
So new order on day 2 can be entered with same value of tag11(as 1)
On Day2: 35=D,11=1,…(Order should get accepted)
Hope it will be some kind of useful info
Others please correct me if my answer is misleading/incorrect
Cheers,
Ashwaq
Ashwaq,
Sorry to tell you that but I don’t understand your scenario and it doesn’t seem to be FIX compliant. Feel free to clarify.
Siddharth,
Your scenario seems to be the consequence of a synchronization issue between counterparts. It should never happen (in a good world) but as we can’t exclude an unexpected event, a good pratice would be to detect this issue at business level and to ignore resent messages…
Hi,
I need to know what should happen in below case.
Day 1 11=1 52= day 1 + 10:00:00
Day 2 11=1 43=Y 122=day 1 + 10:00:00 52=day2 + 11:00:00(this is a dup of order on day 1).Day 2 11=1 52=day 2 + 12:00:00 → at this step, should this order get accepted or rejected?
So, the question is - if you already have processed a dup order of earlier day, should you accept new order with same clorderid, sendingTime and source.
Thanks in advance.
Hi,
Yes the order get accepted in below scenario
I observed scenario which works as below
Order entered on day1(sure will be GTC/GTD) with Tag11(as 1) on following day(day2) Execution report will be returned as unsolicited/restated state so tag 11 will have the value of Tag37.
On Day1:
35=D,11=1,59=1
35=8,11=1,59=1,…,37=X,39=0,150=0
On Day2: after logon
35=8,11=X(same as Tag 37),377=N,37=X,150=DSo new order on day 2 can be entered with same value of tag11(as 1)
On Day2: 35=D,11=1,…(Order should get accepted)
Hope it will be some kind of useful info
Others please correct me if my answer is misleading/incorrect
Cheers,
Ashwaq
Usage of PossDupFlag (43) requires to use the same MsgSeqNum, i.e. you need to be in the same FIX session. Are you sure that you are assuming a multi-day FIX session in your example below? This is fairly rare but certainly possible. Your usage of the terms “Day 1” and “Day 2” seems to imply otherwise. Also, PossDupFlag is used when retransmitting the same application data. There is also PossResend (97) where the same application data is sent under a different sequence number and the recipient has to determine whether it is a duplicate from looking at various fields.
Another aspect is the fact that it is possible to re-use the same ClOrdID in the same session, for example if a request was rejected. Depending on the ClOrdID scope of the receiver there might be more cases, e.g. when an order has reached a terminal state (filled, cancelled, expired). However, it is never really advisable to do so in the interest of the submitter. It can also be quite a burden for the recipient to keep all ClOrdID values of a multi-day session and enforce uniqueness, certainly for an exchange environment. One would recommend to use the date as part of ClOrdID so that you have “Day1-1” and “Day2-2” as actual values. It should never be an issue to re-use ClOrdID values from one session to the next but is also not recommended as soon as GTC or GTD orders are supported by the recipient.
Hi,
I need to know what should happen in below case.
Day 1 11=1 52= day 1 + 10:00:00
Day 2 11=1 43=Y 122=day 1 + 10:00:00 52=day2 + 11:00:00(this is a dup of order on day 1).Day 2 11=1 52=day 2 + 12:00:00 → at this step, should this order get accepted or rejected?
So, the question is - if you already have processed a dup order of earlier day, should you accept new order with same clorderid, sendingTime and source.
Thanks in advance.