LegExecInst (FIX tag 1384)

MultipleCharValueFIX 5.0 SP2

LegExecInst (tag 1384) is a MultipleCharValue field defined in FIX 5.0 SP2. It appears in 5 message types, always optionally.

At a glance

Tag: 1384
Name: LegExecInst
Datatype: MultipleCharValue (String)
Dialects: FIX 5.0 SP2
Messages: 5

What the specification says

Refer to ExecInst(18)

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

A real message using tag 1384

ExecutionReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	171
35	MsgType	8	ExecutionReport
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
37	OrderID	ORD-10042
17	ExecID	EXEC-88117
150	ExecType	0	New
39	OrdStatus	0	New
54	Side	1	Buy
151	LeavesQty	0
14	CumQty	1000000
555	NoLegs2 entries	2	repeating group
600	LegSymbol	EXAMPLE
1384	LegExecInst	1 2
600	LegSymbol	EXAMPLE
1384	LegExecInst	1 2
10	CheckSum	134

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 1384 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
ExecutionReport	8	Optional	inside the InstrmtLegExecGrp component
MultilegOrderCancelReplace	AC	Optional	inside the LegOrdGrp component
NewOrderMultileg	AB	Optional	inside the LegOrdGrp component
TradeCaptureReport	AE	Optional	inside the TrdInstrmtLegGrp component
TradeCaptureReportAck	AR	Optional	inside the TrdInstrmtLegGrp component

Wire format

Values are carried as String on the wire. @boarteam/fix splits the value on its delimiter and returns an array of strings.

Read tag 1384 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[1384];field?.name;   // "LegExecInst"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to an array of strings

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