What is the range for PROD_PERM field and how we can extend it?

Thank you for reaching out to us.

Technically, the type of the PROD_PERM field is unsigned integer 64 bit but the RWF LEN for caching is 2 bytes by default.

!ACRONYM    DDE ACRONYM          FID  RIPPLES TO  FIELD TYPE     LENGTH  RWF TYPE   RWF LEN
!-------    -----------          ---  ----------  ----------     ------  --------   -------
!
PROD_PERM  "PERMISSION"             1  NULL        INTEGER             5  UINT64           2
!

According to this data dictionary definition, the valid values of the PROD_PERM field are from 0 to 65535.

However, regarding how to use this field with a Content Based Entitlement (CBE) subscription, please contact the DACS support team directly via MyRefinitiv.

All comments

Thank you for reaching out to us.

Technically, the type of the PROD_PERM field is unsigned integer 64 bit but the RWF LEN for caching is 2 bytes by default.

!ACRONYM    DDE ACRONYM          FID  RIPPLES TO  FIELD TYPE     LENGTH  RWF TYPE   RWF LEN
!-------    -----------          ---  ----------  ----------     ------  --------   -------
!
PROD_PERM  "PERMISSION"             1  NULL        INTEGER             5  UINT64           2
!

According to this data dictionary definition, the valid values of the PROD_PERM field are from 0 to 65535.

However, regarding how to use this field with a Content Based Entitlement (CBE) subscription, please contact the DACS support team directly via MyRefinitiv.

@Jirapongse

We need to have PROD_PERM field with LENGTH = 7 instead of 5 for our appropriate feeds . For these purpose, we have changed PROD_PERM in RDMFieldDictionary as follow according to IDN/Marketstream Mapping Table:

!ACRONYM DDE ACRONYM FID RIPPLES TO FIELD TYPE LENGTH RWF TYPE RWF LEN

!------- ------------ --- ---------- ---------- ------ -------- -------

PROD_PERM "PERMISSION" 1 NULL INTEGER 7 UINT64 3

We successfully receive 7-digits PROD_PERM in our appropriate instruments, but we see that Lock value in Dacs Lock file is N/A and PE permission does not work properly:

AccessPELock {

Service { TEST_FEED 7999

Items { 2

PE { TEST=1100001 MARKET_PRICE N/A }

PE { TEST=1100002 MARKET_PRICE N/A }

}

Comment { Dump End: Mon Oct 30 14:47:09 2023 }

}

What API are you using to retrieve DACS Lock?

We are using Open DACS server API.

As far as I know, the Open DACS server API can't retrieve DACS Locks.

It provides a class to create DACS Locks from the PE list.

@Jirapongse

We create Access Lock file using ADH dumpAccessLock feature and we see correct values in case of PROD_PERM is less than 5 digits or equal, but N/A value in case of PROD_PERM is more than 5 digits.

On the other hand, we see correct 7-digit value in PROD_PERM field of our appropriate instruments. FID 1 was extended: INTEGER 7 UINT64 3 accordingly.

I checked the ADH installation guide in Section 6.7.4 Refinitiv Data Access Control System Access Lock Creation and found that the Refinitiv Real-Time Advanced Distribution Hub can support the creation of insert locks for FID 1 (PROD_PERM) values up to 65535.

Please contact the ADH support team directly via MyRefinitiv to confirm this.