How can i get possible value of fields from TREP/TRKD [XMIC_CODE, MIC_CODE, RDN_EXCHD2]
How can i get possible value of fields from TREP/TRKD XMIC_CODE, MIC_CODE, RDN_EXCHD2
Thanks,
Somjade.K
Best Answer
-
Hello @somjade.keswongrot
RDN_EXCHD2(field id 1709) is enumerated type. The values of this type are standard numeric values that can be expanded to specific strings. You can find all possible values of this type in enumeration dictionary which EMA consumer examples, example332__Dictionary__Streaming (Java) and 332__Dictionary__Streaming (C++) can consume. Hence, you can run the examples to retrieve the possible values of RDN_EXCHD2 from TREP.
The example output of example332__Dictionary__Streaming:
(Referenced by Fid 1709)
..
value=0 display=" " meaning="null"
value=1 display="ASE" meaning="null"
value=2 display="NYS" meaning="null"
value=3 display="BOS" meaning="null"
value=4 display="CIN" meaning="null"
value=5 display="PSE" meaning="null"
...The example applications are shipped with Elektron SDK - Java package and Elektron SDK - C/C++ package respectively.
XMIC_CODE and MIC_CODE types are string so the possible values of each RIC may be difference depending on the venue which generates them; there is no dictionary defining all values like enumerated type. I would suggest you reach out to the Refinitiv Helpdesk as they have data specialists who can provide you the possible values of both fields for RICs you are interested in.
The types of all fields are defined in RDMFieldDictionary which can be consumed by example332__Dictionary__Streaming and 332__Dictionary__Streaming as well.
Hope this help.
0
Answers
-
You can use one of our realtime APIs such as RFA or Elektron to consume a RIC code that contains those fields and then parse the payload to extract those fields if present.
If you can use Java or C++ then I recommend the Elektron SDK - of which the Elektron Message API is the easiest to learn and use. You can find tutorials on consuming data under the tutorials sections.
e.g. EMA Java Tutorials or EMA C++ Tutorials
If you need to use a different language, please advise which one and we can suggest an alternative API.
Obviously, not all RICs may contain all those particular fields - the Elektron feed carries millions of RICs and the payload is usually determined by what the originating venue provides us in terms of data. The majority do carry RDN_EXCHD2 and a few I tried did have XMIC_CODE or MIC_CODE too.
0
Categories
- All Categories
- 6 AHS
- 39 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
- 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 中文论坛