Newbie, duplicate messages

, ,
1

Imported from previous forum

2

I am just starting out with a fix app implementation project and have very basic knowledge of how fix and our fix engine works.

We are using a 4.1 compliant fix engine.

our application upon restart any time throughout the day, will send all of the execution reports for that day to our fix engine which will subsequently forward to fix client. After restart, it will continue to send any new execution reports.

Wondering what happens to messages send to the client already before our appliation was restarted?

is the fix client responsible for checking duplicate messages or do we need to build the smarts into our apps to only send execution reports that have not been send to the fix engine?

or

Do I need to flag all messages poss-dup inorder for the client to check the message for repeats?

help.
j.

3

[ original email was from Daniel Fry - daniel@javtech.com ]
The way you would indicate that your ExecutionReports are being resent is with the PossResend flag (tag 97) which is for specifying an application-level resend. The client should be checking for the PossResend flag, and then inspecting the OrderID and ExecID to determine if it has already received the ExecutionReport.

The PossDup flag (tag 43) is reserved for session-level resends and should not be used in this case.

for more info you can refer to the "Possible Resends" portion of the FIX MESSAGE FORMAT AND DELIVERY section of the FIX 4.1 spec (page 7)

>
> I am just starting out with a fix app implementation project and have very basic knowledge of how fix and our fix engine works.
>
> We are using a 4.1 compliant fix engine.
>
> our application upon restart any time throughout the day, will send all of the execution reports for that day to our fix engine which will subsequently forward to fix client. After restart, it will continue to send any new execution reports.
>
> Wondering what happens to messages send to the client already before our appliation was restarted?
>
> is the fix client responsible for checking duplicate messages or do we need to build the smarts into our apps to only send execution reports that have not been send to the fix engine?
>
> or
>
> Do I need to flag all messages poss-dup inorder for the client to check the message for repeats?
>
>
> help.
> j.
>