Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • TREP APIs /
  • Open DACS /
avatar image
Question by Craig Thomas · Jan 05 at 06:33 AM · open dacs api

Compose/Decompose Compound DACS Locks

I'm trying to understand how I may use the OpenDACS API to work with complex logical combinations of permission entities (PEs).


The DACSLOCK_devguide section 3.4 (Compression of DACS Locks) suggests that both AND and OR operators may be used in a single compound lock:

1027 & (456 | 985) & 5000


The document goes on to explain how such compounds are compressed in binary coded decimal.

I can't see any way to compose nor decompose such a compound using the API (C++).

The logical operator can be specified in the AuthorizationLock class, but it only operates on type long PEs. I can use this to compose (1027&5000) and, separately, (456|985).
The AuthorizationLockData class allows for combining multiple AuthorizationLockData instances, but has no way to specify the logical operator.

How may I use the APIs to compose a lock of PEs: 1027 & (456 | 985) & 5000.

Or another example to compose: (123 & 456) | (321 & 654)

Will I instead have to work on the raw char* lock data buffer?

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 zoya.farberov · Jan 06 at 12:07 AM

Hello @Craig Thomas,

You are looking to create compound locks.

It appears you are coding a publisher application in RFA C++. It then means you would be referring to the document

DACS Lock Guide for RFA C++

If that is the case, please see "operator". Operator is set when a lock is constructed, can be "&" or "|". We can appendPE(), and obtain lock data, our ultimate goal, using getLock().

AuthorizationData from multiple locks can be combined, using combineLock.

(Perhaps you are coding in ETA. Same concepts implemented for ETA C++ can be found in

Transport API C DACS Library Functions)

In terms of the API usage- RFA C++ or Refinitiv Real-Time ETA C/EMA C++, this should cover the requirements.

However, there may be more to the underlying logic of lock creation. The original lock could have an "|" between PE. Because the same item (for example IBM) can be permissioned via one of several PEs. Can also have an "&". Because multiple permissioned items can be included. When several items from multiple sources are combined into a compound item, in order to consume the item, the user has to be permissioned for all of the items included. I.e. "|" will not work. Essentially, it is "&" on compound, which is why combineLock() function works to derive the necessary compound lock.

If you are coding a new publisher, I would strongly suggest going with Refinitiv Real-Time ETA/EMA for the implementation, as these are contemporary APIs, having all of the latest features and actively evolving. RFA is a currently supported, but feature-complete API choice.

Let me know if this helps, or if this is not what you are looking for, please explain more of the use case and the API being used.

Comment
jirapongse.phuriphanvichai

People who like this

1 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.

avatar image
Answer by Craig Thomas · Jan 06 at 12:19 AM

Thanks for the response @zoya.farberov.

Just to clarify, the AuthorizationLockData::combineLock() function essentially ANDs the AuthorizationLockData arguments (using the & operator)?

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.

avatar image
REFINITIV
Answer by zoya.farberov · Jan 06 at 01:39 AM

Hello @Craig Thomas,

The section of DACS Lock Guide "Compression of DACS Locks" describes and illustrates in detail the content that will ultimately be conveyed in the resulting DACS lock.

Yes, this is what is logically happening to the compound lock as it's being combined, and the reason why the approach works, hopefully is also more intuitive now.

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 >
8 People are following this question.

Related Questions

Open DACS migrate to ODPS - multi-domain support

How to get DacsLockIDs for any service?

  • Feedback
  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Careers
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Calais
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • 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
  • TRIT
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • World-Check Data File
  • Explore
  • Tags
  • Questions
  • Badges