FIX Protocol Tag 198: SecondaryOrderID
Additional order identifier assigned by the sell side.
- Tag number
- 198
- Data type
- STRING
- FIX versions
- FIX 4.1 to 5.0 SP2
- Used in
- 21 message types
Tag 198 in each FIX version
Values and message usage as defined in a specific version.
Data type
STRING: Text of printable characters. It cannot contain the SOH delimiter.
Example
198=ID-1001
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 198
- Execution Report 35=8
- Order Cancel Reject 35=9
- Allocation Instruction 35=J
- Dont Know Trade 35=Q
- Market Data Snapshot Full Refresh 35=W
- Market Data Incremental Refresh 35=X
- Trade Capture Report 35=AE
- Confirmation 35=AK
- Trade Capture Report Ack 35=AR
- Allocation Report 35=AS
- Collateral Request 35=AX
- Collateral Assignment 35=AY
- Collateral Response 35=AZ
- Collateral Report 35=BA
- Collateral Inquiry 35=BB
- Collateral Inquiry Ack 35=BG
- Confirmation Request 35=BH
- Allocation Instruction Alert 35=BM
- Execution Ack 35=BN
- Trade Match Report 35=DC
- Order Mass Cancel Report 35=r
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.