MultilegModel (FIX tag 1377)

intFIX 5.0 SP2

MultilegModel (tag 1377) is an int field defined in FIX 5.0 SP2. It appears in 10 message types, always optionally. It is an enumerated field with 3 defined values.

At a glance

Tag
1377
Name
MultilegModel
Datatype
int
Dialects
FIX 5.0 SP2
Messages
10
Valid values
3

What the specification says

Specifies the type of multileg order. Defines whether the security is pre-defined or user-defined. Note that MultilegModel(1377)=2(User-defined, Non-Securitized, Multileg) does not apply for Securities.

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

A real message using tag 1377

NewOrderMultileg · FIX 5.0 SP2
TagFieldWire valueMeaning
8BeginStringFIXT.1.1
9BodyLength137
35MsgTypeABNewOrderMultileg
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
54Side1Buy
555NoLegs1 entry1repeating group
600LegSymbolEXAMPLE
60TransactTime20240101-12:00:00.000
40OrdType1Market
1377MultilegModel0Predefined Multileg Security
10CheckSum179
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.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

ValueMeaningSymbolic name
0Predefined Multileg SecurityPREDEFINED_MULTILEG_SECURITY
1User-defined Multileg SecurityUSER_DEFINED_MULTLEG_SECURITY
2User-defined, Non-Securitized, MultilegUSER_DEFINED_NON_SECURITIZED_MULTILEG

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

MessageMsgTypeRequirednessWhere in the message
DerivativeSecurityListAAOptionalinside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › BaseTradingRules
DerivativeSecurityListUpdateReportBROptionalinside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › BaseTradingRules
MarketDefinitionBUOptionalinside the BaseTradingRules component
MarketDefinitionUpdateReportBVOptionalinside the BaseTradingRules component
MultilegOrderCancelReplaceACOptionaldirectly on the message body
NewOrderMultilegABOptionaldirectly on the message body
SecurityDefinitiondOptionalinside MarketSegmentGrp › SecurityTradingRules › BaseTradingRules
SecurityDefinitionUpdateReportBPOptionalinside MarketSegmentGrp › SecurityTradingRules › BaseTradingRules
SecurityListyOptionalinside SecListGrp › SecurityTradingRules › BaseTradingRules
SecurityListUpdateReportBKOptionalinside SecLstUpdRelSymGrp › SecurityTradingRules › BaseTradingRules

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 1377 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 multilegModel = message.fields[1377]?.raw;// e.g. "0" — Predefined Multileg Security// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(1377)  ?.enumValues?.find((e) => e.value === multilegModel)  ?.description;

Other int 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-fix50sp2