TradingSessionID (FIX tag 336)

StringFIX 4.4FIX 4.2FIX 5.0 SP2

TradingSessionID (tag 336) is a String field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 51 message types and is required in 1 of them.

At a glance

Tag
336
Name
TradingSessionID
Datatype
String
Dialects
FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages
51

What the specification says

FIX 4.4

Identifier for Trading Session Can be used to represent a specific market trading session (e.g. "PRE-OPEN", "CROSS_2", "AFTER-HOURS", "TOSTNET", "TOSTNET2", etc). To specify good for session where session spans more than one calendar day, use TimeInForce = Day in conjunction with TradingSessionID. Values should be bi-laterally agreed to between counterparties. Firms may register Trading Session values on the FIX website (presently a document maintained within "ECN and Exchanges" working group section).

FIX 4.2

Identifier for Trading Session Can be used to represent a specific market trading session (e.g. "PRE-OPEN", "CROSS_2", "AFTER-HOURS", "TOSTNET1", "TOSTNET2", etc). Values should be bi-laterally agreed to between counterparties.

FIX 5.0 SP2

Identifier for a trading session.

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 336

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength141
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
386NoTradingSessions2 entries2repeating group
336TradingSessionIDREGULAR
336TradingSessionIDREGULAR
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum220
Edit and decode it yourself

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.

Open in the full decoder →

Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Where tag 336 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.

MessageMsgTypeFIX 4.4FIX 4.2FIX 5.0 SP2Where in the message
Advertisement7OptionalOptionalOptionaldirectly on the message body
AllocationInstructionJOptionalOptionalOptionaldirectly on the message body
AllocationInstructionAlertBM——Optionaldirectly on the message body
AllocationReportASOptional—Optionaldirectly on the message body
BidRequestkOptionalOptionalOptionalinside the BidCompReqGrp component
BidResponselOptionalOptionalOptionalinside the BidCompRspGrp component
CollateralAssignmentAYOptional—Optionaldirectly on the message body
CollateralInquiryBBOptional—Optionaldirectly on the message body
CollateralInquiryAckBGOptional—Optionaldirectly on the message body
CollateralReportBAOptional—Optionaldirectly on the message body
CollateralRequestAXOptional—Optionaldirectly on the message body
CrossOrderCancelReplaceRequesttConditional—Optionalinside the TrdgSesGrp component
DerivativeSecurityListAAOptional—Optionalinside the RelSymDerivSecGrp component
DerivativeSecurityListRequestzOptional—Optionaldirectly on the message body
DerivativeSecurityListUpdateReportBR——Optionalinside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp
ExecutionReport8OptionalOptionalOptionaldirectly on the message body
MarketDataIncrementalRefreshXOptionalOptionalOptionalinside the MDIncGrp component
MarketDataRequestVConditionalOptionalOptionalinside the TrdgSesGrp component
MarketDataSnapshotFullRefreshWOptionalOptionalOptionalinside the MDFullGrp component
MassQuoteiOptionalOptionalOptionalinside QuotSetGrp › QuotEntryGrp
MassQuoteAcknowledgementbOptionalOptionalOptionalinside QuotSetAckGrp › QuotEntryAckGrp
MultilegOrderCancelReplaceACConditional—Optionalinside the TrdgSesGrp component
NewOrderCrosssConditional—Optionalinside the TrdgSesGrp component
NewOrderListEConditionalOptionalOptionalinside ListOrdGrp › TrdgSesGrp
NewOrderMultilegABConditional—Optionalinside the TrdgSesGrp component
NewOrderSingleDConditionalOptionalOptionalinside the TrdgSesGrp component
OrderCancelReplaceRequestGConditionalOptionalOptionalinside the TrdgSesGrp component
OrderMassActionReportBZ——Optionaldirectly on the message body
OrderMassActionRequestCA——Optionaldirectly on the message body
OrderMassCancelReportrOptional—Optionaldirectly on the message body
OrderMassCancelRequestqOptional—Optionaldirectly on the message body
OrderMassStatusRequestAFOptional—Optionaldirectly on the message body
PositionMaintenanceReportAMConditional—Optionalinside the TrdgSesGrp component
PositionMaintenanceRequestALConditional—Optionalinside the TrdgSesGrp component
QuoteSOptionalOptionalOptionaldirectly on the message body
QuoteCancelZOptionalOptionalOptionaldirectly on the message body
QuoteRequestROptionalOptionalOptionalinside the QuotReqGrp component
QuoteRequestRejectAGOptional—Optionalinside the QuotReqRjctGrp component
QuoteResponseAJOptional—Optionaldirectly on the message body
QuoteStatusReportAIOptional—Optionaldirectly on the message body
QuoteStatusRequestaOptionalOptionalOptionaldirectly on the message body
RFQRequestAHOptional—Optionalinside the RFQReqGrp component
RequestForPositionsANConditional—Optionalinside the TrdgSesGrp component
SecurityDefinitiondOptionalOptionalOptionaldirectly on the message body
SecurityDefinitionRequestcOptionalOptionalOptionaldirectly on the message body
SecurityDefinitionUpdateReportBP——Optionalinside MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp
SecurityListyOptional—Optionalinside the SecListGrp component
SecurityListRequestxOptional—Optionaldirectly on the message body
SecurityListUpdateReportBK——Optionalinside SecLstUpdRelSymGrp › SecurityTradingRules › TradingSessionRulesGrp
SecurityStatusfOptionalOptionalOptionaldirectly on the message body
SecurityStatusRequesteOptionalOptionalOptionaldirectly on the message body
SecurityTypeRequestvOptional—Optionaldirectly on the message body
SecurityTypeswOptional—Optionaldirectly on the message body
SettlementInstructionsT—Optional—directly on the message body
TradeCaptureReportAEOptional—Optionalinside the TrdCapRptSideGrp component
TradeCaptureReportAckAR——Optionalinside the TrdCapRptAckSideGrp component
TradeCaptureReportRequestADOptional—Optionaldirectly on the message body
TradingSessionListBJ——Requiredinside the TrdSessLstGrp component
TradingSessionListRequestBI——Optionaldirectly on the message body
TradingSessionListUpdateReportBS——Requiredinside the TrdSessLstGrp component
TradingSessionStatushRequiredRequiredRequireddirectly on the message body
TradingSessionStatusRequestgOptionalOptionalOptionaldirectly on the message body

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 336 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";​const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);​const field = message.fields[336];field?.name;   // "TradingSessionID"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Other String fields

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-fix44