NotAffOrigClOrdID (FIX tag 1372)

StringFIX 5.0 SP2

NotAffOrigClOrdID (tag 1372) is a String field defined in FIX 5.0 SP2. It appears in 2 message types, always optionally.

At a glance

Tag: 1372
Name: NotAffOrigClOrdID
Datatype: String
Dialects: FIX 5.0 SP2
Messages: 2

What the specification says

ClOrdID(11) of an order not affected by a mass cancel or mass action request.

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

A real message using tag 1372

OrderMassCancelReport · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	134
35	MsgType	r	OrderMassCancelReport
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
37	OrderID	ORD-10042
1369	MassActionReportID	EXAMPLE
530	MassCancelRequestType	1	Cancel orders for a security
531	MassCancelResponse	0	Cancel Request Rejected - See MassCancelRejectReason (532)
1370	NoNotAffectedOrders2 entries	2	repeating group
1372	NotAffOrigClOrdID	EXAMPLE
1372	NotAffOrigClOrdID	EXAMPLE
10	CheckSum	178

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 1372 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	Requiredness	Where in the message
OrderMassActionReport	BZ	Optional	inside the NotAffectedOrdersGrp component
OrderMassCancelReport	r	Optional	inside the NotAffectedOrdersGrp component

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 1372 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[1372];field?.name;   // "NotAffOrigClOrdID"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

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

Try the decoder Source on GitHub