FIX Drop Copy Specificationfor Bonds
Version 1.4
Updated 1 April 2020

1.

Introduction .................................................................................................................................. 1

2.

Overview ...................................................................................................................................... 1

3.

Service Configuration .................................................................................................................. 1

4.

FIX Protocol ................................................................................................................................. 4

5.

4.1.

Data Types and Required Fields ............................................................................................ 4

4.2.

Limitations............................................................................................................................. 4

Protocol Mappings ....................................................................................................................... 5
5.1.

FIX Order Entry .................................................................................................................... 5

5.2.

OUCH Order Entry ............................................................................................................... 56.

FIX Session Management ............................................................................................................ 67.

FIX Messages ............................................................................................................................... 6
7.1.

Standard Header – Incoming Messages ................................................................................ 6

7.2.

Standard Header – Outgoing Messages................................................................................. 7

7.3.

Standard Trailer ..................................................................................................................... 7

7.4.

Administrative Messages ...................................................................................................... 7

7.4.1.

Logon ............................................................................................................................. 7

7.4.2.

Heartbeat ........................................................................................................................ 8

7.4.3.

Test Request ................................................................................................................... 8

7.4.4.

Resend Request .............................................................................................................. 8

7.4.5.

Reject ............................................................................................................................. 8

7.4.6.

Sequence Reset .............................................................................................................. 9

7.4.7.

Logout ............................................................................................................................ 9

7.5.

8.

Application Messages............................................................................................................ 9

7.5.1.

Execution Report – Order Accepted .............................................................................. 9

7.5.2.

Execution Report – Order Replaced ............................................................................ 11

7.5.3.

Execution Report – Order Canceled ............................................................................ 12

7.5.4.

Execution Report – Trade ............................................................................................ 13

7.5.5.

Business Message Reject ............................................................................................. 15

Revision History ........................................................................................................................ 15

FIX Drop Copy Specification for Bonds

2020-04-01

1. Introduction
This document explains access to the bonds drop copy services of Japannext PTS via the FIX protocol. It
describes the service's configuration and specifies the messages that can be received via subscription. For
further information and inquiries regarding drop copy services or for questions concerning connectivity
please contact Japannext PTS Technical Support via email to: ito@japannext.co.jp.

2. Overview
The drop copy service is designed to deliver real-time information about trading activity taking place at
Japannext PTS and can be configured to send a message any time an order is entered, modified, canceled or
executed. The service can be integrated for straight through processing (STP) into a client's risk management
and settlement systems (see Figure 1).

Figure 1: Drop copy integration
The TCP/IP protocol is used for the point-to-point transport layer.

3. Service Configuration
The drop copy service can be configured to deliver copies of transactions based on a combination of order
entry port identifier, security group identifier and client reference.
Two subscription types are available:•

Reconciliation, consisting of only trade-related transactions.

•

Full, consisting of both order and trade-related transactions.

The ClientID field can be configured to indicate the origin of an order with the following information:•

Order entry port identifier.

•Trade group identifier to which the order entry port belongs.

•

Both of the above.

As an example, consider an institution with a trading facility which uses two order entry ports providing

1

FIX Drop Copy Specification for Bonds

2020-04-01

access to Japannext PTS for three trade groups (see Figure 2).

Figure 2: Trading flow
There are two typical use cases of the drop copy service, back office processing and risk management.
Usually a back office specific configuration includes copies of all trade reports for all trade groups (seeFigure 3).

Figure 3: Back office specific flow
Whereas a risk management's scope of interest is more narrow, focusing only on particular trade groups,

2

FIX Drop Copy Specification for Bonds

2020-04-01

however is more detailed in that it includes all transactions (see Figure 4).

Figure 4: Risk management specific flow

4. FIX Protocol
The messaging described in this specification complies to the standard FIX 4.2 protocol. For details pleaserefer to http://www.fixprotocol.org/specifications/FIX.4.2.
This specification follows the standard FIX specification as much as possible. However, in limited cases
fields and field values have been extended by backporting from the FIX 4.4 specification.

4.1. Data Types and Required Fields
Field data types in this specification are the same as those defined in the standard FIX specification.
However, in certain places this specification further restricts field values from those specified in the standard.
All field values will be stated in the message specification details.
Fields that are marked as required in the standard FIX specification are also marked as required in thisspecification, denoted 'Y' in the message definitions. Additionally required fields by this specification are
denoted 'R'.

4.2. Limitations
This specification applies limitations on particular field lengths.
Tag

Field Name

Data Type

Comments

1

Account

StringLimited to 10 characters.

6

AvgPx

Price

Limited to 6 whole number digits and 6 decimal places.

11

ClOrdID

StringLimited to 32 characters.

14

CumQtyQty

Limited to 9 whole number digits.

17

ExecID

StringLimited to 20 characters.

31

LastPxPrice

Limited to 6 whole number digits and 3 decimal places.

3

FIX Drop Copy Specification for Bonds
Tag

Field Name

Data Type

2020-04-01

Comments

32

LastShares

Qty

Limited to 9 whole number digits.

37

OrderID

StringLimited to 20 characters.

38

OrderQty

Qty

Limited to 9 whole number digits.

41

OrigClOrdID

StringLimited to 32 characters.

44

Price

Price

Limited to 6 whole number digits and 3 decimal places.

50

SenderSubID

StringLimited to 4 characters for outgoing messages.

55

SymbolStringLimited to 9 digits.

109

ClientID

StringLimited to 30 characters.

110

MinQtyQty

Limited to 9 whole number digits.

151

LeavesQty

Qty

Limited to 9 whole number digits.

375

ContraBroker

StringLimited to 12 characters

880

TrdMatchID

StringLimited to 20 characters.

5. Protocol Mappings
This section defines mappings from the order entry protocols used in the trading services of Japannext PTS
to the drop copy protocol.

5.1. FIX Order Entry
Fields in the drop copy messages match the original trading messages with the following exceptions.
In the original messages the ClientID field contains the firm identifier (MPID), whereas in the drop copy
messages this field contains the order entry port and/or trade group identifiers (see Service Configuration).
Since a drop copy session can deliver messages aggregated from multiple order entry ports, the subscriber
should not rely solely on the ClOrdID field to uniquely identify orders. Augmenting the ClOrdID with anappropriately configured ClientID can be used for this purpose.
If the original message has the TimeInForce field with value 4 = Fill or Kill (FOK) then the drop copy
message will have the TimeInForce field with value 3 = Immediate or Cancel (IOC) and the MinQty fieldwith value equal to the OrderQty field's value.
The ExecID assigned to a drop copy message will differ from that of the original message. Uniqueness of
this field is only guaranteed per individual drop copy session.

5.2. OUCH Order Entry
Fields in the drop copy messages match the original trading messages with the following exceptions.
In the original messages the ClientID (Firm) field contains the firm identifier (MPID), whereas in the drop
copy messages this field contains the order entry port and/or trade group identifiers (see Service
Configuration.)
Since a drop copy session can deliver messages aggregated from multiple order entry ports, the subscriber
should not rely solely on the ClOrdID (Order Token) field to uniquely identify orders. Augmenting the
ClOrdID (Order Token) with an appropriately configured ClientID can be used for this purpose.
Uniqueness of the ExecID field is only guaranteed per individual drop copy session.
FIX and OUCH field mappings are defined below.

4FIX Drop Copy Specification for Bonds
Tag
11

Field Name
ClOrdID

2020-04-01

OUCH Field Name
Order Token
Replacement Order Token

1

Account

Client Reference

54

Side

Buy/Sell Indicator

38

OrderQty

Quantity

55

SymbolOrderbook Id

50

SenderSubID

Group

44

Price

Yield

59

TimeInForce

Time in Force

109

ClientID

Firm Id

47

Rule80A

Capacity

37

OrderID

Order Number

110

MinQtyMinimum Quantity

41

OrigClOrdID

Previous Order Token

378

ExecRestatementReason Canceled Order Reason

32

LastShares

Executed Quantity

31

LastPxExecution Yield

375

ContraBroker

Counter Party

851

LastLiquidityInd

Liquidity Indicator880

TrdMatchID

Match Number

8060 OrderClassification

Order Classification

6. FIX Session Management
FIX sessions are uniquely defined by the SenderCompID and TargetCompID. Any attempt to establish an
additional FIX session using the same SenderCompID and TargetCompID will be rejected.
At log on clients are identified by their SenderCompID.
Clients are required to log on to the service using the log on message. Once logged on, clients will need tosend heartbeat messages to keep the session active.
In case of connection loss clients are required to again log on using the next transmitted sequence numbers
while also taking care of any potential message loss in a FIX protocol compliant manner.
IP addresses, port numbers and CompIDs to use are issued upon application completion.

7. FIX Messages
7.1. Standard Header – Incoming Messages
Tag

Field Name

Data Type Req’d

Comments

8

BeginString

StringY

Identifies beginning of new message and protocol version. Always first
field in message. Value is FIX.4.2.

9

BodyLengthintY

Message length, in bytes, forward to the CheckSum (10) field. Always
second field in message.

35

MsgType

StringY

Defines message type. Always third field in message.

5

FIX Drop Copy Specification for Bonds
Tag

Field Name

Data Type Req’d
Y

2020-04-01

Comments

34

MsgSeqNum

int

Integer message sequence number.

43

PossDupFlag

Boolean49

SenderCompID

String

52

SendingTimeUTC
YTimestamp

Time of message transmission (always expressed in UTC).

56

TargetCompID

StringUsed to identify receiving firm. As assigned by Japannext PTS.

122

OrigSendingTime

UTCTimestamp

Indicates possible re transmission of message with this sequence number.
Values:Y = Possible duplicate
N = Original transmission
Y

Y

Used to identify firm sending message. As assigned by Japannext PTS.

Original time of message transmission (always expressed in UTC).

7.2. Standard Header – Outgoing Messages
Tag

Field Name

Data Type Req’d

Comments

8

BeginString

StringY

Identifies beginning of new message and protocol version. Always first
field in message. Value is FIX.4.2.

9

BodyLengthintY

Message length, in bytes, forward to the CheckSum (10) field. Always
second field in message.

35

MsgType

StringY

Defines message type. Always third field in message.

34

MsgSeqNum

int

Y

Integer message sequence number.

49

SenderCompID

StringY

Used to identify firm sending message. As assigned by Japannext PTS.

50

SenderSubID

StringAssigned value used to identify specific message originator.
Values:DJGB = JGB Market

52

SendingTimeUTC
YTimestamp

Time of message transmission (always expressed in UTC).

56

TargetCompID

StringUsed to identify receiving firm. As assigned by Japannext PTS.

122

OrigSendingTime

UTCTimestamp

Y

Original time of message transmission (always expressed in UTC).

7.3. Standard Trailer
Tag
10

Field Name
CheckSum

Data Type Req’d
StringY

Comments
Three byte, simple checksum. Always defined as three characters. Always
last field in message.

7.4. Administrative Messages
7.4.1. Logon
Tag

Field Name

Standard header

Data Type Req’d

Comments
MsgType (35) = A

6

FIX Drop Copy Specification for Bonds
Tag

Field Name

Data Type Req’d

2020-04-01

Comments

98

EncryptMethod

intY

Method of encryption. Not supported.
Values:0 = None / other108

HeartBtInt

int

YHeartbeat interval (seconds). Recommended value is 30 seconds.

141

ResetSeqNumFlag

BooleanIndicates that both sides of the FIX session should reset sequence numbers.
Values:Y = Yes, reset sequence numbers
N = No553

Username

String

Userid. As assigned by Japannext PTS.

554

Password

StringPassword or passphrase. As assigned by Japannext PTS.

Standard trailer

7.4.2. Heartbeat
Tag

Field Name

Data Type Req’d

Standard header
112

TestReqID

Comments
MsgType (35) = 0

StringRequired when the heartbeat is the result of a Test Request message.

Standard trailer

7.4.3. Test Request
Tag

Field Name

Data Type Req’d

Standard header
112

TestReqID

Comments
MsgType (35) = 1

StringY

Identifier to be returned in resulting Heartbeat.

Standard trailer

7.4.4. Resend Request
Tag

Field Name

Data Type Req’d

Standard header

Comments
MsgType (35) = 2

7

BeginSeqNo

int

Y

Message sequence number of first message in range to be resent.

16

EndSeqNo

int

Y

Message sequence number of last message in range to be resent.

Standard trailer

7.4.5. Reject
Tag

Field Name

Data Type Req’d

Standard header

Comments
MsgType (35) = 3

45

RefSeqNum

int

Y

58

Text

StringMessage explaining reject reason.

371

RefTagIDint

The tag number of the FIX field being referenced.

372

RefMsgType

String

The MsgType (35) of the FIX message being referenced.

MsgSeqNum (34) of rejected message

7

FIX Drop Copy Specification for Bonds
Tag

Field Name

373

SessionRejectReason

Data Type Req’dint

2020-04-01

Comments
Code to identify reason for a session-level Reject message.
Values:0 = Invalid tag number
1 = Required tag missing
2 = Tag not defined for this message type
3 = Undefined tag
4 = Tag specified without a value
5 = Value is incorrect (out of range) for this tag
6 = Incorrect data format for value
9 = CompID problem
10 = SendingTime (52) accuracy problem
11 = Invalid MsgType (35)Standard trailer

7.4.6. Sequence Reset
Tag

Field Name

Data Type Req’d

Standard header

Comments
MsgType (35) = 4

36

NewSeqNo

int

123

GapFillFlag

BooleanY

New sequence number.
Indicates replacing administrative or application messages which will not be
resent.
Values:Y = Gap Fill message, MsgSeqNum (34) field valid
N = Sequence Reset, ignore MsgSeqNum (34)Standard trailer

7.4.7. Logout
Tag

Field Name

Data Type Req’d

Standard header
58

Text

Comments
MsgType (35) = 5

StringMessage explaining logout reason.

Standard trailer

7.5. Application Messages
7.5.1. Execution Report – Order Accepted
Tag

Field Name

Data Type Req’d

Standard header - Outgoing

Comments
MsgType (35) = 8

1

Account

StringAccount mnemonic as assigned by the institution.

6

AvgPx

Price

11

ClOrdID

String

14

CumQtyQty

Y

Total number of bonds filled.
Value is 0.

17

ExecID

StringY

Unique identifier of execution message as assigned by Japannext PTS.

20

ExecTransType

char

Y

Identifies transaction type.
Values:0 = NewY

Calculated average yield of all fills on this order.
Value is 0.
Unique identifier for the order as assigned by the institution.

8

FIX Drop Copy Specification for Bonds
Tag

Field Name

Data Type Req’d

2020-04-01

Comments

37

OrderID

StringY

Unique identifier for order as assigned by Japannext PTS.

38

OrderQty

Qty

R

Quantity accepted.

39

OrdStatuscharY

Identifies current status of this order.
Values:0 = New

40

OrdTypechar

ROrder type.
Values:2 = Limit

44

Price

Price

R

Price per bond.

47

Rule80A

char

R

Designates the capacity of the firm placing the order.
Values:A = Agency
P = Principal

54

Side

char

Y

Side of order.
Values:1 = Buy
2 = Sell

55

SymbolStringY

Ticker symbol.
Value is the bond code per SICC definition.

59

TimeInForce

char

R

Specifies how long the order remains in effect.
Values:0 = Day
3 = Immediate or Cancel (IOC)60TransactTime

UTC
R
Timestamp

Time the transaction represented by this message occurred.

109

ClientID

StringOrder entry port and/or trade group identifiers as assigned by Japannext
PTS.

110

MinQtyQty

Minimum quantity of an order to be executed.

150

ExecTypechar

Y

Describes the specific Execution Report.
Values:0 = New

151

LeavesQty

Qty

YAmount of bonds open for further execution.
Value is the same as that of OrderQty (38).

423

PriceTypeint

R

Code to represent the price type.
Values:
9 = Yield

797

CopyMsgIndicator

BooleanR

Indicates whether or not this message is a drop copy of another message.
Value is Y = Yes

8060

OrderClassification

char

R

High Frequency Trading (HFT) order classification.
Values:
1 = Non HFT
3 = HFT market making strategy
4 = HFT arbitrage strategy
5 = HFT directional strategy
6 = HFT other strategy

Standard trailer

9

FIX Drop Copy Specification for Bonds

2020-04-01

7.5.2. Execution Report – Order Replaced
Tag

Field Name

Data Type Req’d

Standard header - Outgoing

Comments
MsgType (35) = 8

1

Account

StringAccount mnemonic as assigned by the institution.

6

AvgPx

Price

11

ClOrdID

String

14

CumQtyQty

Y

Total number of bonds filled.

17

ExecID

StringY

Unique identifier of execution message as assigned by Japannext PTS.

20

ExecTransType

char

Y

Identifies transaction type.
Values:0 = New

37

OrderID

StringY

Unique identifier for order as assigned by Japannext PTS.

38

OrderQty

Qty

R

Quantity accepted.

39

OrdStatuscharY

Identifies current status of this order.
Values:
1 = Partially filled
2 = Filled
5 = Replaced40

OrdTypechar

ROrder type.
Values:2 = Limit

41

OrigClOrdID

StringR

ClOrdID (11) of the previous order (not the initial order) as assigned by theinstitution.

44

Price

Price

47

Rule80A

char

R

Designates the capacity of the firm placing the order.
Values:A = Agency
P = Principal

54

Side

char

Y

Side of order.
Values:1 = Buy
2 = Sell

55

SymbolStringY

Ticker symbol.
Value is the bond code per SICC definition.

59

TimeInForce

char

R

Specifies how long the order remains in effect.
Values:0 = Day
3 = Immediate or Cancel (IOC)60TransactTime

UTC
R
Timestamp

Time the transaction represented by this message occurred.

109

ClientID

StringOrder entry port and/or trade group identifiers as assigned by Japannext
PTS.

110

MinQtyQty

Minimum quantity of an order to be executed.

150

ExecTypechar

Y

Describes the specific Execution Report.
Values:5 = Replaced

151

LeavesQty

Qty

YAmount of bonds open for further execution.

378

ExecRestatement
Reasonint

Y

Code to identify reason for unsolicited cancel.
Values:100 = Trade preventionY

Calculated average price of all fills on this order.
Unique identifier for the order as assigned by the institution.

Price per bond.

10

FIX Drop Copy Specification for Bonds
Tag

Field Name

Data Type Req’d

2020-04-01

Comments

423

PriceTypeint

R

Code to represent the price type.
Values:
9 = Yield

797

CopyMsgIndicator

BooleanR

Indicates whether or not this message is a drop copy of another message.
Value is Y = Yes

8060

OrderClassification

char

R

High Frequency Trading (HFT) order classification.
Values:
1 = Non HFT
3 = HFT market making strategy
4 = HFT arbitrage strategy
5 = HFT directional strategy
6 = HFT other strategy

Standard trailer

7.5.3. Execution Report – Order Canceled
Tag

Field Name

Data Type Req’d

Standard header - Outgoing

Comments
MsgType (35) = 8

1

Account

StringAccount mnemonic as assigned by the institution.

6

AvgPx

Price

11

ClOrdID

String

14

CumQtyQty

Y

Total number of bonds filled.

17

ExecID

StringY

Unique identifier of execution message as assigned by Japannext PTS.

20

ExecTransType

char

Y

Identifies transaction type.
Values:0 = New

37

OrderID

StringY

Unique identifier for order as assigned by Japannext PTS.

38

OrderQty

Qty

R

Quantity accepted.

39

OrdStatuscharY

Identifies current status of this order.
Values:
4 = Canceled40

OrdTypechar

ROrder type.
Values:2 = Limit

41

OrigClOrdID

String

44

Price

Price

R

Price per bond.

47

Rule80A

char

R

Designates the capacity of the firm placing the order.
Values:A = Agency
P = Principal

54

Side

char

Y

Side of order.
Values:1 = Buy
2 = Sell

55

SymbolStringY

Ticker symbol.
Value is the bond code per SICC definition.

Y

Calculated average yield of all fills on this order.
Unique identifier for the order as assigned by the institution.

ClOrdID (11) of the previous order (not the initial order) as assigned by theinstitution.

11

FIX Drop Copy Specification for Bonds
Tag

Field Name

Data Type Req’d
R

2020-04-01

Comments

59

TimeInForcechar

Specifies how long the order remains in effect.
Values:0 = Day
3 = Immediate or Cancel (IOC)60TransactTime

UTC
R
Timestamp

Time the transaction represented by this message occurred.

109

ClientID

StringOrder entry port and/or trade group identifiers as assigned by Japannext
PTS.

110

MinQtyQty

Minimum quantity of an order to be executed.

150

ExecTypechar

Y

Describes the specific Execution Report.
Values:
4 = Canceled

151

LeavesQty

Qty

YAmount of bonds open for further execution.
Value is 0.

378

ExecRestatement
Reasonint

423

PriceTypeint

R

Code to represent the price type.
Values:
9 = Yield

797

CopyMsgIndicator

BooleanR

Indicates whether or not this message is a drop copy of another message.
Value is Y = Yes.

8060

OrderClassification

char

R

High Frequency Trading (HFT) order classification.
Values:
1 = Non HFT
3 = HFT market making strategy
4 = HFT arbitrage strategy
5 = HFT directional strategy
6 = HFT other strategy

Code to identify reason for unsolicited cancel.
Values:2 = Verbal change
7 = Cancel on System Failure
12 = Cancel on connection loss
99 = Other
100 = Trade prevention

Standard trailer

7.5.4. Execution Report – Trade
Tag

Field Name

Data Type Req’d

Standard header - Outgoing

Comments
MsgType (35) = 8

1

Account

StringAccount mnemonic as assigned by the institution.

6

AvgPx

Price

11

ClOrdID

String

14

CumQtyQty

Y

Total number of bonds filled.

17

ExecID

StringY

Unique identifier of execution message as assigned by Japannext PTS.

20

ExecTransType

Char

Y

Identifies transaction type.
Values:0 = New

31

LastPxPrice

R

Yield of this (last) fill.

32

LastShares

Qty

R

Quantity bought/sold on this (last) fill.

37

OrderID

StringY

Unique identifier for order as assigned by Japannext PTS.

Y

Calculated average yield of all fills on this order.
Unique identifier for the order as assigned by the institution.

12

FIX Drop Copy Specification for Bonds
Tag

Field Name

Data Type Req’d

2020-04-01

Comments

38

OrderQty

Qty

R

Quantity accepted.

39

OrdStatuscharY

Identifies current status of this order.
Values:
1 = Partially filled
2 = Filled

40

OrdTypechar

ROrder type.
Values:2 = Limit

44

Price

Price

R

Yield per bond.

47

Rule80A

char

R

Designates the capacity of the firm placing the order.
Values:A = Agency
P = Principal

54

Side

char

Y

Side of order.
Values:1 = Buy
2 = Sell

55

SymbolStringY

Ticker symbol.
Value is the bond code per SICC definition.

59

TimeInForce

char

R

Specifies how long the order remains in effect.
Values:0 = Day
3 = Immediate or Cancel (IOC)60TransactTime

UTC
R
Timestamp

Time the transaction represented by this message occurred.

109

ClientID

StringOrder entry port and/or trade group identifiers as assigned by Japannext
PTS.

110

MinQtyQty

Minimum quantity of an order to be executed.

150

ExecTypechar

Y

Describes the specific Execution Report.
Values:
1 = Partial fill
2 = Fill

151

LeavesQty

Qty

YAmount of bonds open for further execution.

375

ContraBroker

StringR

Used to identify the counter party of the trade.
Value is the PSMS code per JASDEC definition.

382

NoContraBroker

intR

The number of ContraBroker entries.
Value is 1.

423

PriceTypeint

R

Code to represent the price type.
Values:
9 = Yield

797

CopyMsgIndicator

BooleanR

Indicates whether or not this message is a drop copy of another message.
Value is Y = Yes.

851

LastLiquidityInd

intR

Indicator to identify whether this fill was a result of a liquidity provider
providing or liquidity taker taking the liquidity.
Values:1 = Added liquidity
2 = Removed liquidity880

TrdMatchID

StringR

Identifier assigned to a trade by a matching system.

13

FIX Drop Copy Specification for Bonds
Tag

Field Name

8060

OrderClassification

Data Type Req’dcharR

2020-04-01

Comments
High Frequency Trading (HFT) order classification.
Values:
1 = Non HFT
3 = HFT market making strategy
4 = HFT arbitrage strategy
5 = HFT directional strategy
6 = HFT other strategy

Standard trailer

7.5.5. Business Message Reject
Tag

Field Name

Data Type Req’d

Standard header - Outgoing

Comments
MsgType (35) = j

45

RefSeqNum

int

MsgSeqNum (34) of rejected message

58

Text

StringMessage explaining reject reason.

372

RefMsgType

StringY

The MsgType (35) of the FIX message being referenced.

380

BusinessRejectReason

int

Y

Code to identify reason for a Business Message Reject message.
Values:0 = Other
3 = Unsupported Message TypeStandard trailer

8. Revision History
Date

VersionChanges

2016-12-05 1.0

Initial revision.

2017-08-31 1.1

Decreased Account (1) field's length limitation from 16 to 10.
Decreased ExecID (17) field's length limitation from 30 to 20.
Decreased SenderSubID (50) field's length limitation from 10 to 4 for outgoing messages.
Removed TargetSubID (57) from field length limitations table.
Increased ClientID (109) field's length limitation from 20 to 30.
Added TrdMatchID (880) to field length limitations table with value 20.
Removed value 4 = Fill or Kill (FOK) from TimeInForce (59) field.

2017-12-05 1.2

Updated OUCH field names
Added Data Type column to message definition tables.
Added values for boolean fields.
Changed order of fields listed in header to group first three required fields.
Added parenthesized tag numbers to field names appearing in comments of message definition tables.

2018-04-05 1.3

Added OrderClassification (8060) field to Execution Report messages.

2020-04-01 1.4

Change company name.

14