Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note
Drop Copy logon must follow the CME Globex Secure API Logon procedure. Once securely logged on, the following information is applicable to the Drop Copy session.

Client systems use the  Logon (tag 35-MsgType=A) message for authentication with Drop Copy. There are three Logon scenarios:

...

If authentication is successful, a Logon (35=A) message is sent with a Fault Tolerance Indicator of  'N'.

...

  1. While the client system is logged out, Drop Copy stores any messages to be sent to the client system.
  2. As a result, the client system may receive a Logon (35=A) message with a sequence number higher than expected due to the fact that Drop Copy processed those stored messages prior to the Mid-Week Logon message and incremented its outbound sequence number accordingly.
  3. The client system submits a  Resend Request (35=2) message for messages stored while the client system was logged out.

...

  1. The client system successfully logged on Tuesday morning and submitted New Order (35=D)  messages.
  2. The client system logged out. While the client system is logged out, the orders remain active and any corresponding Execution Reports are generated. Drop Copy processes these Execution Reports and increments its outbound sequence number while the client system is logged out.
  3. The client system logs in on Wednesday morning. When the client system receives the Logon Confirmation (tag 35-MsgType=A) message, the client system detects that the sequence number of the Logon Confirmation (tag 35-MsgType=A) message is higher than expected. The client application follows up with a Resend Request (tag 35-MsgType=2) message and retrieves unsent messages that were generated while the client system was logged out.

...