Versions Compared

Version Old Version 1 New Version Current
Changes made by

Space Sync for Confluence

Space Sync for Confluence

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Info

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.

Panel
borderColor#FFFFFF
bgColor#FFFFFF
borderstylenone
Image Modified

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 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.

Note
title

Warning

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.

...