JAVA RFA API RespTypeNum: 10 (MULTIPLE) is not documented anywhere

Usually for this message type, I would get RespTypeNum corresponding to Quote, Trade, Closing run.
But what am I supposed to get for RespTypeNum: 10 (MULTIPLE)?
[ 18:45:04:969 ] ,ItemManager event=121,event handle=225901797, key= /NEAR.Z MsgModelType 6 respMsg.getRespTypeNum: 10=>MULTIPLE
MESSAGE
Msg Type: MsgType.UPDATE_RESP
Msg Model Type: MARKET_PRICE
Indication Flags: DO_NOT_CONFLATE
Hint Flags: HAS_RESP_TYPE_NUM | HAS_SEQ_NUM
SeqNum: 61214
RespTypeNum: 10 (MULTIPLE)
Payload: 164 bytes
FIELD_LIST
FIELD_ENTRY 6/TRDPRC_1: 50.135000
FIELD_ENTRY 11/NETCHNG_1: -0.005000
FIELD_ENTRY 14/PRCTCK_1: Þ (1)
FIELD_ENTRY 40/CTS_QUAL: CLS (214)
FIELD_ENTRY 56/PCTCHNG: -0.0100
FIELD_ENTRY 178/TRDVOL_1:
FIELD_ENTRY 379/SALTIM: 22:30:02
FIELD_ENTRY 1001/GV2_TEXT:
FIELD_ENTRY 1021/SEQNUM: 1237992
FIELD_ENTRY 1022/PRNTYP:
FIELD_ENTRY 1042/GV2_FLAG:
FIELD_ENTRY 1067/EXCHTIM: 22:30:02
FIELD_ENTRY 1392/CLOSE_TIME: 22:30:02
FIELD_ENTRY 3246/PCT_ABNVOL: 0.6547
FIELD_ENTRY 3372/OFF_CLOSE: 50.135000
FIELD_ENTRY 3854/SALTIM_MS: 81002108
FIELD_ENTRY 3889/LS_SUBIND:
FIELD_ENTRY 3900/TRADE_ID: 52983525700695
FIELD_ENTRY 4345/TRD_THRU_X:
FIELD_ENTRY 4756/LSTSALCOND: M
FIELD_ENTRY 4760/THRESH_IND: 1 (1)
FIELD_ENTRY 4763/RETRAN_IND: 1 (1)
FIELD_ENTRY 6377/OFF_CL_TIM: 22:30:02
FIELD_ENTRY 6762/OFF_CLS_DT: 22 SEP 2021
FIELD_ENTRY 13457/HELD_T_IND: (0)
FIELD_ENTRY 14239/TRDRECV_MS: 22:30:02:107
FIELD_ENTRY 14258/OFF_CLS_MS: 22:30:02:108
Best Answer
-
Hi @chris.xiao
The Multiple Update type is mentioned in the RFA JAVA RMDUsageGuide.pdf under the Section for MarketPrice Update Message under the RespTypeNum
RDMInstrument.Update.MULTIPLE=10
My understanding is that one reason for receiving a Multiple type update is on a conflated feed when multiple ticks have been conflated into one tick.
If you are using an internal ADS to consume your data, you can reach out to your Market Data team to understand what if any conflation they have enabled on the service you are consuming the data from.
If you are consuming data directly from Refinitiv e.g. via RTO+LPC or Elektron Connect, to get a full explanation of what may have happened for the above tick, I recommend you raise a Content-Type ticket for the Refinitiv Real-Time product and the content team should be able to help you further.
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.8K Refinitiv Data Platform
- 622 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛