UPA for SingleOpen == 1 && AllowSuspectData == 1 streamState should always be “Open”

Following question is from client:
verify w/ Refinitiv (according to UPAC V7.6.1 Reuters Domain Model (RDM) Usage Guide) for SingleOpen == 1 && AllowSuspectData == 1) the streamState should always be “Open” for Source Directory update in ServiceStateInfo or ServiceGroupInfo portion of the message.
------------------------------------------------------------------------------------------------------------------
typedef struct {
RsslUInt64 ServiceState;
RsslUInt64 AcceptingRequests;
RsslState Status; ---------------------------here
} RsslServiceStateInfo;
/* service group information */
typedef struct {
RsslUInt32 GroupLen;
RsslUInt8 Group[MAX_GROUP_INFO_LEN];
RsslUInt32 MergedToGroupLen;
RsslUInt8 MergedToGroup[MAX_GROUP_INFO_LEN];
RsslState Status; ------------------------------here
} RsslServiceGroupInfo;
where
typedef struct
{
RsslUInt8 streamState; /*!< @brief An enumerated value providing information about the state of the stream, populated from \ref RsslStreamStates */
RsslUInt8 dataState; /*!< @brief An enumerated value providing information about the state of data, populated from \ref RsslDataStates */
RsslUInt8 code; /*!< @brief An enumerated code providing additional state information, populated from \ref RsslStateCodes */
RsslBuffer text; /*!< @brief text describing the state or state code */
} RsslState;
Best Answer
-
Thanks for reaching out to us.
According to the document, the item state will remain open under the following conditions.
UPA has been rebranded to ETA in Refinitiv Real-Time SDK. Please consider using ETA instead.
I hope that this information is of help.
0
Answers
-
Client would like to confirm below statement:
If I look at the second column which is the “MESSAGE_SENT WHEN:” to the UPA client the SS is always OPEN. Is this the correct SS from the client perspective when client set to SINGLEOPEN=1 and ALLOWSUSPECTDATA=1 (just want to verify)?
0 -
@Anup Patel
I will not say that the SS is always OPEN for the second column.
If the actual SS from the data feed is CLOSED_RECOVER, the API or the infrastructure will change it to OPEN and it will recover the item on behalf of the application.
However, if the actual SS is CLOSED, the application will retrieve CLOSED. Typically, the SS is CLOSED when a RIC is invalid.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 615 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
- 252 ETA
- 556 WebSocket API
- 38 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
- 3 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.9K Refinitiv Data Platform
- 652 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛