...
After sending a Logout (tag 35-MsgType=5) message, the client system should wait for a Logout Confirmation (tag 35-MsgType=5) message before closing the socket connection. Working orders are not affected by a client logout and will continue to be eligible for trades. Any message activity on working orders sent while the client is logged out will be stored and may be retreived retrieved by the client at next logon.
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
  |
Logout Where Sequence Number Is Lower Than Expected
If the client system sends a iLink 2 Logout message with tag 34-MsgSeqNum containing a lower sequence number than CME Globex is expecting, CME Globex automatically logs out the client system.
The following diagram illustrates this message flow.
...
Logout Where Sequence Number Is Higher Than Expected
The following diagram illustrates the message flow for a Logout scenario where the client's outbound sequence number is higher than what CME Globex is expecting.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
  |
In the diagram, the client system sends a iLink 2 Logout message which contains tag 34-MsgSeqNum=150. CME Globex detects a sequence gap.
CME Globex sends a iLink 2 Resend Request message with tag 369-LastMsgSeqNumProcessed=146 contain the value of the last message received.
...
Now the messages are in sequence, CME Gobex Globex sends a Logout Confirmation (tag 35-MsgType=5) with tag 369-LastMsgSeqNumProcessed=150 which matches the client system Logout (tag 35-MsgType=5) message.