RootPartyRole (FIX tag 1119)

intFIX 5.0 SP2

RootPartyRole (tag 1119) is an int field defined in FIX 5.0 SP2. It appears in 8 message types, always optionally.

At a glance

Tag
1119
Name
RootPartyRole
Datatype
int
Dialects
FIX 5.0 SP2
Messages
8

What the specification says

PartyRole value within a root parties component. Same values as PartyRole (452)

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

A real message using tag 1119

QuoteRequest · FIX 5.0 SP2
TagFieldWire valueMeaning
8BeginStringFIXT.1.1
9BodyLength139
35MsgTypeRQuoteRequest
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
131QuoteReqIDEXAMPLE
1116NoRootPartyIDs2 entries2repeating group
1117RootPartyIDEXAMPLE
1119RootPartyRole1
1117RootPartyIDEXAMPLE
1119RootPartyRole1
146NoRelatedSym1 entry1repeating group
55SymbolEUR/USD
10CheckSum193
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 1119 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
CrossOrderCancelReplaceRequesttOptionalinside the RootParties component
CrossOrderCancelRequestuOptionalinside the RootParties component
NewOrderCrosssOptionalinside the RootParties component
NewOrderListEOptionalinside the RootParties component
QuoteRequestROptionalinside the RootParties component
QuoteRequestRejectAGOptionalinside the RootParties component
TradeCaptureReportAEOptionalinside the RootParties component
TradeCaptureReportAckAROptionalinside the RootParties component

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

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