Where can I get the documentation for status message relating to RTMDS for websocket API

Example :
STATUS (Item Closed) Text: RTMDS*Access Denied: to IDN StreamState: CLOSEDDataState: SUSPECT
CACHED Status - StreamState: CLOSED DataState: SUSPECT
Answers
-
Hello @roy-a.wong
Please be informed that the
is a server-side API. All status messages are generated on the server side (either RTMDS, RTDS, or RTO) , so I recommend you contact the RTMDS Support team about the RTMDS's error and status messagesAbout the example status message, the "RTMDS*Access Denied: to IDN" status text indicates that it is a permission issue with your DACS user and the subscription service.
This permission issue cannot be fixed via the code. Please contact your LSEG representative or Account manger to verify your permission.
0 -
Thank you for your assistance. Is there any available documentation regarding the RSSL RFA status code? I am encountering the same error. I understand that the issue is not related to the code itself. However, I seek a comprehensive understanding of whether both messages are identical when one is mounted on PREM RTDS and the other on RTMDS, utilizing the same RIC.
STATUS (Item Closed) Text: ADS Record not service permissioned StreamState: CLOSED DataState: SUSPECT
CACHED Status - StreamState: CLOSED DataState: SUSPECTSTATUS (Item Closed) Text: RTMDS*Access Denied: to IDN StreamState: CLOSED DataState: SUSPECT
CACHED Status - StreamState: CLOSED DataState: SUSPECT0 -
Hello @roy-a.wong
I checked the RFA and ADS documents. Unfortunately, I could not find any information about them on the documents.
Based on my experience, both of them are relate to the permission issues. This kind of messages are generated from the server side (ADS, DACS, etc.), not the API. There are many levels of permission (the RIC level, Service level, user level, etc.) which can produce different error messages.
About the "ADS Record not service permissioned" error message, I cannot find a clear explanation about it. I strongly suggest you contact the ADS Support team to look into the issue. You can contact the team via https://myaccount.lseg.com/en/helpandsupport website.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 48 Data Fusion
- 34 Data Model Discovery
- 689 Datastream
- 1.4K DSS
- 627 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
- 24 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 278 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 706 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 中文论坛