How to decode Rmtes partial update data with EMA C++?
Our system was changed API from RFA C# 7.2.18 to EMA C++ 3.6.7.
It is possible that the decoding result is incorrect due to the difference in the way RFA and EMA handle RMTES encoding.
The following data shows the decoding results obtained using RFA and EMA, respectively.
RFA:
2023-09-14 17:48:35,610 ICAPEUROBASIS3 UPDATE 321=[60`3
EMA:
2023-09-14 17:48:35,610 ICAPEUROBASIS3 UPDATE 321=ICAK HKG60090 6.1250 -7.87501063 14/SEP 17:45
When investigating this issue, we found a similar question on the following link.
And we have 2 questions:
(1) whether this issue has already been resolved. If not, the question is whether there are any plans to resolve it in the future.
(2) Based on the content of the past article, the correct decoding results can be obtained by addressing the issue using the following method.If there are any improvements or alternative methods to address this issue, please let me know.
if ((FieldEntry.getEntry().getLoadType()) == DataType::RmtesEnum) {
EmaBuffer c = FieldEntry.getAsHex();
value = asciiTochar(c.asRawHexString());
}
Best Answer
-
Thank you for reaching out to us.
As mentioned on that discussion, please modify and run the 310_MarketPrice_RMTES example to replicate this issue. Your implementation may be different from the 310_MarketPrice_RMTES example.
Regarding the DataType::RmtesEnum, the examples use the following code to get an ENUM value.
case DataType::RmtesEnum:
cout << fe.getRmtes().toString() << endl;
break;0
Answers
-
Thank you for your answer and sorry for the delayed response. We have tested your answer, but the result did not meet my expectations. While we make the test program as 310_MarketPrice_RMTES sample, we were unable to obtain information for the update location.
Test Result: ICAPEUROBASIS3 UPDATE 321=3
Expected: ICAPEUROBASIS3 UPDATE 321=[60`3
And Our client in this matter plans to make a separate inquiry through Premium Support.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 162 App Studio
- 4 Block Chain
- 5 Bot Platform
- 17 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
- 370 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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛