StreamAsgnRejReason (FIX tag 1502)
StreamAsgnRejReason (tag 1502) is an int field defined in FIX 5.0 SP2. It appears in 2 message types, always optionally. It is an enumerated field with 5 defined values.
At a glance
- Tag
- 1502
- Name
- StreamAsgnRejReason
- Datatype
- int
- Dialects
- FIX 5.0 SP2
- Messages
- 2
- Valid values
- 5
What the specification says
Reason code for stream assignment request reject.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1502
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 91 | |
| 35 | MsgType | CE | StreamAssignmentReportACK |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 1503 | StreamAsgnAckType | 0 | Assignment Accepted |
| 1501 | StreamAsgnRptID | EXAMPLE | |
| 1502 | StreamAsgnRejReason | 0 | Unknown client |
| 10 | CheckSum | 211 |
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 5.0 SP2 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 |
|---|---|---|
| 0 | Unknown client | UNKNOWN_CLIENT |
| 1 | Exceeds maximum size | EXCEEDS_MAXIMUM_SIZE |
| 2 | Unknown or Invalid currency pair | UNKNOWN_OR_INVALID_CURRENCY_PAIR |
| 3 | No available stream | NO_AVAILABLE_STREAM |
| 99 | Other | OTHER |
Where tag 1502 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 |
|---|---|---|---|
| StreamAssignmentReport | CD | Optional | inside StrmAsgnRptGrp › StrmAsgnRptInstrmtGrp |
| StreamAssignmentReportACK | CE | Optional | directly on the message body |
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 1502 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const streamAsgnRejReason = message.fields[1502]?.raw;// e.g. "0" — Unknown client// The dictionary also carries the labels:const label = fix.dictionary .fieldByTag(1502) ?.enumValues?.find((e) => e.value === streamAsgnRejReason) ?.description;Other int fields
- 1503StreamAsgnAckType
- 1498StreamAsgnReqType
- 1490ComplexEventCondition
- 1489ComplexEventPriceTimeType
- 1487ComplexEventPriceBoundaryMethod
- 1484ComplexEventType
- 1482OptPayoutType
- 1481UnderlyingPriceDeterminationMethod
- 1479StrikePriceBoundaryMethod
- 1478StrikePriceDeterminationMethod
- 1477NewsRefType
- 1473NewsCategory
- 1471SecurityListTypeSource
- 1470SecurityListType
- 1464TargetPartyRole
- 1447RateSourceType
- 1446RateSource
- 1444SideLiquidityInd
- 1443FillLiquidityInd
- 1442DerivativeFlowScheduleType
- 1441UnderlyingFlowScheduleType
- 1440LegFlowScheduleType
- 1439FlowScheduleType
- 1438DerivativeContractMultiplierUnit
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-fix50sp2