FIX Protocol Tag 386: NoTradingSessions
Number of trading sessions in the repeating group.
- Tag number
- 386
- Data type
- NUMINGROUP
- FIX versions
- FIX 4.2 to 5.0 SP2
- Used in
- 13 message types
Tag 386 in each FIX version
Values and message usage as defined in a specific version.
Data type
NUMINGROUP: A positive integer giving the number of entries in the repeating group that follows.
Example
386=2
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 386
- New Order Single 35=D
- New Order List 35=E
- Order Cancel/Replace Request 35=G
- Market Data Request 35=V
- New Order Multileg 35=AB
- Multileg Order Cancel/Replace 35=AC
- Position Maintenance Request 35=AL
- Position Maintenance Report 35=AM
- Request For Positions 35=AN
- Trading Session List 35=BJ
- Trading Session List Update Report 35=BS
- 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.