AllowableOneSidednessPct (FIX tag 765)
AllowableOneSidednessPct (tag 765) is a Percentage field defined in FIX 4.4. It appears in 1 message type, always optionally.
At a glance
- Tag
- 765
- Name
- AllowableOneSidednessPct
- Datatype
- Percentage (float)
- Dialects
- FIX 4.4
- Messages
- 1
What the specification says
The maximum percentage that execution of one side of a program trade can exceed execution of the other.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 765
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 122 | |
| 35 | MsgType | E | Order – List |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 66 | ListID | EXAMPLE | |
| 394 | BidType | 1 | "Non Disclosed" Style (e.g. US/European) |
| 765 | AllowableOneSidednessPct | 0.05 | |
| 68 | TotNoOrders | 1 | |
| 73 | NoOrders1 entry | 1 | repeating group |
| 11 | ClOrdID | ORD-10042 | |
| 67 | ListSeqNo | 1 | |
| 54 | Side | 1 | Buy |
| 10 | CheckSum | 106 |
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.
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.
Where tag 765 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 |
|---|---|---|---|
| NewOrderList | E | Optional | directly on the message body |
Wire format
A decimal rate where 1.0 means 100%, not 1%. @boarteam/fix parses the value as a number and reports parse/invalid-float when it does not lex as one; the raw string is kept so precision and trailing zeros are never lost.
Read tag 765 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[765];field?.name; // "AllowableOneSidednessPct"field?.raw; // the verbatim wire stringfield?.value; // coerced to a numberOther Percentage fields
- 849ParticipationRate
- 869PctAtRisk
- 634OfferYield
- 633MidYield
- 632BidYield
- 898MarginRatio
- 615LegCouponRate
- 516OrderPercent
- 512DistribPercentage
- 435UnderlyingCouponRate
- 413CrossPercent
- 410WtAverageLiquidity
- 407OutsideIndexPct
- 405EFPTrackingError
- 403LiquidityPctHigh
- 402LiquidityPctLow
- 252LegRepurchaseRate
- 245UnderlyingRepurchaseRate
- 236Yield
- 227RepurchaseRate
- 223CouponRate
- 158AccruedInterestRate
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