SideTimeInForce (FIX tag 962)
SideTimeInForce (tag 962) is an UTCTimestamp field defined in FIX 5.0 SP2. It appears in 2 message types, always optionally.
At a glance
- Tag
- 962
- Name
- SideTimeInForce
- Datatype
- UTCTimestamp (String)
- Format
- YYYYMMDD-HH:MM:SS[.sss]
- Dialects
- FIX 5.0 SP2
- Messages
- 2
What the specification says
Indicates how long the order as specified in the side stays in effect. SideTimeInForce allows a two-sided cross order to specify order behavior separately for each side. Absence of this field indicates that TimeInForce should be referenced. SideTimeInForce will override TimeInForce if both are provided.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 962
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 211 | |
| 35 | MsgType | s | NewOrderCross |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 548 | CrossID | EXAMPLE | |
| 549 | CrossType | 1 | All-or-none cross |
| 550 | CrossPrioritization | 0 | None |
| 552 | NoSides2 entries | 2 | repeating group |
| 54 | Side | 1 | Buy |
| 11 | ClOrdID | ORD-10042 | |
| 962 | SideTimeInForce | 20240101-12:00:00.000 | |
| 54 | Side | 1 | Buy |
| 11 | ClOrdID | ORD-10042 | |
| 962 | SideTimeInForce | 20240101-12:00:00.000 | |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 40 | OrdType | 1 | Market |
| 10 | CheckSum | 213 |
Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.
Generated from the FIX 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.
Where tag 962 appears
Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.
| Message | MsgType | Requiredness | Where in the message |
|---|---|---|---|
| CrossOrderCancelReplaceRequest | t | Optional | inside the SideCrossOrdModGrp component |
| NewOrderCross | s | Optional | inside the SideCrossOrdModGrp component |
Wire format
A UTC date and time. The fractional-seconds part is optional, so two timestamps can be equal but not byte-identical. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.
Read tag 962 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[962];field?.name; // "SideTimeInForce"field?.raw; // the verbatim wire stringfield?.value; // coerced to a stringOther UTCTimestamp fields
- 1012SideTrdRegTimestamp
- 779LastUpdateTime
- 1145EventTime
- 769TrdRegTimestamp
- 1289DerivativeEventTime
- 629HopSendingTime
- 586OrigOrdModTime
- 515ExecValuationPoint
- 483TransBkdTime
- 443StrikeTime
- 438ContraTradeTime
- 1492ComplexEventStartDate
- 1493ComplexEventEndDate
- 1504RelSymTransactTime
- 370OnBehalfOfSendingTime
- 367QuoteSetValidUntilTime
- 345TradSesEndTime
- 344TradSesCloseTime
- 343TradSesPreCloseTime
- 342TradSesOpenTime
- 341TradSesStartTime
- 168EffectiveTime
- 126ExpireTime
- 122OrigSendingTime
Decode this in your own code
The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.
npm i @boarteam/fix @boarteam/fix-dict-fix50sp2