What does blank value during closing run interpret as?

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?
Best Answer
-
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.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛