SeqReset-Reset message

, ,
1

Imported from previous forum

2

[ original email was from Duilio Gamba - ]

Do SeqReset-Reset messages that are sent in reply to a resend request have the PossDup flag set ? I ask because one section of the FIX4.0 specification states that:

  • “all messages created as the result of a resend request will contain the PossDupFlag set to ‘Y’”

whereas in another section it says that we must:

  • "detect inadvertently retransmitted administrative messages (PossDup flag set indicating a resend)"

and that

  • "the business/application processing of these messages should be skipped"

    Is the way to handle SeqReset-Reset messages to bypass PossDup and Sequence checks and simply use the new Sequence Number (provided of course that it does not attempt to reduce the next expected incoming sequence number) ?

Thanks

3

[ original email was from Ryan Pierce - rpierce@taltrade.com ]
Sequence checing is supposed to be ignored in the case of a SeqReset-Reset. Hence Poss Dupe doesn’t gain you any advantage. And since the spec says that Poss Dupe admins are errors and supposed to be discarded, I’d be inclined not to make SeqReset-Reset’s Poss Dupe.

I also wouldn’t be inclined to generate them in response to a Resend Request - it’s much friendlier to use a Gap Fill.

This made me notice a contradiction with Poss Dupe Gap Fills, which I’m going to comment on in the 4.0 Session discussion group.

Ryan Pierce
Townsend Analytics Ltd.