We have a question regarding blank values during closing run in Elektron service. Basically, one of my client reported that in SSL, they get a 0 value for bid/ask/last on closing run for RIC such as ADEw.J and similar tickers. And, after investigation, we see that in our C++ RFA OMM we get blank values(using isBlank). We would like to confirm if it's the case and what is expected user way of handling a blank ?
For fields that are doubles, what does blank value interpret as ? Should we ignore it, or should we set it to 0 ?
Similarly, for string values, what does blank value mean ? Should it be ignored or set to empty string?
I believe that the value you recieved in both application should represent the same blank value. Basically the closing run is a housekeeping exercise performed by Thomson Reuters generally at the end of the day or some specific time depending on data specification, which prepares the display template for the next trading session. The last trade is moved to historical close and bid, ask and last prices may be cleared.
Actually in Marketfeed data transfer to the wire as string or text regardless of field type. So what the application received into a field of type PRICE is really just text.
In OMM RWF world there's native support for blank values by checking isBlank whereas in Marketfeed it has to use "+0" or "0" to represent blank values and "-0" represent zero value.Blank value in OMM is the indication of an empty or null data and no value is currently present.Any previously stored or displayed value should be cleared. The contents of the data should be ignored; any display or calculation should treat the value as blank or null. Thus the application should not apply data processing when receiving blank value.
-For fields that are double, display value depending on your display logic, you may reset it to 0 or shows other message like "<blank>" instead.
-For string value, Blank is output as an empty zero length string.