ExecInstValue (FIX tag 1308)

charFIX 5.0 SP2

ExecInstValue (tag 1308) is a char field defined in FIX 5.0 SP2. It appears in 10 message types, always optionally.

At a glance

Tag: 1308
Name: ExecInstValue
Datatype: char
Dialects: FIX 5.0 SP2
Messages: 10

What the specification says

Indicates execution instructions that are valid for the specified market segment

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

A real message using tag 1308

TradingSessionListUpdateReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	103
35	MsgType	BS	TradingSessionListUpdateReport
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
386	NoTradingSessions1 entry	1	repeating group
336	TradingSessionID	1	Day
340	TradSesStatus	0	Unknown
1232	NoExecInstRules2 entries	2	repeating group
1308	ExecInstValue	1
1308	ExecInstValue	1
10	CheckSum	090

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 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 1308 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
DerivativeSecurityList	AA	Optional	inside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › ExecInstRules
DerivativeSecurityListUpdateReport	BR	Optional	inside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › ExecInstRules
MarketDefinition	BU	Optional	inside the ExecInstRules component
MarketDefinitionUpdateReport	BV	Optional	inside the ExecInstRules component
SecurityDefinition	d	Optional	inside MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › ExecInstRules
SecurityDefinitionUpdateReport	BP	Optional	inside MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › ExecInstRules
SecurityList	y	Optional	inside SecListGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › ExecInstRules
SecurityListUpdateReport	BK	Optional	inside SecLstUpdRelSymGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › ExecInstRules
TradingSessionList	BJ	Optional	inside TrdSessLstGrp › TradingSessionRules › ExecInstRules
TradingSessionListUpdateReport	BS	Optional	inside TrdSessLstGrp › TradingSessionRules › ExecInstRules

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 1308 in TypeScript

decode.tsts

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[1308];field?.name;   // "ExecInstValue"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

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

Try the decoder Source on GitHub