NoOfSecSizes (FIX tag 1177)
NoOfSecSizes (tag 1177) is a NumInGroup field defined in FIX 5.0 SP2. It appears in 2 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
- 1177
- Name
- NoOfSecSizes
- Datatype
- NumInGroup (int)
- Dialects
- FIX 5.0 SP2
- Messages
- 2
What the specification says
The number of secondary sizes specifies in this entry
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1177
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 96 | |
| 35 | MsgType | W | MarketDataSnapshotFullRefresh |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 268 | NoMDEntries1 entry | 1 | repeating group |
| 269 | MDEntryType | 0 | Bid |
| 1177 | NoOfSecSizes2 entries | 2 | repeating group |
| 1178 | MDSecSizeType | 1 | Customer |
| 1178 | MDSecSizeType | 1 | Customer |
| 10 | CheckSum | 007 |
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.
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 1177 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 |
|---|---|---|---|
| MarketDataIncrementalRefresh | X | Optional | inside MDIncGrp › SecSizesGrp |
| MarketDataSnapshotFullRefresh | W | Optional | inside MDFullGrp › SecSizesGrp |
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 1177 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);// NoOfSecSizes is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[1177] is undefined.const entries = message.groups[1177] ?? [];for (const entry of entries) { // entry.fields is keyed by tag; entry.groups holds nested groups}Other NumInGroup fields
- 1175NoStatsIndicators
- 1165NoSettlOblig
- 1158NoSettlDetails
- 1201NoStrikeRules
- 1205NoTickRules
- 1141NoMDFeedTypes
- 1218NoDerivativeSecurityAltID
- 1232NoExecInstRules
- 1120NoRootPartySubIDs
- 1234NoLotTypeRules
- 1235NoMatchRules
- 1236NoMaturityRules
- 1237NoOrdTypeRules
- 1116NoRootPartyIDs
- 1239NoTimeInForceRules
- 1286NoDerivativeEvents
- 1062NoUndlyInstrumentPartySubIDs
- 1292NoDerivativeInstrumentParties
- 1058NoUndlyInstrumentParties
- 1296NoDerivativeInstrumentPartySubIDs
- 1052NoInstrumentPartySubIDs
- 1309NoTradingSessionRules
- 1310NoMarketSegments
- 1311NoDerivativeInstrAttrib
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