Tag number, field name, MsgType, message or component name, or a value such as 39=1 or OrdStatus=2. Search runs in your browser.
NextExpectedMsgSeqNum <789>
- Tag
789- Type
- SeqNum (base int)
- FIXML name
NextExpectedMsgSeqNum- Pedigree
- Added FIX 4.4
- Versions
- FIX Latest ✓ · FIX 4.4 ✓ · Not in FIX 4.2
NextExpectedMsgSeqNum <789> in plain English
Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).
NextExpectedMsgSeqNum gives the next MsgSeqNum (34) the sender expects to receive. It can be sent on the Logon and Logout messages.
Where it is used
Logon (35=A), Logout (35=5) .
In all, 2 messages in FIX Latest can carry it. Full list.
Example message
8=FIXT.1.1|9=90|35=A|49=BUYSIDE|56=SELLSIDE|34=1|52=20261116-08:30:00.000|98=0|108=30|141=Y|1137=10|789=1|10=084 Illustrative example, not real orders or market data. A Logon (35=A) in FIX Latest, shown with BeginString FIXT.1.1. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX Latest dictionary, but it is not a complete specification of the message.
Related tags: MsgSeqNum <34>
Description (from the Orchestra file)
Next expected MsgSeqNum value to be received.