CxlRejReason (FIX tag 102)

intFIX 4.4FIX 4.2FIX 5.0 SP2

CxlRejReason (tag 102) is an int field defined in FIX 4.4, FIX 4.2 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
102
Name
CxlRejReason
Datatype
int
Dialects
FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages
1
Valid values
8

What the specification says

FIX 4.4

Code to identify reason for cancel rejection

FIX 4.2

Code to identify reason for cancel rejection.

FIX 5.0 SP2

Code to identify reason for cancel rejection.

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

A real message using tag 102

OrderCancelReject · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength119
35MsgType9Order Cancel Reject
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
37OrderIDORD-10042
11ClOrdIDORD-10042
41OrigClOrdIDORD-10041
39OrdStatus0New
434CxlRejResponseTo1Order Cancel Request
102CxlRejReason0Too late to cancel
10CheckSum211
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
0Too late to cancelTOO_LATE_TO_CANCEL / TooLateToCancelFIX 4.4, FIX 4.2, FIX 5.0 SP2
1Unknown orderUNKNOWN_ORDER / UnknownOrderFIX 4.4, FIX 4.2, FIX 5.0 SP2
2Broker / Exchange OptionBROKER / BrokerCredit / BROKER_EXCHANGE_OPTIONFIX 4.4, FIX 4.2, FIX 5.0 SP2
3Order already in Pending Cancel or Pending Replace statusORDER_ALREADY_IN_PENDING_CANCEL_OR_PENDING_REPLACE_STATUS / OrderAlreadyInPendingStatusFIX 4.4, FIX 4.2, FIX 5.0 SP2
4Unable to process Order Mass Cancel RequestUNABLE_TO_PROCESS_ORDER_MASS_CANCEL_REQUESTFIX 4.4, FIX 5.0 SP2
5OrigOrdModTime (586) did not match last TransactTime (60) of orderORIGORDMODTIME / ORIGORDMODTIME_OF_ORDERFIX 4.4, FIX 5.0 SP2
6Duplicate ClOrdID (11) receivedDUPLICATE_CLORDID / DUPLICATE_CLORDID_RECEIVEDFIX 4.4, FIX 5.0 SP2
99OtherOTHERFIX 4.4, FIX 5.0 SP2
7Price exceeds current pricePRICE_EXCEEDS_CURRENT_PRICEFIX 5.0 SP2
8Price exceeds current price bandPRICE_EXCEEDS_CURRENT_PRICE_BANDFIX 5.0 SP2
18Invalid price incrementINVALID_PRICE_INCREMENTFIX 5.0 SP2

Where tag 102 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 4.2FIX 5.0 SP2Where in the message
OrderCancelReject9OptionalOptionalOptionaldirectly 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 102 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 cxlRejReason = message.fields[102]?.raw;// e.g. "0" — Too late to cancel// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(102)  ?.enumValues?.find((e) => e.value === cxlRejReason)  ?.description;

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