PosReqResult (FIX tag 728)

intFIX 4.4FIX 5.0 SP2

PosReqResult (tag 728) is an int field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 2 message types and is required in 2 of them. It is an enumerated field with 6 defined values.

At a glance

Tag: 728
Name: PosReqResult
Datatype: int
Dialects: FIX 4.4 and FIX 5.0 SP2
Messages: 2
Valid values: 6

What the specification says

FIX 4.4

Result of Request for Position 4000+ Reserved and available for bi-laterally agreed upon user-defined values

FIX 5.0 SP2

Result of Request for Positions.

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

A real message using tag 728

PositionReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	180
35	MsgType	AP	Position Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
721	PosMaintRptID	EXAMPLE
728	PosReqResult	0	Valid Request
715	ClearingBusinessDate	20240101
1	Account	ACCT-11223
581	AccountType	1	Account is carried on customer Side of Books
730	SettlPrice	1.09210
731	SettlPriceType	1	Final
734	PriorSettlPrice	1.09210
711	NoUnderlyings1 entry	1	repeating group
311	UnderlyingSymbol	EXAMPLE
732	UnderlyingSettlPrice	1.09210
733	UnderlyingSettlPriceType	1
10	CheckSum	240

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	Valid Request	VALID_REQUEST
1	Invalid or unsupported Request	INVALID_OR_UNSUPPORTED_REQUEST
2	No positions found that match criteria	NO_POSITIONS_FOUND_THAT_MATCH_CRITERIA
3	Not authorized to request positions	NOT_AUTHORIZED_TO_REQUEST_POSITIONS
4	Request for Position not supported	REQUEST_FOR_POSITION_NOT_SUPPORTED
99	Other (use Text(58) in conjunction with this code for an explanation)	OTHER

Where tag 728 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 5.0 SP2	Where in the message
PositionReport	AP	Required	Optional	directly on the message body
RequestForPositionsAck	AO	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 728 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 posReqResult = message.fields[728]?.raw;// e.g. "0" — Valid Request// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(728)  ?.enumValues?.find((e) => e.value === posReqResult)  ?.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