PosMaintStatus (FIX tag 722)

intFIX 4.4

PosMaintStatus (tag 722) is an int field defined in FIX 4.4. It appears in 1 message type and is required in 1 of them. It is an enumerated field with 5 defined values.

At a glance

Tag: 722
Name: PosMaintStatus
Datatype: int
Dialects: FIX 4.4
Messages: 1
Valid values: 5

What the specification says

Status of Position Maintenance Request

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

A real message using tag 722

PositionMaintenanceReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	163
35	MsgType	AM	Position Maintenance Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
721	PosMaintRptID	EXAMPLE
709	PosTransType	1	Exercise
712	PosMaintAction	1	New: used to increment the overall transaction quantity
713	OrigPosReqRefID	EXAMPLE
722	PosMaintStatus	0	Accepted
715	ClearingBusinessDate	20240101
1	Account	ACCT-11223
581	AccountType	1	Account is carried on customer Side of Books
60	TransactTime	20240101-12:00:00.000
10	CheckSum	249

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
0	Accepted	ACCEPTED
1	Accepted with Warnings	ACCEPTED_WITH_WARNINGS
2	Rejected	REJECTED
3	Completed	COMPLETED
4	Completed with Warnings	COMPLETED_WITH_WARNINGS

Where tag 722 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
PositionMaintenanceReport	AM	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 722 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 posMaintStatus = message.fields[722]?.raw;// e.g. "0" — Accepted// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(722)  ?.enumValues?.find((e) => e.value === posMaintStatus)  ?.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