Logon Message Fields
| Tag | Field Name | Required | Description |
|---|---|---|---|
| 35 | MsgType | Y | A |
| 108 | HeartbeatInterval | Y | Client Heartbeat Interval (in seconds). |
The Logon message must be the first message sent by the user after the TCP connection is established. EncryptMethod is ignored (FIX level encryption is not supported).
Cboe will wait one second after a Logon message is received to ensure that no Resend Request messages are in flight from the Member. A Heartbeat message will be sent to indicate that the one second wait period has ended. Members should not send any orders prior to receiving this first Heartbeat from Cboe.
The IP Address of the user, the SenderCompId, SenderSubId and TargetCompId (defined in the Logon Message Fields table) and TargetSubId (TEST/ PROD) will be validated. If validation fails the connection will be dropped without a reject (to avoid corrupting the users sequence in the case that the user merely mistakenly connected to the wrong port).
If connection is unexpectedly broken, upon reconnection the user may receive a login reply with a sequence number greater than expected. This means that in-flight messages were missed (likely important execution reports). The user should issue a Resend Request message to retrieve the missed messages.
Similarly Cboe will issue a Resend Request message to the user for messages that it missed. The user may wish to send gap fill messages in place of new orders to avoid re-submission of potentially stale orders.
HeartbeatInterval must be specified by the user in the Logon message. This value will be clamped between 5 and 300 seconds and returned in the logon reply message. We recommend using as low a value as the reliability and latency of your telecommunications channel will allow.