Messages without Name field in EMA

Hi all,

We differentiate messages received from EMA based on the name(RIC) field contained within the message.

UpdateMsg streamId="420" domain="MarketPrice Domain" updateTypeNum="0" seqNum="44766" doNotConflate name="CNH=" serviceId="600" serviceName="IDN_RDF" Payload dataType="FieldList" FieldList FieldListNum="0" DictionaryId="0" FieldEntry fid="22" name="BID" dataType="Real" value="7.1028" FieldEntry fid="393" name="PRIMACT_1" dataType="Real" value="7.1028" FieldEntry fid="25" name="ASK" dataType="Real" value="7.1032" FieldEntry fid="275" name="SEC_ACT_1" dataType="Real" value="7.1032" FieldEntry fid="875" name="VALUE_DT1" dataType="Date" value="17 SEP 2025 " FieldEntry fid="1010" name="VALUE_TS1" dataType="Time" value="05:44:37:000:000:000" FieldEntry fid="831" name="CTBTR_1" dataType="Rmtes" value="2" FieldEntry fid="836" name="CTB_LOC1" dataType="Rmtes" value="2" FieldEntry fid="841" name="CTB_PAGE1" dataType="Rmtes" value="2" FieldEntry fid="3" name="DSPLY_NAME" dataType="Rmtes" value="2" FieldEntry fid="78" name="OFFCL_CODE" dataType="Rmtes" value="2" FieldEntry fid="105" name="BCKGRNDPAG" dataType="Rmtes" value="2" FieldEntry fid="826" name="DLG_CODE1" dataType="Rmtes" value="2" FieldEntry fid="1011" name="VALUE_TS2" dataType="Time" value="05:44:37:000:000:000" FieldEntry fid="1012" name="VALUE_TS3" dataType="Time" value="05:44:36:000:000:000" FieldListEnd PayloadEnd UpdateMsgEnd

However, we observe that the name field is not transmitted in many messages similar to the example below. What is the cause of this behavior? How can we effectively handle this scenario?

UpdateMsg streamId="15" domain="MarketPrice Domain" updateTypeNum="0" seqNum="63998" doNotConflate Payload dataType="FieldList" FieldList FieldListNum="0" DictionaryId="0" FieldEntry fid="22" name="BID" dataType="Real" value="3.7507" FieldEntry fid="393" name="PRIMACT_1" dataType="Real" value="3.7507" FieldEntry fid="25" name="ASK" dataType="Real" value="3.7509" FieldEntry fid="275" name="SEC_ACT_1" dataType="Real" value="3.7509" FieldEntry fid="875" name="VALUE_DT1" dataType="Date" value="16 SEP 2025 " FieldEntry fid="1010" name="VALUE_TS1" dataType="Time" value="21:41:50:000:000:000" FieldEntry fid="831" name="CTBTR_1" dataType="Rmtes" value="4Y6M" FieldEntry fid="836" name="CTB_LOC1" dataType="Rmtes" value="4Y6M" FieldEntry fid="841" name="CTB_PAGE1" dataType="Rmtes" value="4Y6M" FieldEntry fid="3" name="DSPLY_NAME" dataType="Rmtes" value="4Y6M" FieldEntry fid="78" name="OFFCL_CODE" dataType="Rmtes" value="4Y6M" FieldEntry fid="105" name="BCKGRNDPAG" dataType="Rmtes" value="4Y6M" FieldEntry fid="826" name="DLG_CODE1" dataType="Rmtes" value="4Y6M" FieldEntry fid="1011" name="VALUE_TS2" dataType="Time" value="21:41:49:000:000:000" FieldEntry fid="1012" name="VALUE_TS3" dataType="Time" value="21:41:48:000:000:000" FieldListEnd PayloadEnd UpdateMsgEnd

Find more posts tagged with

ric

ema-api

update-message

#technology

Accepted answers

All comments

Jirapongse

@SquadTreasury

Thank you for reaching out to us.

The item name in an update message is optional.

I found the MsgKeyInUpdates configuration in the Consumer.

The default value is 1 so update messages should contain item names.

However, instead of relying on the MsgKeyInUpdates configuration, you can try the following methods to solve this problem.

Typically, each item has a unique handle, allowing the application to implement a mapping between handles and item names. The application can map a handle to an item name by parsing a refresh message
Or, if the application doesn't use batch requests. The application can set a closure with an item name and get a closure (item name) through the OmmConsumerEvent passed in the callback methods

If you have any further question, please provide the following information.

The version of EMA that you are using
EMA configurations or EMA configuration file used by the application
Is it EMA C++, Java, or C#?

SquadTreasury

Thanks for your answer,

Based on your response, our investigation indicates that the handles in Update and Refresh messages appear to be different. Here are a few examples:
In the Update message:
Handle = 5 for DKK=TRB
Handle = 147 for DKKSWID=R
Handle = 416 for CNH=

In the Refresh message:
Handle = 1105 for DKK=TRB
Handle = 1247 for DKKSWID=R
Handle = 1516 for CNH=

I understand this difference to be important for distinguishing between message types.

Furthermore, will these handle values always remain the same? Or will they change daily or in each session?

We are using the LSEG.EMA.Core 3.4.0 library with C#.

We set MsgKeyInUpdates = 1.
We are using the "user dispatch" method.
MaxDispatchCountUserThread = 100

Other than these, our other settings are at default.

Gurpreet

https://community.developers.refinitiv.com/discussion/comment/127965#Comment_127965

Hello @SquadTreasury

There might be some bug in your code. The item handle that is received at the time of subscription will not change and will remain same throughout the Refresh and Update messages.

Please show the code that you are using, or simply add these lines to your code -

System.out.println("Refresh - handle: " + event.handle() + " closure: " + event.closure());

SquadTreasury

As you can see in the image, the same handle is always displayed for TRY=TRB with the Update message, until a new handle is displayed with the Refresh message. Also, the closure is empty. This must be because we're making batch requests.

Jirapongse

@SquadTreasury

I assumed that the application may close (Unregister) the previous handle of TRY=TRB and then resubscribe to TRY=TRB.

In this case, the application will get a new handle for TRY=TRB.

My initial response didn’t account for all use cases. Each registered item will have a unique handle. For instance, if you register TRY=TRB twice, each registration will receive its own distinct handle.

EXPLORE OUR SITES