...
- A newly detected message sequence gap must be distinguished from a continuation of a gap and a new gap versus a duplicate Resend Request must be issued accordingly.
- When a message sequence number gap is newly detected (the sequence number received is greater than expected), issue a new Resend Request on its own sequence number. The requested sequence number range must be the next expected sequence number to infinity.
- For each subsequent message that constitutes a continuation of the gap, issue a duplicate Resend Request. This message must be sent on the same message sequence number of the original Resend Request, tag 43-PossDupFlag must be set to 'Y' and tag 122-OrigSendingTime must not be sent.
- The FIX Engine should detect receipt of the first message sent in response to a previous Resend Request and discontinue issuing the Resend Requests marked PossDup.
- The FIX Engine should issue a new Resend Request, if needed, only after the receipt of the counterparty's response has been completed.
- For resend requests from the Client System to CME Globex, both basic and enhanced resend logic are supported.
| Note | title | Warning
|---|
| Info |
Basic FIX resend logic, while currently support will be phased out. ALL CLIENT SYSTEMS WILL BE REQUIRED TO MIGRATE TO ENHANCED CME GLOBEX RESEND LOGIC. For new system development, it is imperative that enhanced CME Globex resend logic be implemented. |
Basic Resend Logic from Client System to CME Globex
A description of basic FIX resend request logic is available at http://www.fixprotocol.org/specifications/.
...