SeqNum
base: intFIX 4.4FIX 5.0 SP2
SeqNum is a FIX datatype defined in FIX 4.4 and FIX 5.0 SP2, carried on the wire as int. 8 fields use it.
Wire format
- Base type
- int
- Fields
- 8
A positive sequence number. Session-level, and monotonic within a session.
What the specification says
FIX 4.4
int field representing a message sequence number. Value must be positive.
FIX 5.0 SP2
Sequence of digits without commas or decimals. Value must be positive and may not contain leading zeros.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
How @boarteam/fix handles it
@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.
Fields with this datatype
| Tag | Field | Dialects | Messages |
|---|---|---|---|
| 7 | BeginSeqNo | FIX 4.4, FIX 4.2, FIX 5.0 SP2 | 1 |
| 16 | EndSeqNo | FIX 4.4, FIX 4.2, FIX 5.0 SP2 | 1 |
| 34 | MsgSeqNum | FIX 4.4, FIX 4.2, FIX 5.0 SP2 | 93 |
| 36 | NewSeqNo | FIX 4.4, FIX 4.2, FIX 5.0 SP2 | 1 |
| 45 | RefSeqNum | FIX 4.4, FIX 4.2, FIX 5.0 SP2 | 2 |
| 369 | LastMsgSeqNumProcessed | FIX 4.4, FIX 4.2, FIX 5.0 SP2 | 93 |
| 630 | HopRefID | FIX 4.4, FIX 5.0 SP2 | 93 |
| 789 | NextExpectedMsgSeqNum | FIX 4.4, FIX 5.0 SP2 | 1 |
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