TotalAffectedOrders (FIX tag 533)

intFIX 4.4FIX 5.0 SP2

TotalAffectedOrders (tag 533) is an int field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 1 message type, always optionally.

At a glance

Tag: 533
Name: TotalAffectedOrders
Datatype: int
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 1

What the specification says

FIX 4.4

Total number of orders affected by mass cancel request.

FIX 5.0 SP2

Total number of orders affected by either the OrderMassActionRequest(MsgType=CA) or OrderMassCancelRequest(MsgType=Q).

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

A real message using tag 533

OrderMassCancelReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	94
35	MsgType	r	Order Mass Cancel Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
37	OrderID	ORD-10042
530	MassCancelRequestType	1	Cancel orders for a security
531	MassCancelResponse	0	Cancel Request Rejected -- See MassCancelRejectReason (532)
533	TotalAffectedOrders	1
10	CheckSum	189

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 533 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 5.0 SP2	Where in the message
OrderMassActionReport	BZ	—	Optional	directly on the message body
OrderMassCancelReport	r	Optional	Optional	directly on the message body

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