X_RIC_NAME field not available via SFC C++ application?

Hi,
is it possible to get the field X_RIC_NAME using an SFC C++ consumer via SSL/MarketFeed?
The application is configured to download the data dictionary from Network, and actually I see such field in the dictionary, with IFD = -1.
However, when subscribing to a RIC expected to contain a value for such field, I get an image not containing X_RIC_NAME at all (we've enabled the IPCTRACE files to double check it).
Is there any known limitation in SFC explaining this?
In addition, could you please help me understand why some fields in the data dictionary have a negative number as FID?
Thanks
Best Regards,
Paolo
Best Answer
-
As I know, the Refinitiv Real-Time feed doesn't use the X_RIC_NAME field. X_RIC_NAME is defined by ATS (Refinitiv Real-Time Advanced Transformation Server).
! Using by ATS Contribution, clients are not suggested to redefine these fields.
X_RIC_NAME "RIC NAME" -1 NULL ALPHANUMERIC 32 RMTES_STRING 32
X_ERRORMSG "X_ERRORMSG" -2 NULL ALPHANUMERIC 80 RMTES_STRING 80
X_LOLIM_FD "X_LOLIM_FD" -3 NULL ALPHANUMERIC 3 RMTES_STRING 3Therefore, the Refinitiv Real-Time Distribution System (TREP) that has ATS may add those negative fields into the data dictionary file.
Negative fields are custom fields. The usage is explained in this Publish Custom Data via Refinitiv Real-Time Distribution System by EMA article.
0
Answers
-
Hi, thanks for the reply.
Is an SFC C++ based application, using SSL/Marketfeed, able to consume those custom fields? Do you have any idea why in this case the X_RIC_NAME field is not showing into the IPCTRACE file of the application? Maybe a configuration issue on the ATS?
Thanks
Paolo
0 -
SFC C++ subscriber retrieves the real-time data from the data feed. It is unable to modify the data. If it doesn't have the X_RIC_NAME field in the IPCTRACE file, it means that the data feed doesn't provide this X_RIC_NAME field.
As I know, the X_RIC_NAME is used when the application sends an insert message to ATS for creating or deleting a RIC.
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
- 687 Datastream
- 1.4K DSS
- 621 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 254 ETA
- 557 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 276 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 669 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
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛