PegRoundDirection (FIX tag 838)

intFIX 4.4

PegRoundDirection (tag 838) is an int field defined in FIX 4.4. It appears in 8 message types, always optionally. It is an enumerated field with 2 defined values.

At a glance

Tag: 838
Name: PegRoundDirection
Datatype: int
Dialects: FIX 4.4
Messages: 8
Valid values: 2

What the specification says

If the calculated peg price is not a valid tick price, specifies whether to round the price to be more or less aggressive

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

A real message using tag 838

NewOrderSingle · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	117
35	MsgType	D	Order – Single
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
838	PegRoundDirection	1	More aggressive – on a buy order round the price up to the nearest tick, on a sell round down to the nearest tick
10	CheckSum	008

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	More aggressive – on a buy order round the price up to the nearest tick, on a sell round down to the nearest tick	MORE_AGGRESSIVE_ON_A_BUY_ORDER_ROUND_THE_PRICE_UP_ROUND_UP_TO_THE_NEAREST_TICK_ON_A_SELL_ROUND_DOWN_TO_THE_NEAREST_TICK
2	More passive – on a buy order round down to nearest tick on a sell order round up to nearest tick	MORE_PASSIVE_ON_A_BUY_ORDER_ROUND_DOWN_TO_NEAREST_TICK_ON_A_SELL_ORDER_ROUND_UP_TO_NEAREST_TICK

Where tag 838 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
CrossOrderCancelReplaceRequest	t	Optional	inside the PegInstructions component
ExecutionReport	8	Optional	inside the PegInstructions component
MultilegOrderCancelReplace	AC	Optional	inside the PegInstructions component
NewOrderCross	s	Optional	inside the PegInstructions component
NewOrderList	E	Optional	inside ListOrdGrp › PegInstructions
NewOrderMultileg	AB	Optional	inside the PegInstructions component
NewOrderSingle	D	Optional	inside the PegInstructions component
OrderCancelReplaceRequest	G	Optional	inside the PegInstructions 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 838 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 pegRoundDirection = message.fields[838]?.raw;// e.g. "1" — More aggressive – on a buy order round the price up to the nearest tick, on a sell round down to the nearest tick// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(838)  ?.enumValues?.find((e) => e.value === pegRoundDirection)  ?.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