what status message is expected from publisher when the Instrument is currently not available.

Hi All,
I would like to briefly explain the scenario:
We have a publisher that sends a Service Up message, but initially, no instruments are available. Instruments are created dynamically, so it's not possible to expect all of them to be available immediately.
In this case, what message is expected from the publisher to ensure the end user receives the data once it becomes available?
RSSL_STREAM_CLOSED or RSSL_STREAM_CLOSED_RECOVER
Second scenario:
Out of 10 requested instruments, only 5 are actually available. The remaining 5 have expired and will never be served by the publisher.
How should we handle timeouts or negative acknowledgments for these invalid instruments?
Many Thanks,
Answers
-
Hello @yathing.ullal
The key difference between the CLOSED and CLOSED_RECOVER is the recovery of data. A CLOSED implies that the instrument does not exist and will never be available again. The application/SDK should not try to subscribe to this instrument again. This should be used in the second scenario that you describe - the expired instruments that will never be available again.
A CLOSED RECOVER, implies that the instrument is not currently available. It might become available at some time in future and the app should try again at a later time.
0 -
Hi Gurpreet, Many Thanks for the suggestion, it's very clear now that I definitely have to use CLOSED_RECOVER, as the Instruments will be available anytime, but I am still unclear how should we handle wrong or expired Instruments, as we have set CLOSED_RECOVER it will wait.
0 -
For invalid or expired instruments, the publisher should send a Closed status message. See this example that infrastructure sends for an instrument that does not exist -
StatusMsg streamId="5" domain="MarketPrice Domain" state="Closed / Suspect / Not found / '**The record could not be found'" name="INV.ALID" nameType="1" serviceId="257" serviceName="ELEKTRON_DD" StatusMsgEnd
0 -
Hi Gurpreet - Many thanks for the suggestion, there is one more condition i would like to get your suggestion on.
After the service is up few of the Instruments are available but they are not actually available with any FIDS populated, currently its set as RSSL_STREAM_OPEN with RSSL_DATA_SUSPECT and once the fields are populated, we again send a refresh, is this the correct way to handle this, or would you like to suggest a better way of doing it.
ThanksYathin
0 -
Yes, you could do that.
0 -
Many Thanks @Jirapongse , but is there any other way of handling this, just want to make sure the way we have it is the best way, if you have any other option pls let me know, would love to try that out.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 697 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
- 2.9K Elektron
- 1.5K EMA
- 256 ETA
- 564 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
- 283 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2.1K Refinitiv Data Platform
- 779 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
- 122 Open DACS
- 1.1K RFA
- 107 UPA
- 194 TREP Infrastructure
- 231 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 98 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛