PreallocMethod (FIX tag 591)

charFIX 4.4

PreallocMethod (tag 591) is a char field defined in FIX 4.4. It appears in 10 message types, always optionally. It is an enumerated field with 2 defined values.

At a glance

Tag
591
Name
PreallocMethod
Datatype
char
Dialects
FIX 4.4
Messages
10
Valid values
2

What the specification says

Indicates the method of preallocation.

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

A real message using tag 591

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength117
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
591PreallocMethod0Pro-rata
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum003
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.

ValueMeaningSymbolic name
0Pro-rataPRO_RATA
1Do not pro-rata = discuss firstDO_NOT_PRO_RATA_DISCUSS_FIRST

Where tag 591 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.

MessageMsgTypeRequirednessWhere in the message
CrossOrderCancelReplaceRequesttOptionalinside the SideCrossOrdModGrp component
ExecutionReport8Optionaldirectly on the message body
MultilegOrderCancelReplaceACOptionaldirectly on the message body
NewOrderCrosssOptionalinside the SideCrossOrdModGrp component
NewOrderListEOptionalinside the ListOrdGrp component
NewOrderMultilegABOptionaldirectly on the message body
NewOrderSingleDOptionaldirectly on the message body
OrderCancelReplaceRequestGOptionaldirectly on the message body
TradeCaptureReportAEOptionalinside the TrdCapRptSideGrp component
TradeCaptureReportAckAROptionaldirectly on the message body

Wire format

A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.

Read tag 591 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 preallocMethod = message.fields[591]?.raw;// e.g. "0" — Pro-rata// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(591)  ?.enumValues?.find((e) => e.value === preallocMethod)  ?.description;

Other char fields

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