Tag number, field name, MsgType, message or component name, or a value such as 39=1 or OrdStatus=2. Search runs in your browser.
MaxMessageSize <383>
- Tag
383- Type
- int
- Pedigree
- Added FIX 4.2
- Versions
- FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓
This page shows MaxMessageSize <383> as defined in FIX 4.2. For the current standard, see tag 383 MaxMessageSize in FIX Latest.
MaxMessageSize <383> in plain English
Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).
MaxMessageSize, sent on the Logon message, gives the largest single message, in bytes, that the sender supports.
Where it is used
Logon (35=A) .
In all, 1 message in FIX 4.2 can carry it. Full list.
Example message
8=FIX.4.2|9=85|35=A|49=BUYSIDE|56=SELLSIDE|34=1|52=20261116-08:30:00.000|98=0|108=30|141=Y|383=8192|10=054 Illustrative example, not real orders or market data. A Logon (35=A) in FIX 4.2, shown with BeginString FIX.4.2. 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 4.2 dictionary, but it is not a complete specification of the message.
Description (from the Orchestra file)
Maximum number of bytes supported for a single message.
Used in
Messages (1)
| Message | MsgType | Presence |
|---|---|---|
| Logon | A | Optional |