CME Globex issues the Session Level Reject (tag 35-MsgType=3) message when the inbound (client system to CME Globex) message fails to pass a CME Globex session-level validation check. These messages have invalid basic data (e.g., CheckSum and BodyLength), but successfully passed de-encryption validations. The reason a message is rejected is described in tag 58-Text field.
Reasons that a Session Level Reject (tag 35-MsgType=3) message is sent include:
...
If a client system submits a message that cannot be parsed or fails a data integrity check, iLink 2 will not send a response message. In such a scenario, when the next valid message is processed, iLink 2 will detect a sequence gap and generate a Resend Request (tag 35-MsgType=2) message. If the client system resends the corrected message and it is valid, normal processing will continue.
| Warningnote | ||
|---|---|---|
| ||
If the previously invalid message remains in error and the client system continues to send the message without making the required corrections, the Resend Request (tag 35-MsgType=2) message process will loop indefinitely. Clients must detect this condition and perform the corrective processing to avoid it. |
...