PROD_PERM and DACS getPeList function for real and delayed symbols
We are receiving DACS response and reading data returned by getPeList which is vector of unsigned int.
We need to know how to interpret numbers, there is no information in DACS docs unfortunately. We need to know actually only one thing - whether authorization response came on actual or delayed symbol. in out case real time PE is always 5625 and for delayed symbols it is 9241.
We are using Open DACS and RFA 8.0 C++
Best Answer
-
PE can be mapped to DACS subservices which are assigned to DACS users.
For example, from the above picture. PE 5625 is mapped to LSE1D (exchange subservice) and GBSE3PRIPD (product subservice). To subscribe to the item with PE 5625, the DACS user must have both LSE1D and GBSE3PRIPD in the profile.
You can use the getPeToSubServiceList() method is used to lookup within DACS, the PE to subservice authorization values that have been assigned to the referred to service.
For more information, please refer to Tutorial 4 - Content Based Entitlements (CBE).
0
Answers
-
Hello @mktdata ,
If my understanding is correct, you are trying to understand, for each of the PEs returned per user if it is a realtime PE or a delayed PE?
The way I can think of obtaining this information, you would need to obtain a DACS lock per realtime item (for example, subscribe IBM.N), and a DACS lock per delayed realtime item (for example, subscribe delayed /IBM.N), and each will carry it's lock, you will see the PE assigned, to this item, and therefore to this type of item per exchange. The information would repeat for each type of instrument that you require, so you would need to run this once, per type of instrument required.
Perhaps not directly relevant, Open DACS Permission Server (ODPS) interface includes function itemToPE that is intended to obtain this information, to map item to it's PE(s).
Hope this info helps
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
- 25 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
- 716 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 中文论坛