EMA consumer handling of messages with StreamState ==ommstate.ClosedRecover
What is the difference between StreamState ==ommstate.Closed and StreamState ==ommstate.ClosedRecover?
How should an EMA consumer handle a MarketPrice Refresh or MarketPrice Status message received with the state component publishing StreamState ==ommstate.ClosedRecover?
Best Answer
-
ommstate.Closed means data is not available and is not likely to become available.
An example for Closed state is when you request invalid name. Data will not be available unless you change the name.
ommstate.ClosedRecover means data is currently not available but can be recovered at a later time.
By default, an EMA consumer should never received this status because TREP will attempt to recover data on EMA’s behalf.
To received closed recover status, EMA consumer must override the default login request by using the OmmConsumerConfig.addAdminMsg().
And If you wish to handle it, then you could just treat it as a closed status but EMA consumer can attempt to re-request at a later time using the same request message.
0
Answers
-
ommstate.Closed means data is not available and is not likely to become available.
An example for Closed state is when you request invalid name. Data will not be available unless you change the name.
ommstate.ClosedRecover means data is currently not availablebut can be recovered at a later time.
By default, an EMA consumer should never received this status because TREP will attempt to recover data on EMA’s behalf.
To received closed recover status, EMA consumer must override the default login request by using theOmmConsumerConfig.addAdminMsg().
And If you wish to handle it, then you could just treat it as a closed status but EMA consumer can attempt to re-request at a later time using the same request message.
0 -
Thanks!
what config in login msg will override the default behavior and allow reception of ClosedRecover into the application? Is it SingleOpen = 0?
0 -
Yes, it is SingleOpen. But I advise against turning SingleOpen off. It usually better to let TREP recover the data.
1
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛