Imported from previous forum
Hi All,
Does FIX specify any restriction on the character lebgth for the values which are sent back in execution reports for tag 58 ?
Regards,
kashyap
Hi All,
Does FIX specify any restriction on the character lebgth for the values which are sent back in execution reports for tag 58 ?
Regards,
kashyap
As per FIX4.2,Tag#58 is string datatype and I don’t see any restriction, it depends on the mutual understing between th BUY side and SELL side that how much length will be processed.
Amiya.
[ original email was from John Greenan - john.greenan@alignment-systems.com ]
>
Hi All,
Does FIX specify any restriction on the character lebgth for the values which are sent back in execution reports for tag 58 ?
Regards,
kashyap
No, but…
If I was working for a sell-side I would add a configurable parameter about what length of characters I would allow to be sent to a buy-side.
There is at least one buy-side OMS with a hard code limit of 4000 characters in tag 58. 4001 characters will result in catastrophic system failure where the server has to be shut down and the pending transaction log manually amended to reduce to <4000.
I would also check that I was sending FIX compliant characters in tag 58. If you were working for a French or German firm you may see non-compliant accented letters. Best to check how to send these bearing in mind that you cannot really calculate a valid check sum in this case. There is another thread on here a while back I started about this - worth a look.
Most generally, code defensivly and expect your counterparties to be non-compliant…