MassActionScope (FIX tag 1374)

intFIX 5.0 SP2

MassActionScope (tag 1374) is an int field defined in FIX 5.0 SP2. It appears in 2 message types and is required in 2 of them. It is an enumerated field with 12 defined values.

At a glance

Tag: 1374
Name: MassActionScope
Datatype: int
Dialects: FIX 5.0 SP2
Messages: 2
Valid values: 12

What the specification says

Specifies scope of Order Mass Action Request.

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

A real message using tag 1374

OrderMassActionRequest · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	116
35	MsgType	CA	OrderMassActionRequest
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
1373	MassActionType	1	Suspend orders
1374	MassActionScope	1	All orders for a security
60	TransactTime	20240101-12:00:00.000
10	CheckSum	083

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.

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.

Value	Meaning	Symbolic name
1	All orders for a security	ALL_ORDERS_FOR_A_SECURITY
2	All orders for an underlying security	ALL_ORDERS_FOR_AN_UNDERLYING_SECURITY
3	All orders for a product	ALL_ORDERS_FOR_A_PRODUCT
4	All orders for a CFI Code	ALL_ORDERS_FOR_A_CFICODE
5	All orders for a security type	ALL_ORDERS_FOR_A_SECURITYTYPE
6	All orders for a trading session	ALL_ORDERS_FOR_A_TRADING_SESSION
7	All orders	ALL_ORDERS
8	All orders for a market	ALL_ORDERS_FOR_A_MARKET
9	All orders for a market segment (or multiple segments)	ALL_ORDERS_FOR_A_MARKET_SEGMENT
10	All orders for a security group	ALL_ORDERS_FOR_A_SECURITY_GROUP
11	All orders for an issuer	CANCEL_FOR_SECURITY_ISSUER
12	All orders for an issuer of underlying security	CANCEL_FOR_ISSUER_OF_UNDERLYING_SECURITY

Where tag 1374 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	Required	directly on the message body
OrderMassActionRequest	CA	Required	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 1374 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 massActionScope = message.fields[1374]?.raw;// e.g. "1" — All orders for a security// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(1374)  ?.enumValues?.find((e) => e.value === massActionScope)  ?.description;

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