TT® FIX General

Sequence Reset (4) Message

Sequence Reset (4) Message

Sequence Reset (4) Message

Purpose

Used to reset the message sequence number or gap fill

Message Direction

From TT FIX to FIX client and from FIX client to TT FIX

Tag Directory

Click the links below to navigate to the documentation for that tag.

Supported Tags

Tag # Field Name Req’d Data type Comments
Component: <Standard Header>
Y 35=4 (MsgType)
For additional information about this component group, consult the documentation.
Tag # Field Name Req’d Data type Comments
8 BeginString Y String

FIX protocol version

The tag indicates the beginning of a new message. This tag must be the first tag in the message.

You must set the value to FIX.4.2 or FIX.4.4.

9 BodyLength Y int

Message length (in characters)

The value represents number of characters in the message following this tag up to, and including, the delimiter immediately preceding Tag 10 (CheckSum). This tag must be the second field in a message.

35 MsgType Y String

Type of message contained in the message body

This tag must appear third in the list of header tags.

Possible values include:

  • 0: Heartbeat
  • 1: Test Request
  • 2: Resend Request
  • 3: Reject
  • 4: Sequence Reset
  • 5: Logout
  • 8: Execution Report
  • 9: Order Cancel Reject
  • A: Logon
  • B: News
  • c: Security Definition Request
  • D: Order Single
  • d: Security Definition
  • e: Security Status Request
  • f: Security Status
  • F: Order Cancel Request
  • G: Order Cancel Replace Request
  • H: Order Status Request
  • Q: Don't Know Trade (Inbound Drop Copy only)
  • V: Market Data Request
  • W: Market Data Snapshot Full Refresh
  • X: Market Data Incremental Refresh
  • Y: Market Data Request Reject
  • AE: Trade Capture Report
49 SenderCompID Y String

ID for the FIX client, corresponding to the RemoteCompID specified for the user in TT User Setup

56 TargetCompID Y String

TT session identity

TT FIX does not validate this field. To guarantee session persistence, the FIX client must maintain the same value of this field for the life of the session.

You can use any value in this tag to identify the TT session for the FIX client. TT FIX will return this value in tag 49 (SenderCompID) in its responses.

50 SenderSubID N String

Unique ID for the message sender

For order routing messages, this tag overrides the exchange Operator ID configured in Setup.

57 TargetSubID C String

Unique ID for the message receiver.

Condition: If the Target Sub Id field has a value for the FIX Session in Setup, you must supply that value is this tag for a Logon (A) message.

116 OnBehalfOfSubID C String

New tag for TT

Unique Trader ID

The value maps to the Alias field configured for a user in Setup.

Condition: Required when multiple users are associated with the account.

34 MsgSeqNum Y SeqNum

Message sequence number

142 SenderLocationID N string Specific message originator's location (i.e. geographic location and/or desk, trader)
43 PossDupFlag C Boolean

Whether the sequence number for this message is already used

Possible values include:

  • Y: Possible duplicate
  • N: Original transmission

Condition: Must send when a FIX client resends messages

Note: If 43=Y is present, TT will reject New Order Single (D), Order Cancel/Replace Request (G), New Order Multileg (AB), and Multileg Order Cancel/Replace (AC) messages with a Business Message Reject (j) message.

122 OrigSendingTime C UTCTimestamp

Original time of message transmission, when transmitting orders as the result of a resend request

Always expressed in UTC.

Condition: Required for resent messages

52 SendingTime Y UTCTimestamp

Time, in UTC, the message was sent.

Tag # Field name Req’d Data type Comments
8 BeginString Y String

FIX protocol version

The tag indicates the beginning of a new message. This tag is always the first tag in the message.

The value is either FIX.4.2 or FIX.4.4.

9 BodyLength Y int

Message length (in characters)

The value represents number of characters in the message following this tag up to, and including, the delimiter immediately preceding Tag 10 (CheckSum). This tag must be the second field in a message.

35 MsgType Y String

Type of message contained in the message body

This tag must appear third in the list of header tags.

Possible values include:

  • 0: Heartbeat
  • 1: Test Request
  • 2: Resend Request
  • 3: Reject
  • 4: Sequence Reset
  • 5: Logout
  • 8: Execution Report
  • 9: Order Cancel Reject
  • A: Logon
  • B: News
  • c: Security Definition Request
  • D: Order Single
  • d: Security Definition
  • e: Security Status Request
  • f: Security Status
  • F: Order Cancel Request
  • G: Order Cancel Replace Request
  • H: Order Status Request
  • Q: Don't Know Trade (Inbound Drop Copy only)
  • V: Market Data Request
  • W: Market Data Snapshot Full Refresh
  • X: Market Data Incremental Refresh
  • Y: Market Data Request Reject
  • AE: Trade Capture Report
49 SenderCompID Y String

ID of the FIX session

The value will be the same value the FIX client sends in tag 56 (TargetCompID) in its requests to TT FIX.

56 TargetCompID Y String

FIX client ID, corresponding to the SenderCompID specified for the user in TT User Setup

The value is the same as sent in tag 49 (SenderCompID) in FIX client requests.

50 SenderSubID C String

Unique ID for the message sender

For CME, the value corresponds to the Operator ID.

Condition: Sent if TT User Setup specifies an exchange operator ID

142 SenderLocationID N string Specific message originator's location (i.e. geographic location and/or desk, trader)
116 OnBehalfOfSubID N Data type: String

New tag for TT

Unique Trader ID (can also be provided in Tag 50 (SenderSubID))

The value maps to the Alias field configured for a user in Setup.

129 DeliverToSubID C String

Value of Tag 116 (OnBehalfOfSubID) in the FIX client request.

Condition: Sent in Execution Report (8) and Order Cancel Reject (9) messages.

34 MsgSeqNum Y SeqNum

Message sequence number.

43 PossDupFlag C Boolean

Whether the sequence number for this message is already used

Possible values include:

  • Y: Possible duplicate
  • N: Original transmission

Condition: Sent when TT FIX resends messages

97 PossResend C Boolean

Whether the message might contain information that has been sent under another sequence numbe

Possible values include:

  • Y: Possible resend
  • N: Original transmission

Condition: Sent when TT FIX restarts after encountering a corrupt FIX message cache, and only until it completes the initial download.

122 OrigSendingTime C UTCTimestamp

Original time of message transmission, when transmitting orders as the result of a resend request

Always expressed in UTC.

Condition: Sent when TT FIX resends a message

52

SendingTime

Y UTCTimestamp

Time, in UTC, the message was sent.

123 GapFillFlag N

Boolean

Indicates that the Sequence Reset message replaces missing administrative or application messages

Valid values include:

  • Y: Gap Fill message, Tag 34 (MsgSeqNum) field is valid
  • N: Sequence Reset, ignore Tag 34 (MsgSeqNum)

Default: N

36 NewSeqNo Y SeqNum

New sequence number

Component: <Standard Trailer>
Y For additional information about this component group, consult the full documentation.
Tag # Field Name Req’d Data type Comments
10 Checksum Y String

Unencrypted three-character checksum

This tag must always be the last field in a message (i.e. it serves, with the trailing <SOH>, as the end-of-message delimiter).

Message Notes

The Sequence Reset (4) message is used to reset the message sequence number when the FIX client and TT FIX message sequence numbers do not match. If the message omits Tag 123 (GapFillFlag), the value of Tag 36 (NewSeqNo) indicates the new starting sequence number.

If a FIX client or TT FIX needs to skip messages that would be included in a resend request, it sets Tag 123 (GapFillFlag) to Y, and the value of Tag 36 (NewSeqNo) represents the sequence number of the next message to be transmitted.

Note: Non-gap fill resets should be used only to when the sequence number differences cannot be resolved.

For more information about sequence resets and gap fills, refer to the FIX specification.

Related Information

Logon (A)
Resend Request (2)