FIX Protocol Tag 281: MDReqRejReason
Reason a Market Data Request was rejected, such as unknown symbol or insufficient permissions.
- Tag number
- 281
- Data type
- CHAR
- FIX versions
- FIX 4.2 to 5.0 SP2
- Used in
- 1 message type
Tag 281 in each FIX version
Values and message usage as defined in a specific version.
Data type
CHAR: A single character.
Valid values
14 enumerated values across all FIX versions.
| Value | Meaning | FIX versions |
|---|---|---|
| 0 | Unknown symbol | All |
| 1 | Duplicate MDReqID | All |
| 2 | Insufficient bandwidth | All |
| 3 | Insufficient permissions | All |
| 4 | Unsupported subscription request type | All |
| 5 | Unsupported market depth | All |
| 6 | Unsupported MD update type | All |
| 7 | Unsupported aggregated book | All |
| 8 | Unsupported MD entry type | All |
| 9 | Unsupported trading session ID | 4.3, 4.4, 5.0, 5.0 SP1, 5.0 SP2 |
| C | Unsupported MD implicit delete | 4.3, 4.4, 5.0, 5.0 SP1, 5.0 SP2 |
| B | Unsupported open close settle flag | 4.3, 4.4, 5.0, 5.0 SP1, 5.0 SP2 |
| A | Unsupported scope | 4.3, 4.4, 5.0, 5.0 SP1, 5.0 SP2 |
| D | Insufficient credit | 5.0, 5.0 SP1, 5.0 SP2 |
Example
281=0
Illustrative value. In a message, fields are separated by the SOH character (0x01), often shown as | or ^ in logs.
Decode a message with this tagMessage types that use tag 281
Covers every version from FIX 4.0 to 5.0 SP2, including fields reached through components and repeating groups. The version pages above show whether the tag is required in each message.
Field and message data comes from the QuickFIX data dictionaries for FIX 4.0 to 5.0 SP2 and FIXT 1.1, used under the QuickFIX Software License. This product includes software developed by quickfixengine.org (http://www.quickfixengine.org/). Enumerated value names are converted to plain text for reading.