Ability for a consumer to identify if prices published by a provider are stale
Using EMA, is there a mechanism for a market data consumer to identify if prices being published by providers are stale due to an issue faced by the provider or any other reason?
Best Answer
-
In addition to the answer already provided there are two additional points to note:
- There isn't exactly a state called "stale", but there's a data state called "SUSPECT" and this is what you are looking for. SUSPECT is actually a much better word. In most cases you'll experience that an item in this state has stopped updating (meaning it is stale in the true meaning of the word) but this may not be the case. SUSPECT simply means there's currently something wrong with the item, not necessarily that it is no longer updating.
- State is something you'll need to keep track of yourself on a per-item basis as each UPDATE message doesn't come with its own state. As with everything else in TREP you'll only see messages if something is actually changing. This is also true for State.
Lars
Addicticks
1
Answers
-
When a market data stream state changes e.g. suspect/stale due to the provider goes down. EMA consumer will receive status messages at the callback method named onStatusMsg(...).of OmmConsumerClient interface. The example source code implementing the onStatusMsg(..) in EMA Java Consumer application
public void onStatusMsg(StatusMsg statusMsg, OmmConsumerEvent event)
{
System.out.println("Item Name: " + (statusMsg.hasName() ? statusMsg.name() : "<not set>"));
System.out.println("Service Name: " + (statusMsg.hasServiceName() ? statusMsg.serviceName() : "<not set>"));
if (statusMsg.hasState())
System.out.println("Item State: " +statusMsg.state());
System.out.println();
}The example output when the provider goes down, EMA application will receive a status message:
Item Name: IBM.N
Service Name: API_NEON_NI
Item State: Open / Suspect / None / 'A23: Service has gone down. Will recall when service becomes available.'
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 中文论坛