TradSesUpdateAction (FIX tag 1327)
TradSesUpdateAction (tag 1327) is a char field defined in FIX 5.0 SP2. It appears in 2 message types, always optionally.
At a glance
- Tag
- 1327
- Name
- TradSesUpdateAction
- Datatype
- char
- Dialects
- FIX 5.0 SP2
- Messages
- 2
What the specification says
Specifies the action taken for the specified trading sessions.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1327
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 108 | |
| 35 | MsgType | BJ | TradingSessionList |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 386 | NoTradingSessions2 entries | 2 | repeating group |
| 336 | TradingSessionID | 1 | Day |
| 1327 | TradSesUpdateAction | 1 | |
| 340 | TradSesStatus | 0 | Unknown |
| 336 | TradingSessionID | 1 | Day |
| 1327 | TradSesUpdateAction | 1 | |
| 340 | TradSesStatus | 0 | Unknown |
| 10 | CheckSum | 049 |
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 1327 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 |
|---|---|---|---|
| TradingSessionList | BJ | Optional | inside the TrdSessLstGrp component |
| TradingSessionListUpdateReport | BS | Optional | inside the TrdSessLstGrp component |
Wire format
A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.
Read tag 1327 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[1327];field?.name; // "TradSesUpdateAction"field?.raw; // the verbatim wire stringfield?.value; // coerced to a stringOther char fields
- 1324ListUpdateAction
- 1317DerivativeSettlMethod
- 1308ExecInstValue
- 1299DerivativeExerciseStyle
- 1265DerivativeOptAttribute
- 1391UnderlyingLegOptAttribute
- 1395MarketUpdateAction
- 1255DerivativeInstrmtAssignmentMethod
- 1416Nested4PartyIDSource
- 1430VenueType
- 1193SettlMethod
- 1463TargetPartyIDSource
- 1164SettlObligSource
- 1162SettlObligTransType
- 1133ExDestinationIDSource
- 1124OrigTradeHandlingInstr
- 1123TradeHandlingInstr
- 1118RootPartyIDSource
- 1115OrderCategory
- 1111TriggerOrderType
- 1109TriggerPriceDirection
- 1108TriggerPriceTypeScope
- 1107TriggerPriceType
- 1101TriggerAction
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