What is the recommended way to subscribe to all RICs on a particular exchange?
My questions concern a few things about symbol list requests, the ITEM_LIST field of source directory messages and generally segmenting RICs by exchange.
What is the recommended way for me to programmatically, from my C or C++ application, to subscribe to, say, "all RICs on Nasdaq"? I have tried sending a symbol list request for "0#ITEMS", however I received a "record could not be found" response. In addition, what does "0#ITEMS" represent (found in the symbol list sample in the RDM Usage Guide) and how can I find other "symbol list" names?
I fail to find anything specific when searching.
Best Answer
-
Not a purely programmatic way of doing this. On the ETA side you are approaching this right. However, if the list of NASDAQ is not published by the provider, a subscriber app can not subscribe for it.
How to publish such a list?
On Elektron Edge device, which is probably your source of data, you can define a Broadcast Data Stream containing NASDAQ list.
Broadcast data stream is a simulated broadcast datafeed between the server and client application, that is defined based on criteria, for example, every instrument belonging to NASDAQ (or a static list of instruments united by some other commonality).
Once the BDS exists on EE, a subscriber can subscribe to it, as symbol list model type, via RIC name that has been given to it when it was defined.
0
Answers
-
Thanks for the info. I think I'm understanding you. So if the EE device had a custom collection configured (e.g. all symbols on nasdaq), I would then be able to send a subscription request for the RIC of that particular collection and receive streaming updates for all symbols in that collection?
Any chance you could point me towards documentation regarding the configuration of the EE or how I might start down this path? I am not having much luck searching for the names in your post.
0 -
It is documented in "TRSC for Elektron Edge User Guide". This document is part of EE installation and it is not available here. You should contact your technical account manager or TR technical specialist for help.
The creation of Broadcast data stream must be performed through TRSC, and is not available programmatically through a realtime
API. Moreover, the symbol list definitions can be constructed using either a file containing a list of RICs or a database query (SQL) only.1
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 中文论坛