SecondaryDisplayQty (FIX tag 1082)

QtyFIX 5.0 SP2

SecondaryDisplayQty (tag 1082) is a Qty field defined in FIX 5.0 SP2. It appears in 10 message types, always optionally.

At a glance

Tag
1082
Name
SecondaryDisplayQty
Datatype
Qty (float)
Dialects
FIX 5.0 SP2
Messages
10

What the specification says

Used for reserve orders when DisplayQty applies to the primary execution market (e.g.an ECN) and another quantity is to be shown at other markets (e.g. the exchange). On orders specifies the qty to be displayed, on execution reports the currently displayed quantity.

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

A real message using tag 1082

NewOrderSingle · FIX 5.0 SP2
TagFieldWire valueMeaning
8BeginStringFIXT.1.1
9BodyLength124
35MsgTypeDNewOrderSingle
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
1082SecondaryDisplayQty1000000
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum156
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 1082 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 DisplayInstruction component
ExecutionReport8Optionalinside the DisplayInstruction component
MultilegOrderCancelReplaceACOptionalinside the DisplayInstruction component
NewOrderCrosssOptionalinside the DisplayInstruction component
NewOrderListEOptionalinside ListOrdGrp › DisplayInstruction
NewOrderMultilegABOptionalinside the DisplayInstruction component
NewOrderSingleDOptionalinside the DisplayInstruction component
OrderCancelReplaceRequestGOptionalinside the DisplayInstruction component
TradeCaptureReportAEOptionalinside TrdCapRptSideGrp › TradeReportOrderDetail › DisplayInstruction
TradeCaptureReportAckAROptionalinside TrdCapRptAckSideGrp › TradeReportOrderDetail › DisplayInstruction

Wire format

A decimal quantity. Fractional quantities are legal, which is why this is a float family rather than an integer. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.

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

Other Qty 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