CollAction (FIX tag 944)

intFIX 4.4

CollAction (tag 944) is an int field defined in FIX 4.4. It appears in 3 message types, always optionally. It is an enumerated field with 3 defined values.

At a glance

Tag
944
Name
CollAction
Datatype
int
Dialects
FIX 4.4
Messages
3
Valid values
3

What the specification says

Action proposed for an Underlying Instrument instance

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

A real message using tag 944

CollateralResponse · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength167
35MsgTypeAZCollateral Response
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
904CollRespIDEXAMPLE
902CollAsgnIDEXAMPLE
895CollAsgnReason0Initial
905CollAsgnRespType0Received
60TransactTime20240101-12:00:00.000
711NoUnderlyings2 entries2repeating group
311UnderlyingSymbolEXAMPLE
944CollAction0Retain
311UnderlyingSymbolEXAMPLE
944CollAction0Retain
10CheckSum207
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
0RetainRETAIN
1AddADD
2RemoveREMOVE

Where tag 944 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
CollateralAssignmentAYConditionalinside the UndInstrmtCollGrp component
CollateralRequestAXConditionalinside the UndInstrmtCollGrp component
CollateralResponseAZConditionalinside the UndInstrmtCollGrp 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 944 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 collAction = message.fields[944]?.raw;// e.g. "0" — Retain// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(944)  ?.enumValues?.find((e) => e.value === collAction)  ?.description;

Other int 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