DACS building PE Maps

Hi, I am attempting to write a DACS integration for a middleware product. The middleware product itself does not directly interact with the subscription infrastructure and has no way to get at the DACS locks for particular instruments.
What I am attempting to do is to collect the User's PE list upon login to our middleware product and then use that to permission data that is plumbed through the system to end users. I have two problems:
1) I need to look up the DACS loc to get the PE List and condition for a particular Instrument (say AAPL.O). I have access to the set of subscribed instrument names for this particular part. While I have looked at the examples in the java library, I can only find ways to map PE's to known subservices (say NYS), not a particular instrument. Again, I am _not_ performing subscriptions and do not have another way to get access to the DACS lock for the instrument.
~~2) I have been unable to get getPEList() to return anything other than an empty list for any user, even using the example java programs. I have gone through the DACS API to ensure that there are, indeed, permissions enabled for the user I am using to test with, log-in is working and if I just happen to know a PE for something (CSCO.O. PE 74 (NAS1)) I can get a permission allowed response from the example with a properly configured UI, and if I revoke the permissions in the UI can see that change to a permission denied for the same user.~~
My questions are the following:
1) How do I get the PE List + Condition for a particular instrument . (DACSLock) given only the instrument name.
~~2) What needs to be done to get a non-empty PE list?~~ . I have figured this one out, My permissions from the UI were missing an item.
I am more than happy to provide code snippets from my integration efforts to illustrate what I have tried.
Best Answer
-
Hello @andrewbaranec,
1. PE list code per instrument can not be retrieved via OpenDACS calls.
- PE codes assigned per user can be retrieved by via OpenDACS (getPEList)
- PE per instrument can be retrieved by realtime subscription from Elektron (fid=PROD_PERM)
- or indirectly used by OpenDACS in determining checkSubscription
- or manually retrieved, via Product Code Lookup Tool on my.refinitiv.com , search for "Product Code Lookup"
2. Thanks for letting us know, it may help other member of the developer community
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
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 24 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 713 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛