Diff of eta3.7.2.L1.linux.rrg vs eta3.6.1.L2.linux.rrg

We wanted to check the output messages which we send back to our users along with the Symbol name and other fields. We tried our subscription with two different versions.

For eta3.7.2.L1.linux.rrg it shows the RIC name while for eta3.6.1.L2.linux.rrg it does not. See SS.

Questions:

Could you explain why there’s a difference between the two versions?
What steps should we take with version eta3.6.1.L2.linux.rrg to ensure the symbol name is included with the output log?

3.6

3.7

Thank you

Find more posts tagged with

eta-api

#technology

Accepted answers

All comments

wasin.w V3

Hello @marlon_T

The ETA 3.6.1 was released since 2021 which is very old. We highly recommend the client upgrade to the latest version 3.9.2.L1 to get all bug fixed and features.

marlon_T

thanks @wasin.w V3

Any explanation that we can share with the client about the changes that we have made from 3.6 to 3.7?
upgrades on the client side is not easy and right now, most of them are in a change freeze.

Jirapongse

The CHANGELOG.md file in the package lists the changes in the API.

Typically, the client can set the RSSL_RQMF_MSG_KEY_IN_UPDATES flag in the request message to Indicates that the consumer wants to receive the full msgKey in update messages. The RIC name is in the msgKey.

How did the client generate those outputs? Were they produced using the same code, or did the client run the example scripts included in the package?

The client may need to share the code they used to subscribe to the data.

If the client would like to investigate this issue in ETA and the client is a named user of the Refinitiv Developer Connect, the client can raise this issue to the API support team directly via Contact Premium Support.

EXPLORE OUR SITES