FID explanation for JGBs
Take a look at the following RICs JP00170054=RRPS OR JP00180054=RRPS . We used to get the benchmark on the LINKLINK1 FID. The format of the LONGLINK1 getting published has changed and we dont have permissions anymore. What other FIDs can give us the benchmark? Also what do the LONGLINK1 , LONGLINK2 and LONGLINK3 FIDs publish for these Japanese government bonds.
Answers
-
Thank you for reaching out to us.
LONGLINKxx fields are typically used with chain RICs, which contain a list of their constituent RICs.
For example, 0#.SETI is a chain RIC for SET INDEX.
The LONGLINK1 to LONGLINK14 fields contain RICs in SET INDEX.
The application need to subscribe to RICs in the LONGLINK1 to LONGLINK14 fields to get the data of those RICs. For more information, please refer to this Retrieve underlying Instrument of Chain Symbol article.
If you don’t have permission to access RICs in the LONGLINK1 to LONGLINK14 fields, please reach out to your LSEG account or sales team to verify your account’s access rights.
0 -
Thank you @Jirapongse ,
That might be typically the case for the LONGLINK based FIDs. However in this case the Japanese government bond in itself is not a chain. Thats why we need explanation on what the exchange thinks its publishing.
0 -
Thank you for the update.
This forum is dedicated to software developers using LSEG APIs. The moderators on this forum do not have deep expertise in every bit of content available through LSEG products, which is required to answer content questions such as this one.
The best resource for content questions is the Helpdesk support team, which can be reached by submitting queries through LSEG Support. The support team will either have the required content expertise ready available or can reach out to relevant content experts to get the answer for you.
Please include the URL of this discussion in your raised question to prevent it from being redirected back to this Q&A forum.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 707 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.3K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 3K Elektron
- 1.5K EMA
- 259 ETA
- 570 WebSocket API
- 41 FX Venues
- 16 FX Market Data
- 2 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 26 Messenger Bot
- 4 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 284 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 25 RDMS
- 2.2K Refinitiv Data Platform
- 8 CFS Bulk File/TM3
- 901 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 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
- 126 Open DACS
- 1.1K RFA
- 108 UPA
- 196 TREP Infrastructure
- 232 TRKD
- 921 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 106 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛