DSPLY_NAME field issue

On the "REFRESH_RESP" item event, we can see there is the field "DSPLY_NAME" representing the Currency Pair in the response.
But on the subsequence "UPDATE_RESP" there was no "DSPLY_NAME" field anymore, only the rates and the dates.
How do we know if this "UPDATE_RESP" is for which item? How do we identify it?
I also have a question: What's the equivalent of "com.reuters.rfa.session.event.MarketDataItemStatus" in OMM?
Best Answer
-
Hi Gurpreet… there is one more question at the end of my previous message, pasted below as well.. please help on that.
"What's the equivalent of "com.reuters.rfa.session.event.MarketDataItemStatus" in OMM?"
0
Answers
-
Hello @Pulaputra.Sudheer
The item name is included in the encapsulated message and not in the fields which are updated. There are multiple means of identifying the instrument in RFA API callback method.
- Assign a unique closure object to each subscribed item. The closure could be a string with the item name or any other identifier. This closure is available in the event callback for that particular subscribed item.
2. Get the item handle when subscribing. This item handle is subsequently available in the process event callback:
Handle itemHandle = _ommConsumer.registerClient(_eventQueue, connIntSpec, callbackClient, null);
and in the callback method:
public void processEvent(Event event) { Handle itemHandle = event.getHandle(); …
3. Request Attribute information in the update messages -
ommmsg.setIndicationFlags(OMMMsg.Indication.REFRESH | OMMMsg.Indication.ATTRIB_INFO_IN_UPDATES);
and the update messages will now contain the item name in the response:
Msg Type: MsgType.UPDATE_RESP Msg Model Type: MARKET_PRICE Indication Flags: DO_NOT_CONFLATE Hint Flags: HAS_ATTRIB_INFO | HAS_RESP_TYPE_NUM | HAS_SEQ_NUM SeqNum: 70945 RespTypeNum: 0 (UNSPECIFIED) AttribInfo ServiceName: ELEKTRON_DD ServiceId: 10002 Name: CAD= NameType: 1 (RIC) Payload: 13 bytes FIELD_LIST FIELD_ENTRY 114/BID_NET_CH: -0.0003 FIELD_ENTRY 372/IRGPRC: -0.02
1 -
It should be equivalent to OMMState in the OMMMsg.
static final void parseMsg(OMMMsg msg, PrintStream ps, int tabLevel)
{
if (msg.has(OMMMsg.HAS_STATE))
{
dumpIndent(ps, tabLevel + 1);
ps.println("State: " + msg.getState());
}0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛