OrdStatus (FIX tag 39)
OrdStatus (tag 39) is a char field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 4 message types and is required in 3 of them. It is an enumerated field with 14 defined values.
At a glance
- Tag
- 39
- Name
- OrdStatus
- Datatype
- char
- Dialects
- FIX 4.4, FIX 4.2 and FIX 5.0 SP2
- Messages
- 4
- Valid values
- 14
What the specification says
FIX 4.4
Identifies current status of order. *** SOME VALUES HAVE BEEN REPLACED - See "Replaced Features and Supported Approach" *** (see Volume : "Glossary" for value definitions)
FIX 4.2
Identifies current status of order.
FIX 5.0 SP2
Identifies current status of order. *** SOME VALUES HAVE BEEN REPLACED - See "Replaced Features and Supported Approach" *** (see Volume : "Glossary" for value definitions)
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 39
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 113 | |
| 35 | MsgType | 9 | Order Cancel Reject |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 37 | OrderID | ORD-10042 | |
| 11 | ClOrdID | ORD-10042 | |
| 41 | OrigClOrdID | ORD-10041 | |
| 39 | OrdStatus | 0 | New |
| 434 | CxlRejResponseTo | 1 | Order Cancel Request |
| 10 | CheckSum | 204 |
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.
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 | Dialects |
|---|---|---|---|
| 0 | New | NEW / New | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| 1 | Partially filled | PARTIALLY_FILLED / PartiallyFilled | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| 2 | Filled | FILLED / Filled | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| 3 | Done for day | DONE_FOR_DAY / DoneForDay | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| 4 | Canceled | CANCELED / Canceled | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| 6 | Pending Cancel (e.g. result of Order Cancel Request) | PENDING_CANCEL / PendingCancel | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| 7 | Stopped | STOPPED / Stopped | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| 8 | Rejected | REJECTED / Rejected | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| 9 | Suspended | SUSPENDED / Suspended | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| A | Pending New | PENDING_NEW / PendingNew | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| B | Calculated | CALCULATED / Calculated | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| C | Expired | EXPIRED / Expired | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| D | Accepted for bidding | ACCEPTED_FOR_BIDDING / AcceptedForBidding | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| E | Pending Replace (e.g. result of Order Cancel/Replace Request) | PENDING_REPLACE / PendingReplace | FIX 4.4, FIX 4.2, FIX 5.0 SP2 |
| 5 | Replaced | Replaced / REPLACED | FIX 4.2, FIX 5.0 SP2 |
Where tag 39 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 | FIX 4.4 | FIX 4.2 | FIX 5.0 SP2 | Where in the message |
|---|---|---|---|---|---|
| ExecutionReport | 8 | Required | Required | Required | directly on the message body |
| ListStatus | N | Required | Required | Required | inside the OrdListStatGrp component |
| OrderCancelReject | 9 | Required | Required | Required | directly on the message body |
| TradeCaptureReport | AE | Optional | — | Optional | directly on the message body |
| TradeCaptureReportAck | AR | — | — | Optional | inside TrdCapRptAckSideGrp › TradeReportOrderDetail |
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 39 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 ordStatus = message.fields[39]?.raw;// e.g. "0" — New// The dictionary also carries the labels:const label = fix.dictionary .fieldByTag(39) ?.enumValues?.find((e) => e.value === ordStatus) ?.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