StatusValue (FIX tag 928)

intFIX 4.4

StatusValue (tag 928) is an int field defined in FIX 4.4. It appears in 1 message type, always optionally. It is an enumerated field with 4 defined values.

At a glance

Tag: 928
Name: StatusValue
Datatype: int
Dialects: FIX 4.4
Messages: 1
Valid values: 4

What the specification says

Indicates the status of a network connection

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

A real message using tag 928

NetworkCounterpartySystemStatusResponse · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	124
35	MsgType	BD	Network (Counterparty System) Status Response
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
937	NetworkStatusResponseType	1	Full
932	NetworkResponseID	EXAMPLE
936	NoCompIDs2 entries	2	repeating group
930	RefCompID	EXAMPLE
928	StatusValue	1	Connected
930	RefCompID	EXAMPLE
928	StatusValue	1	Connected
10	CheckSum	046

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.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

Value	Meaning	Symbolic name
1	Connected	CONNECTED
2	Not connected – down expected up	NOT_CONNECTED_DOWN_EXPECTED_UP
3	Not connected – down expected down	NOT_CONNECTED_DOWN_EXPECTED_DOWN
4	In Process	IN_PROCESS

Where tag 928 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	Requiredness	Where in the message
NetworkCounterpartySystemStatusResponse	BD	Optional	inside the CompIDStatGrp 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 928 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 statusValue = message.fields[928]?.raw;// e.g. "1" — Connected// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(928)  ?.enumValues?.find((e) => e.value === statusValue)  ?.description;

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