Sending permData from Contex application to DACS

Hi,
We are sending the permData for Contex application to DACS in the following format by enabling the flag "RSSL_PSMF_HAS_PERM_DATA"
permData="0301
6620 00C0"
Based on the above values.
03 – The header
01 66 – Service ID in
HEX
20 00 – PE Code in
Decimal
C – Terminator
0 – is just padding
But the DACS is display wrong permData and getting NAK in Contex application.
RSSL_PSMF_HAS_PERM_DATA)" seqNum="6" postId="6" permData="CC" postUserId="0"
Best Answer
-
It is the same question as in this thread.
0
Answers
-
Please explain more about the problem and share the connection diagram.
In my understanding, the Contex application sent a post message to TREP with permData="0301 6620 00C0". However, the TREP has changed the permData to "CC" while forwarding the post message to the contribution server. Then, the Contex application got the NAK message for that post.
Is it correct?
0 -
Thanks for your reply.
You are right Contex application sending post message to TREP-->DACS.
The flow is as below:
CONTEX > ADS (ATS_CORE) > ATS > DACS
The requirement here is Contex application has to send DACS Enabled permissioning DATA to TREP(ATS) at each record set level.We have following function in Contex(UPAMessageCodec.h) which will set the permissioning data in Post Message and sends to TREP(ATS).
template<class T> RsslRet UPAMsgBuilder<T>::SetDacsPermissioning( int nEnableDacsPermissioning ) {
unsigned int final_Value = 3 | 358 | 8192 | 12;
const std::string& value = std::to_string( static_cast<long long>(final_Value));
m_message.permData.data = const_cast<char *>( value.c_str() ); m_message.permData.length = static_cast<RsslUInt32>( value.length() );
return RSSL_RET_SUCCESS;
}
In above function we have hard coded the header and Terminator values for Testing.
unsigned int final_Value = 3 | 358 | 8192 | 12;(In Decimal)
03 – The header
01 66 – Service ID in HEX
20 00 – PE Code
C – Terminator
0 – is just padding
My query is here whether the filling of permData in above function(SetDacsPermissioning) is proper?if it's wrong how we need to fill permData with headers,terminators,PE Code(PROD_PERM) so that permData should be displayed properly in DACS and get ACK message to Contex applicaton
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
- 695 Datastream
- 1.5K DSS
- 631 Eikon COM
- 5.2K Eikon Data APIs
- 12 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 4 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 561 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
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 734 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
- 96 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛