data for *.DE rics through Java RFA on 03-July-2017

Hi,
It seem that there was release on XETRA exchange on 3 July (http://www.deutsche-boerse-cash-market.com/dbcm-en/newsroom/press-releases/New-T7-trading-technology-goes-live-on-Xetra/3089506).
I can see that a new field appeared in data from RFA since then (NA_MSG_TYP, fid 8636) with values like "d", "W", "f", "X".
Can you please tell what different values stand for or point me to some document where i can look them up myself?
Also, on 03-Jul-2017 i haven't received any trade messages for *.DE rics (BOSSn.DE for example) through RFA (using Java RFA api v.7.2.1.E2).
But since 4 July i've started getting trade messages again, without any changes on my side.
Does anyone know if there were changes on 03-July-2017 on Reuters side that affect *.DE rics?
Best Answer
-
If I'm not wrong your question is data related only. This discussion forum is dedicated to APIs and probably not the best place to get the answer you're looking for.
The Thomson Reuters Content Service group, on the other hand, is a more appropriate contact for this kind of question. You can contact them at this email address: content.services@thomsonreuters.com
0
Answers
-
Hi Olivier,
thanks for the answer.
The link you've posted seems to have 2 addresses:content.services@thomsonreuters.com
as text, and the acutal address leads toTRTHUpgradeSpecialists@thomsonreuters.com
Which one should be used?0 -
My bad. This is due to a wrong copy paste. The correct address is: content.services@thomsonreuters.com
0 -
Sorry, but are you sure that mentioned mailbox is still available?
I've tried sending message there and the message was bounced back with "Recipient address is possibly incorrect".
Is that address listed somewhere on reuters support sites?0 -
That's very embarrassing. This is the address I got from a reference document. Let me check that and I come back to you soon.
0 -
After verification it seems that I gave you to the wrong procedure. My apologize for this.The data support is not done via the email addresses I listed above, but via the My Account portal. Once logged in you will find a "RAISE A CASE" button at the top right of the screen that will redirect you to the "Product Support" screen. From this screen you will be able to raise your issue. The "I believe content is incorrect or incomplete" is probably the most appropriate option in your case.
Once the case raised, the content support team should contact you very shortly0 -
Thanks Olivier, i'll try that procedure.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 705 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 3K Elektron
- 1.5K EMA
- 259 ETA
- 569 WebSocket API
- 40 FX Venues
- 16 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
- 4 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 284 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 24 RDMS
- 2.2K Refinitiv Data Platform
- 879 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 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
- 123 Open DACS
- 1.1K RFA
- 108 UPA
- 196 TREP Infrastructure
- 232 TRKD
- 919 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 103 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛