FIX TAG 427
GTBookingInst
Definition
Code to identify whether to book out executions on a part-filled GT order on the day of execution or to accumulate.
Compare versions
Differences between the selected source snapshots, including wording and errata; not a migration guide.
FIX 4.4 FIX 5.0 SP2
Definition text changed
FIX 4.4
Code to identify whether to book out executions on a part-filled GT order on the day of execution or to accumulate
FIX 5.0 SP2
Code to identify whether to book out executions on a part-filled GT order on the day of execution or to accumulate.
Value text or deprecation changed 3
| Value | FIX 4.4 | FIX 5.0 SP2 |
|---|---|---|
0 | book out all trades on day of execution | Book out all trades on day of execution |
1 | accumulate executions until order is filled or expires | Accumulate executions until order is filled or expires |
2 | accumulate until verbally notified otherwise | Accumulate until verbally notified otherwise |
Values 3
About the int data type
Sequence of digits without commas or decimals and optional sign character (ASCII characters "-" and "0" - "9" ). The sign character utilizes one byte (i.e. positive int is "99999" while negative int is "-99999"). Note that int values may contain leading zeros (e.g. "00023" = "23"). Examples: 723 in field 21 would be mapped int as |21=723|. -723 in field 12 would be mapped int as |12=-723| The following data types are based on int.
Used in messages 8
Includes nested components and repeating groups. Open a location to see its surrounding requirements.
35=8ExecutionReportMessage body35=DNewOrderSingleMessage body35=ENewOrderListListOrdGrp35=GOrderCancelReplaceRequestMessage body35=sNewOrderCrossMessage body35=tCrossOrderCancelReplaceRequestMessage body35=ABNewOrderMultilegMessage body35=ACMultilegOrderCancelReplaceMessage body