FIX Protocol Tag 168: EffectiveTime
Time the details in the message take effect, in UTC.
- Tag number
- 168
- Data type
- UTCTIMESTAMP
- FIX versions
- FIX 4.1 to 5.0 SP2
- Used in
- 11 message types
Tag 168 in each FIX version
Values and message usage as defined in a specific version.
Data type
UTCTIMESTAMP: Date and time in UTC as YYYYMMDD-HH:MM:SS, optionally followed by fractions of a second (.sss).
Example
168=20261020-14:30:05.123
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 168
- Execution Report 35=8
- New Order Single 35=D
- New Order List 35=E
- Order Cancel/Replace Request 35=G
- Settlement Instructions 35=T
- New Order Multileg 35=AB
- Multileg Order Cancel/Replace 35=AC
- Settlement Instruction Request 35=AV
- Settlement Obligation Report 35=BQ
- New Order Cross 35=s
- Cross Order Cancel Replace Request 35=t
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.