MDEntryPositionNo (FIX tag 290)
MDEntryPositionNo (tag 290) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 2 message types, always optionally.
At a glance
- Tag
- 290
- Name
- MDEntryPositionNo
- Datatype
- int
- Dialects
- FIX 4.4 and FIX 4.2
- Messages
- 2
What the specification says
FIX 4.4
Display position of a bid or offer, numbered from most competitive to least competitive, per market side, beginning with .
FIX 4.2
Display position of a bid or offer, numbered from most competitive to least competitive, per market side, beginning with 1.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 290
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 93 | |
| 35 | MsgType | W | Market Data-Snapshot/Full Refresh |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 268 | NoMDEntries2 entries | 2 | repeating group |
| 269 | MDEntryType | 0 | Bid |
| 290 | MDEntryPositionNo | 1 | |
| 269 | MDEntryType | 0 | Bid |
| 290 | MDEntryPositionNo | 1 | |
| 10 | CheckSum | 026 |
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 290 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 | FIX 4.4 | FIX 4.2 | Where in the message |
|---|---|---|---|---|
| MarketDataIncrementalRefresh | X | Optional | Optional | inside the MDIncGrp component |
| MarketDataSnapshotFullRefresh | W | Optional | Optional | inside the MDFullGrp component |
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 290 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[290];field?.name; // "MDEntryPositionNo"field?.raw; // the verbatim wire stringfield?.value; // coerced to a numberOther int fields
- 287SellerDays
- 297QuoteStatus
- 298QuoteCancelType
- 300QuoteRejectReason
- 301QuoteResponseLevel
- 303QuoteRequestType
- 304TotNoQuoteEntries
- 265MDUpdateType
- 315UnderlyingPutOrCall
- 264MarketDepth
- 321SecurityRequestType
- 323SecurityResponseType
- 326SecurityTradingStatus
- 251LegRepurchaseTerm
- 334Adjustment
- 244UnderlyingRepurchaseTerm
- 338TradSesMethod
- 339TradSesMode
- 340TradSesStatus
- 346NumberOfOrders
- 226RepurchaseTerm
- 216RoutingType
- 368QuoteEntryRejectReason
- 209AllocHandlInst
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