ExpQty (FIX tag 983)

QtyFIX 5.0 SP2

ExpQty (tag 983) is a Qty field defined in FIX 5.0 SP2. It appears in 1 message type, always optionally.

At a glance

Tag
983
Name
ExpQty
Datatype
Qty (float)
Dialects
FIX 5.0 SP2
Messages
1

What the specification says

Expiration Quantity associated with the Expiration Type

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

A real message using tag 983

ContraryIntentionReport · FIX 5.0 SP2
TagFieldWire valueMeaning
8BeginStringFIXT.1.1
9BodyLength131
35MsgTypeBOContraryIntentionReport
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
977ContIntRptIDEXAMPLE
715ClearingBusinessDate20240101
981NoExpiration2 entries2repeating group
982ExpirationQtyType1Auto Exercise
983ExpQty1000000
982ExpirationQtyType1Auto Exercise
983ExpQty1000000
10CheckSum123
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 983 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
ContraryIntentionReportBOOptionalinside the ExpirationQty component

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