Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Elektron /
  • EMA /
avatar image
Question by Nana · Jan 05, 2017 at 12:47 PM · elektronrefinitiv-realtimeelektron-sdkrrtema-apielektron-message-apiricsfieldschain-ric

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?

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

3 Replies

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by nick.zincone · Jan 05, 2017 at 01:35 PM

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.

Comment
zoya faberov
Tim Smith
Nana

People who like this

3 Show 1 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

avatar image
Nana · Feb 08, 2017 at 12:12 PM 0
Share

Thanks Nick...good answer...

avatar image
REFINITIV
Answer by Olivier DAVANT · Jan 20, 2017 at 07:50 AM

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.

Comment
nick.zincone
Nana

People who like this

2 Show 1 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

avatar image
Nana · Feb 08, 2017 at 12:14 PM 0
Share

Thanks Olivier...very good information... I appreciate it

avatar image
REFINITIV
Answer by Olivier DAVANT · Mar 31, 2017 at 09:57 AM

Hi @Nana,

You may be interested by the following articles and the source code that goes with them:

  • Decoding Chains - Part1
  • Decoding Chains - Part 2
Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
10 People are following this question.

Related Questions

EMA CPP - Exception adding ric into OmmArray

Is there a way to get holiday calendar for markets (instrumen wise or general) using Java API?

Where do I get the Reuters Instrument Code (RIC) ?

Elektron EMA Thailand Data Feed FIDs

How can I find Non-deliverable Forward RIC for BRL, CLP, COP, IDR, KRW, MYR, PEN, PHP, RUB, VND ?

  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Electronic Trading
    • Generic FIX
    • Local Bank Node API
    • Trading API
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Intelligent Tagging
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open Calais
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • RDMS
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • Workspace SDK
    • Element Framework
    • Grid
  • World-Check Data File
  • 中文论坛
  • Explore
  • Tags
  • Questions
  • Badges