NoAltMDSource (FIX tag 816)
NoAltMDSource (tag 816) is a NumInGroup field defined in FIX 4.4. It appears in 1 message type, 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
- 816
- Name
- NoAltMDSource
- Datatype
- NumInGroup (int)
- Dialects
- FIX 4.4
- Messages
- 1
What the specification says
Number of alternative market data sources
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 816
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 103 | |
| 35 | MsgType | Y | Market Data Request Reject |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 262 | MDReqID | REQ-1 | |
| 816 | NoAltMDSource2 entries | 2 | repeating group |
| 817 | AltMDSourceID | EXAMPLE | |
| 817 | AltMDSourceID | EXAMPLE | |
| 10 | CheckSum | 003 |
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 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.
Where tag 816 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 |
|---|---|---|---|
| MarketDataRequestReject | Y | Optional | inside the MDRjctGrp component |
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 816 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);// NoAltMDSource is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[816] is undefined.const entries = message.groups[816] ?? [];for (const entry of entries) { // entry.fields is keyed by tag; entry.groups holds nested groups}Other NumInGroup fields
- 806NoNested2PartySubIDs
- 804NoNestedPartySubIDs
- 802NoPartySubIDs
- 801NoSettlPartySubIDs
- 781NoSettlPartyIDs
- 778NoSettlInst
- 862NoCapacities
- 768NoTrdRegTimestamps
- 864NoEvents
- 870NoInstrAttrib
- 756NoNested2PartyIDs
- 753NoPosAmt
- 887NoUnderlyingStips
- 735NoQuoteQualifiers
- 897NoTrades
- 711NoUnderlyings
- 702NoPositions
- 936NoCompIDs
- 938NoCollInquiryQualifier
- 948NoNested3PartyIDs
- 683NoLegStipulations
- 952NoNested3PartySubIDs
- 670NoLegAllocs
- 627NoHops
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