What is the min/max numerical values and exponents I can submit in a REAL64 that will be successfull
I have a Non-Interactive Provider submitting live updates to our corporate RMDS infrastructure. These live updates are deltas and we rely on the ADH/ADS cache to supply the complete image when a consumer requests the instruments. This is fine but in some cases then the values exceed certain limits these values are not passed to the consumers in the initial image.
The RDM dictionary refines the MarketFeed type of the field as PRICE with size 17 and the RFW type as REAL64 with size 7. What are the limits of the values/exponents that can be placed into the REAL64 to have it successfully cached and overflow conditions can be detected and alerted/logged?
Best Answer
-
The RWF_LEN field in the RDMDictionary indicates the size of the field in caching. Be aware that throughout TREP 2.x series the symptoms of overflow have changed significantly, from ignoring, truncation and dropping the affected field in cache. Overflow is not recorded anywhere and UPA unfortunately does not contain any API for testing overflow.
For REAL fields consider 8-bits are used for exponent and the remainder for the fixed-point mantissa. Thus 7-byte field has a 6-byte mantissa of range from −(247) to 247 − 1.
ATS 1.4.1.E2 will truncate values, so publishing a BID of (9223372036854775807) will be truncated to (140737488355327).
In ADH/ADS 2.4.0.E2, if Real64 FID values do not fit in the RWF_LEN size defined by the dictionary, the values will be zeroed out. However, it won’t truncate or zero out the updates.
Note that the RWF_LEN sizes can be customized to cache the full field if desired, the provided values are only the minimums required for Elektron content.
The document FieldDictionary_Tool_24.pdf in ADH lists the cached significant digit sizes for appropriate lengths:
0
Answers
-
What is the parameter for RWF_LEN that can be used to make sure that ADH caches the full field? And in which file is it present?
0 -
Any update on my query please?0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛