If a user connected via the MarketFeed protocol (port 8101) contributes the value zero "0" to ATS, the subscriber application over the same protocol receives a null value "N/A" instead of the real zero "0".
We could notice that if the subscriber application is Eikon 4 Excel, it is able to handle the situation by converting the null value into zero "0". RFA API is the tool being affected by this issue.
If the value zero "0" contributed to ATS comes from OMM protocol (port 14002), no problem is found, regardless if it's RFA API over port 8101 or Eikon via port 14002.
Does anyone know if this is a known issue with ATS?