MassCancelRejectReason (FIX tag 532)

charFIX 4.4FIX 5.0 SP2

MassCancelRejectReason (tag 532) is a char field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 1 message type, always optionally. It is an enumerated field with 8 defined values.

At a glance

Tag
532
Name
MassCancelRejectReason
Datatype
char
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
1
Valid values
8

What the specification says

Reason Order Mass Cancel Request was rejected

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

A real message using tag 532

OrderMassCancelReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength94
35MsgTyperOrder Mass Cancel Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
37OrderIDORD-10042
530MassCancelRequestType1Cancel orders for a security
531MassCancelResponse0Cancel Request Rejected -- See MassCancelRejectReason (532)
532MassCancelRejectReason0Mass Cancel Not Supported
10CheckSum187
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.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

ValueMeaningSymbolic nameDialects
0Mass Cancel Not SupportedMASS_CANCEL_NOT_SUPPORTEDFIX 4.4, FIX 5.0 SP2
1Invalid or unknown SecurityINVALID_OR_UNKNOWN_SECURITYFIX 4.4, FIX 5.0 SP2
2Invalid or unknown underlyingINVALID_OR_UNKNOWN_UNDERLYING / INVALID_OR_UNKOWN_UNDERLYING_SECURITYFIX 4.4, FIX 5.0 SP2
3Invalid or unknown ProductINVALID_OR_UNKNOWN_PRODUCTFIX 4.4, FIX 5.0 SP2
4Invalid or unknown CFICodeINVALID_OR_UNKNOWN_CFICODEFIX 4.4, FIX 5.0 SP2
5Invalid or unknown Security TypeINVALID_OR_UNKNOWN_SECURITY_TYPE / INVALID_OR_UNKNOWN_SECURITYTYPEFIX 4.4, FIX 5.0 SP2
6Invalid or unknown trading sessionINVALID_OR_UNKNOWN_TRADING_SESSIONFIX 4.4, FIX 5.0 SP2
99OtherOTHERFIX 4.4, FIX 5.0 SP2
7Invalid or unknown marketINVALID_OR_UNKNOWN_MARKETFIX 5.0 SP2
8Invalid or unknown market segmentINVALID_OR_UNKOWN_MARKET_SEGMENTFIX 5.0 SP2
9Invalid or unknown security groupINVALID_OR_UNKNOWN_SECURITY_GROUPFIX 5.0 SP2
10Invalid or unknown security issuerINVALID_OR_UNKNOWN_SECURITY_ISSUERFIX 5.0 SP2
11Invalid or unknown issuer of underlying securityINVALID_OR_UNKNOWN_ISSUER_OF_UNDERLYING_SECURITYFIX 5.0 SP2

Where tag 532 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.

MessageMsgTypeFIX 4.4FIX 5.0 SP2Where in the message
OrderMassCancelReportrConditionalOptionaldirectly on the message body

Wire format

A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.

Read tag 532 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 massCancelRejectReason = message.fields[532]?.raw;// e.g. "0" — Mass Cancel Not Supported// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(532)  ?.enumValues?.find((e) => e.value === massCancelRejectReason)  ?.description;

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