How do you identify if a RIC is a chain RIC in order to subscribe to all the underlying RICs?
I don't believe there is an EMA function which will allow you to subscribe[registerClient] to all the underlying RICs in the chain. So in lieu of this functionality, I wish to pull FIDs from a RIC to determine if it is a chain RIC. From that I can likely subscribe to the associated LONGLINK 1-14 (FID 800 - 813) and see if the LONGNEXTLR (FID:815) has a value to keep pulling in further RICs.
Is the field REF_COUNT(239) a reliable field to use to determine if I'm dealing with a chain?
Best Answer
-
Hi @Nana,
You are correct, EMA does not have the capability to automatically subscribe to the underlying RICs within a chain. In general, you will have to look for a specific field within the response message to determine if you are working with a chain. The reference to the LONGLINK 1-14 and REF_COUNT are fields which you can use as reliable indicators you are dealing with a chain. The LONGNEXTLR and LONGPREVLR are only present if you have additional/previous records within the chain.
In general, the REF_COUNT field should be a sufficient indicator.
0
Answers
-
Hi @Nana,
Nick is absolutely right.
You also have to know that you may encounter different types of chains. They all work the same but use different fields
that support different sizes of RICs. See bellow:- LINK_ chain records use the following fields that
are limited to 10 char RICs:- LINK_1 to LINK_14
- PREV_LR
- NEXT_LR
- LONGLINK chain records use the following fields that
are limited to 17 char RICs:- LONGLINK_1 to LONGLINK_14
- LONGPREVLR
- LONGNEXTLR
- BR_LINK_ chain records use the following fields that
are limited to 32 char RICs:- BR_LINK1 to BR_LINK14
- BR_PREVLR
- BR_NEXTLR
These 3 types of chain use the same REF_COUNT to indicate
the number of links used by the chain element.I’m going to write an article with
much more details about chains. I’ll keep you posted via this question.0 - LINK_ chain records use the following fields that
-
Hello Wasin, I don't see any text saying "Accept". I only see "Like", "Add Comment", "Reward user" and "Share"...
0 -
Thanks Nick...good answer...
0 -
Thanks Olivier...very good information... I appreciate it
0 -
Hi @Nana,
You may be interested by the following articles and the
source code that goes with them: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
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛