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?
Best Answer
-
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
…
}0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛