EMA C++ / Java: ToString error for 0#T7E:
The EMA toString method will report errors for the following RICs:
0#T7E:
0#OCB:
0#TIE:
Questions:
1. Is this by design? Looks like the root cause is from decoder?
2. Is there a 'toString' like method existing in EMA can cope with such case, that can output the message without error, then we may log the message received in log file.
=========================
C++:
Java:
1
Best Answer
-
I found invalid characters when subscribing to those RICs via Eikon Quote.
You may need to contact the Eikon content support team directly via MyRefinitiv to verify the content.
0
Answers
-
The test case is based on Consumer 100 example, just modified the RIC.
Actually the https://github.com/Refinitiv-API-Samples/Article.EMA.Java.ChainExpander example works for those RICs0 -
Hello @Frederic
What is the EMA/RTSDK version that encounters the issue? I have tested with RTSDK 2.0.3.L2 but I got "The record could not be found" error message from my internal service which means my service does not have 0#T7E, 0#OCB, and 0#TIE RICs.
Could you please clarify the second question? You can see more detail on how to log the EMA API and RSSL trace messages on the "Logger Configuration" and "EMA Java Logging" sections of the Enterprise Message API (EMA) - Configuration Overview article.
Additionally, if the client is the premium user (aka RDC named user), the client will see the "Contact premium support" button on the RTSDK page (https://developers.refinitiv.com/en/api-catalog/refinitiv-real-time-opnsrc/rt-sdk-cc and https://developers.refinitiv.com/en/api-catalog/refinitiv-real-time-opnsrc/rt-sdk-java), then the client can submit a ticket to the API support team directly.
Additonally, the client can submit a ticket to the RTSDK development directly via the Real-Time SDK - GitHub issue page.
0 -
Thanks @wasin.w . The RICs should have colon ':' at the end of the name:
0#T7E:
0#OCB:
0#TIE:
The 2nd question is about do we have a toString method may 'toString' without such decoding error? It's easy to reproduce with the simplest and standard example.
And what's the normal response time for the GitHub issue submitting channel?
0 -
@Jirapongse . An interesting issueMany thanks
maybe content problem, and whether the toString method (both C++ and Java ESDK) should handle this scenario. Normally as developer, the toString method will be expected as error free method.
0 -
Hello @Frederic
The EMA API supports the stringification which prints all OMM containers, primitives, and messages to screen in a standardized output format.
Example:
System.out.println(refreshMsg);
System.out.println(updateMsg);
System.out.println(statusMsg);The client can parse each field data based on its data type too. Please check the decode() method of ex360_MP_View/Cons360 example for more detail.
Please note that this Q&A forum and the GitHub issue are community-based support, there is no SLA. However, the Premium user/RDC named user can submit a ticket to the API support team which has a SLA .
0 -
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
- 690 Datastream
- 1.5K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 560 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 724 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛