TotNoOrders (FIX tag 68)

intFIX 4.4FIX 4.2

TotNoOrders (tag 68) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 2 message types and is required in 2 of them.

At a glance

Tag: 68
Name: TotNoOrders
Datatype: int
Dialects: FIX 4.4 and FIX 4.2
Messages: 2

What the specification says

FIX 4.4

Total number of list order entries across all messages. Should be the sum of all NoOrders (73) in each message that has repeating list order entries related to the same ListID (66). Used to support fragmentation. (Prior to FIX 4.2 this field was named "ListNoOrds")

FIX 4.2

Total number of list order entries across all messages. Should be the sum of all NoOrders in each message that has repeating list order entries related to the same ListID. Used to support fragmentation. (Prior to FIX 4.2 this field was named "ListNoOrds")

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 68

NewOrderList · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	113
35	MsgType	E	Order – List
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
66	ListID	EXAMPLE
394	BidType	1	"Non Disclosed" Style (e.g. US/European)
68	TotNoOrders	1
73	NoOrders1 entry	1	repeating group
11	ClOrdID	ORD-10042
67	ListSeqNo	1
54	Side	1	Buy
10	CheckSum	199

Edit and decode it yourself

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.

Open in the full decoder →

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 68 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
ListStatus	N	Required	Required	directly on the message body
NewOrderList	E	Required	Required	directly on the message body

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 68 in TypeScript

decode.tsts

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[68];field?.name;   // "TotNoOrders"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

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

Try the decoder Source on GitHub