Hi @sonali.rane
Thanks for confirming the parameter values,
Can you also confirm the enumtype.def and RDMFieldDictionary are in the locations specified?
../../etc/enumtype.def
../../etc/RDMFieldDictionary
If you refer to your original error message, the final part is 'Unable to open or read specified input file' - which would suggest LPC cannot locate them.
Perhaps it would be better to specify the absolute path for the files, rather than relative paths - just to be absolutely sure the LPC converter is looking in the right place.
If the above is correct or you change the paths to absolute paths and you are still unable to download the dictionary, then I recommend you raise a My.Refinitiv support ticket. This forum is primarily for API 'how to' and programming type queries. The moderators are mostly LPC users and not LPC experts - therefore, the assistance we can offer is limited.
Hi @sonali.rane
Is this an existing LPC installation + existing application that has suddenly stopped working or is this a new install and/or new application?
Hi Umer,
Thanks..
It's new LPC installation and trying to fetch market rates very first time through LPC.
The LPC Version is 1.2.0.
Hi Umer,
Thanks..
It's new LPC installation and trying to fetch market rates very first time through LPC.
The LPC Version is 1.2.0.
Hi @sonali.rane
Please refer to section 9.2 of the Refinitiv_Real-Time_Legacy_Protocol_Converter.pdf which comes with the LPC installation package.
Have you set the downloadDictionary parameter to True? If it is False, then can you confirm the data dictionary files are in the configured location e.g.?
*lpc*downloadDictionary : False *lpc*enumFile : /opt/lpc/etc/enumtype.def *lpc*fieldDictionary : /opt/lpc/etc/RDMFieldDictionary
Even if set to True, as per the documentation, if the download fails it would still try to load from the local files - so please ensure the files are present in the locations specified in the above config parameters.
Hello @sonali.rane
By reading your descriptions, it looks like there are 2 components in play: LPC and your RFA application.
Current answers believe that there is a problem with LPC retrieving the dictionary. If that is the case, then please check the LPC log file and report back of any problems.
However, the main description indicates a problem with the RFA application retrieving the dictionary when connecting into LPC. The dictionary request from RFA should traverse through LPC to the Refinitiv Cloud component and come back down. You may want to check the LPC log to verify that your RFA client is correctly connecting to the cloud. Also, see if there is a way for your RFA client to load a dictionary file rather than performing a message request.
LPC 1.2.0.L1 was just launched recently. Can you report the full version string of LPC? There is an additional hash ID with the version string that I would like to see.