Skip to content
FIXtags

FIX TAG 844

DiscretionRoundDirection

intAdded FIX.4.4

Definition

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

Compare versions

Differences between the selected source snapshots, including wording and errata; not a migration guide.

FIX 4.4 FIX 5.0 SP2

Value text or deprecation changed 2

ValueFIX 4.4FIX 5.0 SP2
1More aggressive – on a buy order round the price up to the nearest tick, on a sell round down to the nearest tickMore aggressive - on a buy order round the price up to the nearest tick; on a sell round down to the nearest tick
2More passive – on a buy order round down to nearest tick on a sell order round up to nearest tickMore passive - on a buy order round down to the nearest tick; on a sell order round up to the nearest tick

Values 2

ValueMeaning
1

More aggressive - on a buy order round the price up to the nearest tick; on a sell round down to the nearest tick

2

More passive - on a buy order round down to the nearest tick; on a sell order round up to the nearest tick

About the int data type

Sequence of digits without commas or decimals and optional sign character (ASCII characters "-" and "0" - "9" ). The sign character utilizes one byte (i.e. positive int is "99999" while negative int is "-99999"). Note that int values may contain leading zeros (e.g. "00023" = "23"). Examples: 723 in field 21 would be mapped int as |21=723|. -723 in field 12 would be mapped int as |12=-723| The following data types are based on int.

Used in messages 8

Includes nested components and repeating groups. Open a location to see its surrounding requirements.