Duplicate Instrument List using DSS SFTP

neha.kabra
neha.kabra LSEG
in DSS

The issue:


  • For a long time, the instrument list we use to upload instruments from Fusion into DSS remained the same as long as the instrument file name remained unchanged. The instrument file simply used to update the existing lists and NOT create a new instrument list.
  • As you know, the scheduled reports have to be mapped to specific instrument lists, and if those lists change or increase, the scheduled reports will keep running for the same lists they are mapped to regardless.
  • In the case explained above, now the scheduled reports have been running using the old instrument list because DSS creates a new instrument list every day when it receives a new instrument file from Fusion – regardless of the fact that the instrument file name is not new.
  • The strange thing here is that when we push an instrument file manually (the very same file with the very same file name), it updates the existing instrument lists without creating a new one – only on the following day when the transfer happens automatically, DSS creates a new instrument list. We send the same file name every day.
  • The current instrument list that we need to keep updating, which is the one mapped to all scheduled reports, is called MIFL_to_Refinitiv_Instrument_List.

DSS iD - 9032730

Tagged:

Best Answer

  • Gurpreet
    Gurpreet admin
    Answer ✓

    Hello @neha.kabra,

    It could be that the time at which DSS processed the instruments or when your application uploads it to sftp have changed. From DSS standpoint there should be no difference between manually uploading a file, vs programmatic upload of the same file.

    Either way, I would recommend that you raise this issue with DSS product team, who can take a look at sftp logs and advise why this is happening.

Answers

  • neha.kabra
    neha.kabra LSEG

    Hi @Gurpreet

    Thanks for your response.

    Schedules run at 2:30 AM and 7 AM london time.

    The Import process starts at 06:40 from 7 AM extraction. Appreciate your assistance, do let me know if we can discuss this directly with the client.

    NOTES

    Import process started... (04/18/2024 06:40) (diagnostic: 20240418 05:40:12.AM UTC)
    User ID: 9032730
    Request Correlation ID: CiD/9032730/AAAAAA.08e1b051c9a9c0ac/FW.187181607

    Instrument List Import Results: Successfully imported 749 instruments in 00:00:10.

    Standard Segment Counts (717 Total)
    Equity 716
    Mutual Fund 1


    Historical Instruments
    Historical 2


    Instruments not found or restricted content (30):
    ISN, ES0148396007 (not found)
    ISN, ES0130670112 (not found)
    ISN, CH0012221716 (not found)
    ISN, CH0102484968 (not found)
    ISN, CH0038863350 (not found)
    ISN, CH0012005267 (not found)
    ISN, CH0012032048 (not found)
    ISN, CH0126881561 (not found)
    ISN, ES0144580Y14 (not found)
    ISN, ES0113211835 (not found)
    ISN, CH0016440353 (not found)
    ISN, CH0024608827 (not found)
    ISN, CH0013841017 (not found)
    ISN, CH0012549785 (not found)
    ISN, CH0418792922 (not found)
    ISN, ES0113900J37 (not found)
    ISN, CH0025751329 (not found)
    ISN, CH1175448666 (not found)
    ISN, CH0210483332 (not found)
    ISN, CH0024638196 (not found)
    ISN, CH1256740924 (not found)
    ISN, CH0244767585 (not found)
    ISN, CH0011075394 (not found)
    ISN, CH1326854028 (not found)
    ISN, ZZ0M28434583 (not found)
    ISN, ES0173516115 (not found)
    ISN, CH0130293662 (not found)
    ISN, CH0012142631 (not found)
    ISN, ES0109067019 (not found)
    ISN, CH0010570767 (not found)


    ****** MACHINE READABLE NOTES ******
    ITEM TYPE: INSTRUMENT LIST
    NAME:MIFL to Refinitiv Instrument List
    ACTION:REPLACE
    LINE#: 42
    LINE STATUS: NOT FOUND
    LINE#: 45
    LINE STATUS: NOT FOUND
    LINE#: 193
    LINE STATUS: NOT FOUND
    LINE#: 194
    LINE STATUS: NOT FOUND
    LINE#: 195
    LINE STATUS: NOT FOUND
    LINE#: 196
    LINE STATUS: NOT FOUND
    LINE#: 198
    LINE STATUS: NOT FOUND
    LINE#: 199
    LINE STATUS: NOT FOUND
    LINE#: 240
    LINE STATUS: NOT FOUND
    LINE#: 276
    LINE STATUS: NOT FOUND
    LINE#: 319
    LINE STATUS: NOT FOUND
    LINE#: 386
    LINE STATUS: NOT FOUND
    LINE#: 387
    LINE STATUS: NOT FOUND
    LINE#: 389
    LINE STATUS: NOT FOUND
    LINE#: 390
    LINE STATUS: NOT FOUND
    LINE#: 398
    LINE STATUS: NOT FOUND
    LINE#: 424
    LINE STATUS: NOT FOUND
    LINE#: 426
    LINE STATUS: NOT FOUND
    LINE#: 427
    LINE STATUS: NOT FOUND
    LINE#: 428
    LINE STATUS: NOT FOUND
    LINE#: 429
    LINE STATUS: NOT FOUND
    LINE#: 430
    LINE STATUS: NOT FOUND
    LINE#: 431
    LINE STATUS: NOT FOUND
    LINE#: 443
    LINE STATUS: NOT FOUND
    LINE#: 450
    LINE STATUS: NOT FOUND
    LINE#: 537
    LINE STATUS: NOT FOUND
    LINE#: 565
    LINE STATUS: NOT FOUND
    LINE#: 646
    LINE STATUS: NOT FOUND
    LINE#: 696
    LINE STATUS: NOT FOUND
    LINE#: 707
    LINE STATUS: NOT FOUND
    ****** END MACHINE READABLE NOTES ******

    Import process completed (04/18/2024 06:40) (diagnostic: 20240418 05:40:24.AM UTC)

  • Gurpreet
    Gurpreet admin
    https://community.developers.refinitiv.com/discussion/comment/116159#Comment_116159
    Hi @neha.kabra​,

    Please raise this issue with DSS product team. We don't have any visibility into the operational aspects of the services and won't be able to tell why the import is failing.

Categories