Imported from previous forum
I see that FIX protocol puts no restriction on the length of the tag 11 - clOrdId. But I have seen BATS exchange specification that says it should be under 20 characters. Is that correct? I did not find anything about other exchanges. What is the good practice? Thanks.
BMV (Mexican Stock Exchange) limits ClOrdID[11] to 40 alphanumeric characters. I would be surprised to find a exchange that doesn’t have a limit, even if it’s big (say 255 chars?)
FIX does not define any limits on string fields, ClOrdID included. This is left to the Rules of Engagement and depends on the receiving system and is often enough a trade off between flexibility (long field, arbitrary characters) and high performance (short field, numbers only). There cannot be a single “good practice” across all usage environments.
I see that FIX protocol puts no restriction on the length of the tag 11 - clOrdId. But I have seen BATS exchange specification that says it should be under 20 characters. Is that correct? I did not find anything about other exchanges. What is the good practice? Thanks.
Do you have any list of exchanges and their clOrdId specifications documented? or are they available any where on the web? Google did not bring up any. Thanks.
FIX does not define any limits on string fields, ClOrdID included. This is left to the Rules of Engagement and depends on the receiving system and is often enough a trade off between flexibility (long field, arbitrary characters) and high performance (short field, numbers only). There cannot be a single “good practice” across all usage environments.
I see that FIX protocol puts no restriction on the length of the tag 11 - clOrdId. But I have seen BATS exchange specification that says it should be under 20 characters. Is that correct? I did not find anything about other exchanges. What is the good practice? Thanks.
No, I would be interested and happy to get such a list…please post it 
Do you have any list of exchanges and their clOrdId specifications documented? or are they available any where on the web? Google did not bring up any. Thanks.
FIX does not define any limits on string fields, ClOrdID included. This is left to the Rules of Engagement and depends on the receiving system and is often enough a trade off between flexibility (long field, arbitrary characters) and high performance (short field, numbers only). There cannot be a single “good practice” across all usage environments.
I see that FIX protocol puts no restriction on the length of the tag 11 - clOrdId. But I have seen BATS exchange specification that says it should be under 20 characters. Is that correct? I did not find anything about other exchanges. What is the good practice? Thanks.
This is interesting – even we are 20 bytes.
No, I would be interested and happy to get such a list…please post it
Do you have any list of exchanges and their clOrdId specifications documented? or are they available any where on the web? Google did not bring up any. Thanks.
FIX does not define any limits on string fields, ClOrdID included. This is left to the Rules of Engagement and depends on the receiving system and is often enough a trade off between flexibility (long field, arbitrary characters) and high performance (short field, numbers only). There cannot be a single “good practice” across all usage environments.
I see that FIX protocol puts no restriction on the length of the tag 11 - clOrdId. But I have seen BATS exchange specification that says it should be under 20 characters. Is that correct? I did not find anything about other exchanges. What is the good practice? Thanks.