LegBenchmarkCurveName (FIX tag 677)

StringFIX 4.4

LegBenchmarkCurveName (tag 677) is a String field defined in FIX 4.4. It appears in 5 message types, always optionally.

At a glance

Tag
677
Name
LegBenchmarkCurveName
Datatype
String
Dialects
FIX 4.4
Messages
5

What the specification says

Name of the Leg Benchmark Curve. See BenchmarkCurveName(221) for description and valid values.

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

A real message using tag 677

Quote · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength129
35MsgTypeSQuote
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
117QuoteIDEXAMPLE
555NoLegs2 entries2repeating group
600LegSymbolEXAMPLE
677LegBenchmarkCurveNameEXAMPLE
600LegSymbolEXAMPLE
677LegBenchmarkCurveNameEXAMPLE
10CheckSum146
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 677 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
QuoteSOptionalinside LegQuotGrp › LegBenchmarkCurveData
QuoteRequestROptionalinside QuotReqGrp › QuotReqLegsGrp › LegBenchmarkCurveData
QuoteRequestRejectAGOptionalinside QuotReqRjctGrp › QuotReqLegsGrp › LegBenchmarkCurveData
QuoteResponseAJOptionalinside LegQuotGrp › LegBenchmarkCurveData
SecurityListyOptionalinside SecListGrp › InstrmtLegSecListGrp › LegBenchmarkCurveData

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 677 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[677];field?.name;   // "LegBenchmarkCurveName"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