Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Elektron /
avatar image
Question by duncan_kerr · Jun 26, 2020 at 09:03 AM · equitylevel 2mbo

MBO L2 data : can I truncate keys?

Im looking at MBO L2 data and I can see that the "action" keys can be printed, and look like:

'3339 6563*******************************39ec'

'3330*************************30'

'1****************************1'

(where * are spaces and pad key to 50 chars wide)

however, when I look at the keys in Refinitiv app OMMViewer, you truncate the keys and only seem to use the right hand end of the keys.

My question is - can you explain how the keys work, and what the significance of the lft and right hand bit of the keys is? Can I make any assumptions with spaces in the gap in the middle of the key?

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.

2 Replies

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by jirapongse.phuriphanvichai · Jun 26, 2020 at 10:14 AM

@duncan_kerr

Refer the RDM usage guide, the data type of the MBO key is buffer.

The data in the buffer is a byte array. When printing to a screen, the byte array can be represented as a hexadecimal string, such as '3339 6563'. Moreover, this data can also be represented as an ASCII string.

For example, from the ASCII table, '3339 6563' represents '39ec' in an ASCII string.

Therefore, the left-hand side should be a hexadecimal string while the right-hand side is an ASCII string.

Hexadecimal string => ASCII string

'3339 6563' => '39ec'
'3330'      => '30'

It depends on what methods or libraries that the application uses to print the buffer. Some methods can display the buffer in this format.

'3339 6563*******************************39ec'
'3330*************************30'

Then, OMM Viewer uses ASCII strings for display. This is my assumption.

However, I am not sure about the last example.

'1****************************1' 

What RICs are you using to retrieve that data?


1593164973356.png (33.9 KiB)
1593165815321.png (126.2 KiB)
Comment

People who like this

0 Show 1 · 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.

avatar image
duncan_kerr · Jun 26, 2020 at 01:36 PM 0
Share

I see, the last example was from memory, and wrong. What I was thinking of, was:

KEY ADD "31 1"

If my understanding is correct I can extract the key from the ascii representation of the buffer by disgarding everything up to and including the last space in the string, so:


31****1 => 1

'3339 6563*******************************39ec' => 39ec

avatar image
Answer by duncan_kerr · Jun 26, 2020 at 09:07 AM

OMM VIewer seems to truncate away some of the key:


1593162457478.png (20.0 KiB)
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 >
7 People are following this question.

Related Questions

Over / Under Level in May Entry Class

trailing junk characters in market price data

Can not get streaming data with MARKET_BY_ORDER model by level 2 ric in HKSE

Quote and Trade Conditions for TSE

List of possible values for FID 3132 IRGVAL

  • 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