Page tree
Skip to end of metadata
Go to start of metadata

CME Globex issues the Session Level Reject (tag 35-MsgType=3) message when the inbound (client sys­tem 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:

  • Required tag missing
  • Undefined tag included
  • Tag specified without a value
  • Value is incorrect (out of range or invalid) for this tag
  • Incorrect data format for value
  • CompID problem
  • SendingTime accuracy problem
  • CME Globex Credit Controls credit limit violation
See Session Layer Validation Conditions for more information.

The following diagram illustrates an unsuccessful message transmission and Session Level Reject (tag 35-MsgType=3) scenario.

In this diagram the client system sent a Logon message without tag 35-MsgType. As a result, CME Globex issued a Session Level Reject (tag 35-MsgType=3) with a descriptive reason in tag 58-Text.

If a client system submits a message that cannot be parsed or fails a data integrity check, iLink 2.X will not send a response message. In such a scenario, when the next valid message is processed, iLink 2.X 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.


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.

  • No labels