CxlQty (FIX tag 84)

QtyFIX 4.4FIX 4.2

CxlQty (tag 84) is a Qty field defined in FIX 4.4 and FIX 4.2. It appears in 1 message type and is required in 1 of them.

At a glance

Tag: 84
Name: CxlQty
Datatype: Qty (float)
Dialects: FIX 4.4 and FIX 4.2
Messages: 1

What the specification says

FIX 4.4

Total quantity canceled for this order. (Prior to FIX 4.2 this field was of type int)

FIX 4.2

Total number of shares canceled for this order. (Prior to FIX 4.2 this field was of type int)

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

A real message using tag 84

ListStatus · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	218
35	MsgType	N	List Status
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
66	ListID	EXAMPLE
429	ListStatusType	1	Ack
82	NoRpts	1
431	ListOrderStatus	1	InBiddingProcess
83	RptSeq	1
68	TotNoOrders	1
73	NoOrders2 entries	2	repeating group
11	ClOrdID	ORD-10042
14	CumQty	1000000
39	OrdStatus	0	New
151	LeavesQty	0
84	CxlQty	1000000
6	AvgPx	1.09215
11	ClOrdID	ORD-10042
14	CumQty	1000000
39	OrdStatus	0	New
151	LeavesQty	0
84	CxlQty	1000000
6	AvgPx	1.09215
10	CheckSum	201

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 84 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.

Message	MsgType	FIX 4.4	FIX 4.2	Where in the message
ListStatus	N	Required	Required	inside the OrdListStatGrp 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 84 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[84];field?.name;   // "CxlQty"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

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

Try the decoder Source on GitHub