Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • TREP APIs /
  • RFA /
avatar image
Question by Catherine Wong · Oct 30, 2017 at 10:36 PM · rfajavarfa javamifid ii

The impact of the MiFID II on RFA Java 7.6

We are using RFA7.6 and we cannot upgrade from 7.6 to 8 currently. Our application uses the toDate() method only for OMMDateTime and millisecond is enough for our usage. Will our application get any exception when it receives a microsecond or nanosecond timestamp?

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Reply

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by Pimchaya.Wongrukun · Oct 30, 2017 at 10:58 PM

Hello @Catherine Wong

Even the application using RFA 7.6 calls the toDate() method only for OMMDateTime, the application still gets the error “Invalid size 7 for Time”(the application receives microsecond timestamp) or “Invalid size 8 for Time”( the application receives nanosecond timestamp) when the application gets data according to its/TIME type (OMMFieldEntry.getData(OMMTypes.TIME) or OMMFieldEntry.getData(OMMFieldEntry.getOMMType()) is called) before it calls toDate(). Anyway, this problem does not occur if the application uses RFA 8.x or higher supporting microsecond and nanosecond timestamp.

To avoid the errors occurring on RFA 7.6 when it receives microsecond or nanosecond timestamp, the application can check if a field is OMMTypes.TIME and the length is more than 5 that means this is microsecond or nanosecond timestamp, do not decode the field. The snipped example application source code is shown below:

//fiddef is an instance of com.reuters.rfa.dictionary.FidDef
//fe is an instance of com.reuters.rfa.omm.OMMFieldEntry
//data is an instance of OMMData
//if a field is TIME
if(fiddef.getOMMType()==OMMTypes.TIME) {
    if(fe.getData().getBytes().length>5) { //the field is microsecond or nanosecond timestamp which RFA 7.6 does not support
       System.out.println("This is microsecond or nanosecond timestamp, do not decode it.");
      break;//stop decoding this field and start decoding the next field
    } else { //the field is the millisecond or lower timestamp which RFA7.6 supports
      //decode & process the field
      …
    }
} else { //not Time types
       //decode and process not Time types
       …
}
Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
8 People are following this question.

Related Questions

I need an example application using MarketData/TibMsg interface to parse page data

Some native library files found in RFA Java 'Libs' folder

RFA Java API - Convert CONTR_MNTH to java.util.Date ?

Best way to listen to EventQueues in RFA?

Subscribing to RIC multiple times

  • Feedback
  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Careers
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Calais
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRIT
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • World-Check Data File
  • Explore
  • Tags
  • Questions
  • Badges