NoExecInstRules (FIX tag 1232)

NumInGroupFIX 5.0 SP2group counter

NoExecInstRules (tag 1232) is a NumInGroup field defined in FIX 5.0 SP2. It appears in 10 message types, always optionally. Its datatype is NumInGroup, which makes it a repeating-group counter: its value is the number of entries that follow, not a quantity in its own right.

At a glance

Tag
1232
Name
NoExecInstRules
Datatype
NumInGroup (int)
Dialects
FIX 5.0 SP2
Messages
10

What the specification says

Number of execution instructions

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

A real message using tag 1232

TradingSessionList · FIX 5.0 SP2
TagFieldWire valueMeaning
8BeginStringFIXT.1.1
9BodyLength103
35MsgTypeBJTradingSessionList
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
386NoTradingSessions1 entry1repeating group
336TradingSessionID1Day
340TradSesStatus0Unknown
1232NoExecInstRules2 entries2repeating group
1308ExecInstValue1
1308ExecInstValue1
10CheckSum081
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 1232 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.

MessageMsgTypeRequirednessWhere in the message
DerivativeSecurityListAAOptionalinside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › ExecInstRules
DerivativeSecurityListUpdateReportBROptionalinside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › ExecInstRules
MarketDefinitionBUOptionalinside the ExecInstRules component
MarketDefinitionUpdateReportBVOptionalinside the ExecInstRules component
SecurityDefinitiondOptionalinside MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › ExecInstRules
SecurityDefinitionUpdateReportBPOptionalinside MarketSegmentGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › ExecInstRules
SecurityListyOptionalinside SecListGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › ExecInstRules
SecurityListUpdateReportBKOptionalinside SecLstUpdRelSymGrp › SecurityTradingRules › TradingSessionRulesGrp › TradingSessionRules › ExecInstRules
TradingSessionListBJOptionalinside TrdSessLstGrp › TradingSessionRules › ExecInstRules
TradingSessionListUpdateReportBSOptionalinside TrdSessLstGrp › TradingSessionRules › ExecInstRules

Wire format

The number of entries in the repeating group that follows. The next field on the wire is the group's delimiter tag. @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 1232 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);// NoExecInstRules is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[1232] is undefined.const entries = message.groups[1232] ?? [];for (const entry of entries) {  // entry.fields is keyed by tag; entry.groups holds nested groups}

Other NumInGroup 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-fix50sp2