TASRestatementUSFuturesV1
| Field Name | Offset | Length | Data Type | Description |
|---|---|---|---|---|
| StartOfMessage | 0 | 2 | Binary |
B0 E3 (58288) |
| MessageLength | 2 | 2 | Binary |
72 00 (114) |
| MessageType | 4 | 2 | Binary |
E9 05 (1513) |
| MatchingUnit | 6 | 1 | Binary | Matching Unit which created this message. |
| Reserved | 7 | 1 | Binary | Unspecified |
| SequenceNumber | 8 | 4 | Binary | The sequence number for this message. Distinct per Matching Unit |
| TransactionTime | 12 | 8 | DateTime | The time the event occurred in the CFE Matching Engine (not the time the message was sent). |
| ClOrdId | 20 | 20 | Text | The order being restated |
| ClearingFirm | 40 | 4 | Alpha |
|
| ExecId | 44 | 8 | Binary |
|
| Side | 52 | 1 | Text |
|
| Price | 53 | 8 | BinaryPrice | Limit price of the order. |
| Symbol | 61 | 8 | Alphanumeric | CFE native identifier of the instrument |
| MaturityDate | 69 | 4 | Date | Maturity date of the instrument |
| LastShares | 73 | 4 | Binary | Executed contracts quantity. |
| LastPx | 77 | 8 | BinaryPrice | Price of this fill. Note the use of Price type to represent positive and negative prices, which can occur with spread instruments. |
| FeeCode | 85 | 2 | Alphanumeric | Indicates fee associated with an execution. Fee codes are published in the pricing schedule. New fee codes may be sent with little or no notice. TPHs are encouraged to code their systems to accept unknown fee codes. |
| TradeDate | 87 | 4 | Date |
|
| ClearingPrice | 91 | 8 | BinaryPrice | Price as sent to clearing after applying post-close conversions to the original LastPx value. |
| ClearingSymbol | 99 | 8 | Alphanumeric | Symbol as sent to clearing; after applying post-close conversions to the original Symbol. |
| MultilegReportingType | 107 | 1 | Text |
|
| SecondaryExecId | 108 | 8 | Binary | Indicates whether an execution is a spread or a simple instrument execution that is part of a spread trade. If SecondaryExecId field is not present, the execution is a simple instrument execution only. If SecondaryExecId is present and is the same as the ExecId required field, the execution represents a spread execution for which associated simple instrument executions will follow.Simple instrument executions associated with a spread execution will contain a SecondaryExecId value that matches the ExecId of the associated spread execution. |
(New fields may be introduced at the end of this message. Consequently, TPHs must treat any additional bytes present as undefined values.)





