Thomson Reuters Enterprise Platform for Data Management · The Thomson Reuters Enterprise Platform...

Thomson Reuters Enterprise Platform for Data Management

TREP221RN.110 Date of issue: 14 January 2011

Release Notes Version 2.2.1

Legal Information

© Thomson Reuters 2008 - 2011. All Rights Reserved.

Thomson Reuters, by publishing this document, does not guarantee that any information contained herein is and will remain accurate or that use of the information will ensure correct and faultless operation of the relevant service or equipment. Thomson Reuters, its agents and employees, shall not be held liable to or through any user for any loss or damage whatsoever resulting from reliance on the information contained herein.

This document contains information proprietary to Thomson Reuters and may not be reproduced, disclosed, or used in whole or part without the express written permission of Thomson Reuters.

Any Software, including but not limited to, the code, screen, structure, sequence, and organization thereof, and Documentation are protected by national copyright laws and international treaty provisions. This manual is subject to U.S. and other national export regulations.

Nothing in this document is intended to, nor does it, alter the legal obligations, responsibilities or relationship between yourself and Thomson Reuters as set out in the contract existing between us.

TREP-DM 2.2.1 – Release Notes TREP221RN.110

Chapter 1 Introduction

Contents

Chapter 1 Introduction....................................................................................................................................... 4

1.1 General Information ............................................................................................................................................. 4 1.2 Release Type....................................................................................................................................................... 4 1.3 Release Description and Product Content .......................................................................................................... 4 1.4 Documentation..................................................................................................................................................... 5

Chapter 2 New Features and Improvements ................................................................................................... 6

2.1 New Features and Improvements in This Release.............................................................................................. 6 2.2 CDM Changes ..................................................................................................................................................... 8 2.3 New Features and Improvements in Previous Releases .................................................................................... 9

Chapter 3 Closed Issues ................................................................................................................................. 14

Chapter 4 Known Issues ................................................................................................................................. 23




1.1

1.2

General Information

System Release Version Previous Version

Thomson Reuters Enterprise Platform - Pricing and Reference Data Management Module (formerly known as RRDS)

2.2.1 2.2.0

Thomson Reuters Enterprise Platform Integration Engine (formerly known as REIE)

2.2.1 2.2.0

Release Type

X Bug fix/problem resolution _

Improved/increased capacity

X New functionality/product _

Administration/Other

1.3 Release Description and Product Content

1.3.1 Thomson Reuters Enterprise Platform for Data Management

The Thomson Reuters Enterprise Platform for Data Management (formerly known as REP) is an integrated data-management platform for managing all of your organization’s platform data services. The platform exposes a common API that enables you to leverage platform data services to administer, enable, and assist with a variety of business needs.

1.3.2 Pricing and Reference Data Management Module

The Pricing and Reference Data Module (formerly known as RRDS) is a relational database-management system that provides the capabilities of storing, normalizing, and creating best-of-breed data for the global financial securities markets. Stored data content encompasses a wide array of data for terms and conditions, pricing (end-of-day, snapshot, manual, current, and historic), cross-references for security identifiers, and compliance data across the full spectrum of asset categories. The system is designed to provide scrubbed composite data. For the product’s full capabilities and instructions on its use, refer to the TREP-DM P&R DMM User Reference Guide.

1.3.3 Integration Engine

The Integration Engine (formerly known as REIE) is a data services platform on which business processes can be defined and automated. It provides cross technology and cross platform access to data services provided by platform participants. The Integration Engine provides a collection of proven building blocks that quickly and reliably use deployments of existing software assets, and expose content and functions as platform services.



1.4 Documentation

These Release Notes describe the new and changed features, closed issues and known limitations of this Thomson Reuters Enterprise Platform for Data Management 2.2.1 release. For information about a prior release, see the Release Notes document for that release.

The following table lists the manuals that comprise the TREP-DM documentation set:

Document Title Latest Revised Version Document IDTREP-DM Release Notes 2.2.1 TREP221RN.110TREP-DM P&R DMM Data Operations Guide 2.2.1 TREP221UMRDS.110TREP-DM P&R DMM User Reference Guide* 2.2.1 TREP221RERDS.110TREP-DM Platform API Reference Guide* 2.2.1 TREP221REAPI.110TREP-DM CDM Schema Reference Guide* 2.2.1 TREP221RE.110TREP-DM Getting Started Guide* 2.2.1 TREP211IG.110TREP-DM Installation Guide 2.2.1 TREP221IP.110TREP-DM Technical Operations Manager User Guide 2.2.1 TREP221REEIE.110TREP-DM P&R DMM System Administration Guide 2.2.0 TREP220ADRDS.100TREP-DM Feed Handler Framework SDK Guide* 2.2.0 TREP220REAPI.090TREP-DM DSS Feed Administration Guide* 2.1.0 TREP210ADRDS.090TREP-DM RMDS Feed Administration Guide* 2.1.0 TREP210ADMDS.090TREP-DM Platform Overview Guide 2.0.1 TREP201OV.090TREP-DM Data Model Overview* 2.0.1 TREP201RERDS.091TREP-DM MarkIT Feed Administration Guide* 2.0.1 TREP201ADMKT.090TREP-DM Parser and Loader User Guide* 2.0.1 TREP201ADPAR.090TREP-DM Parser and Loader Operations Guide* 2.0.1 TREP201IGPAR.090* - Document is bundled only with the Platform+DMM version of TREP-DM


Chapter 2 New Features and Improvements


2.1 New Features and Improvements in This Release

The Thomson Reuters Enterprise Platform for Data Management 2.2.1 release includes the following new features and improvements:

Version Functionality

2.2.1 The Price Scrubbing Results, Advanced Price Scrubbing, Add Manual Price and Pending Manual Prices/Rates pages in Data Ops Manager now provide a Comments field (associated with each result), in which users may enter a comment describing the action taken.

2.2.1 The Feed Status Page has been enhanced to provide better information about price scrubbing across multiple client systems.

2.2.1 The Platform API and Canonical Data Model have been extended with support for additional data entities.

2.2.1 The Platform API now supports a SuperPut operation for the Indicative payload type. This capability includes the creation of new instruments.

2.2.1 Selected rating types have been removed or replaced. For details, refer to section 2.2: CDM Changes.

2.2.1 Watchlist to Client-System synchronization has been improved. For details, refer to Chapter 5: Working with Data Sources and Watchlists in the TREP-DM P&R DMM Data Operations Guide.

2.2.1 An additional algorithm (tolerance type) called Zero Value check has been introduced as an enhancement to the Price Scrubbing capability. This new algorithm checks whether the incoming price is zero.

2.2.1 An additional configurable field called "Illiquid Instrument Indicator" has been introduced. This indicator will be used to decide whether to ignore the Time part of the Evaluate Date/Time during Mid Price Recalculation.

2.2.1 The dependency on previous day's prices for has been removed for the following price tolerance types:

Bid

Ask

Negative

Zero Value

Time Check

Price Range

2.2.1 Close price is now available when assigning an instrument to a Client System and on the Watchlist synchronization pages.

2.2.1 Support was added for RMDS IDN record/template numbers 6, 26, 69, 75, 78, 89 and 191.



Functionality Version

2.2.1 A new configurable flag called "BlockVendorMidValue" has been introduced. Price load procedures will now load or block vendor supplied Mid values based on whether the mentioned flag is unset or set on the Application Settings page. By default BlockVendorMidValue is set to 0 (vendor reported mid prices are loaded)



2.2 CDM Changes

Due to ongoing enhancements and support of ratings, the following changes have been made to CDM ratings types (used for both instrument and party ratings). The following table shows which rating types have been removed and which have been replaced. Where applicable, feeds need to be updated with this information.

Type code Description Mapping

SBDD S&P's Subordinated - D Not supported by S&P. No mapping.

SBDF S&P's Subordinated - F Not supported by S&P. No mapping.

SBFD S&P's Bank Fundamental Strength Ratings - D SGEBLT

SBFF S&P's Bank Fundamental Strength Ratings - F Not supported by S&P. No mapping.

SBSD S&P's Bank Survivability Assessment - D SGESLD

SBSF S&P's Bank Survivability Assessment - F SGESLF

SCGD S&P's Corporate Governance Score - D Not supported by S&P. No mapping.

SCGF S&P's Corporate Governance Score - F Not supported by S&P. No mapping.

SCPD S&P's Commercial Paper - D Not supported by S&P. No mapping.

SCPF S&P's Commercial Paper - F Not supported by S&P. No mapping.

SFED S&P's Long-term Financial Enhancement - D SGEELD

SFEF S&P's Long-term Financial Enhancement - F SGEELF

SFPD S&P's Long-term Financial Program - D SGEPLD

SFPF S&P's Long-term Financial Program - F SGEPLF

SFSD S&P's Long-term Insurer Financial Strength - D SGEFLD

SFSF S&P's Long-term Insurer Financial Strength - F SGEFLF

SIND S&P's Long-term Issuer National Scale Ratings - D SGENLD

SINF S&P's Long-term Issuer National Scale Ratings - F SGENLF

SISD S&P's Short-term Issuer Credit Rating - D SGEISD

SISF S&P's Short-term Issuer Credit Rating - F SGEISF



Type code Description Mapping

SJBD S&P's Junior Subordinated - D Not supported by S&P. No mapping.

SJBF S&P's Junior Subordinated - F Not supported by S&P. No mapping.

SPID S&P's Long-term Issuer Rating - D SGEILD

SPIF S&P's Long-term Issuer Rating - F SGEILF

SSDD S&P's Secured Subordinated Debt - D Not supported by S&P. No mapping.

SSDF S&P's Secured Subordinated Debt - F Not supported by S&P. No mapping.

SSED S&P's Senior Secured - D Not supported by S&P. No mapping.

SSEF S&P's Senior Secured - F Not supported by S&P. No mapping.

SSUD S&P's Senior Unsecured - D Not supported by S&P. No mapping.

SSUF S&P's Senior Unsecured - F Not supported by S&P. No mapping.

STND S&P's Short-term Issuer National Scale Ratings - D SGENSD

STNF S&P's Short-term Issuer National Scale Ratings - F SGENSF

2.3 New Features and Improvements in Previous Releases

The following table lists the new features and improvements that were included in previous releases of TREP-DM:


2.2.0 The system maintains a complete history of Indicative (Terms and Conditions) Attributes.

2.2.0 Instrument Profile Screens can now be customized and extended

2.2.0 The system can now validate instrument indicative data by using user-defined Scrubbing Rules.

2.2.0 Relationships between data elements (attributes) that help govern indicative scrubbing activities can now be viewed on the Data Operations Manager User Interface.

2.2.0 You can now give Price Tolerances an effective date (to make it take effect in the future) and expiration date.

2.2.0 TREP-DM includes a Work Item Management service that manages workflow for system-generated items (which require human intervention).

2.2.0 Manually entered Indicative Data overrides can now be manually deactivated so that new data from vendor feeds are used in the Golden Copy.

2.2.0 Data Ops Manager users can perform a “Check-Out” operation on an Instrument to prevent other users from making conflicting changes on the same Instrument.




2.2.0 The new Feed Status and Feed Management pages in Data Ops Manager provide consolidated locations from which to monitor and work with all registered Interactive Feeds in the system.

2.2.0 Watchlist maintenance tasks are now subject to Maker/Checker approval.

2.2.0 The attribute coverage of Indicative (Terms and Conditions) payload in the Platform API has been enhanced

2.2.0 The Platform API Excel Sample Client has been integrated into the Web Sample Client web interface.

2.2.0 The Platform API has been extended to support Get and Put operations for Curves

2.2.0 The Platform API has been extended to support Put operations for Schedules

2.2.0 The Platform API can Publish Terms and Conditions, Identifiers and Pricing data

2.2.0 The system now provides a mechanism to flag potential Matches on Instrument Indicative data based on user-defined matching rules. Users can review the potential Matches and optionally Merge matching instruments

2.2.0 The system now maintains data for Parties

2.2.0 The Message Analysis functionality in Tech Ops Manager includes data enrichment and validation functions.

2.2.0 A new Reporting Module includes a set of packaged reports along with the necessary tools (SDK) to create rich custom reports.

2.1.1 Schema and Event objects in Technical Operations Manager can now be permissioned.

2.1.1 New functionality has been added to upload assemblies that contain custom expression functions as embedded resources.

2.1.1 The Expression editor introduced for Message Analysis enrichment is now expanded to process correlation, dashboard data part series and subscription filters.

2.1.1 The Expression now includes an intelligent-assistance feature similar to those found in many integrated development environment (IDE) applications.




2.1.0 Support has been added for the following instrument types:

Derivatives:

Equity Indices

Credit Indices

Commodity Indices

Commodity Futures

Options

Index Options

Commodity Options

2.1.0 All RMDS feeds have been merged into the current intraday feed. The adapters share has been removed and the Terms and Conditions RMDS feed has been deprecated.

2.1.0 The Indicative Data View enables you to see a composite of general instrument-profile data or instrument-profile data at the market level or from a particular market. That is, rather than seeing the raw vendor data for an instrument, you see the data as it has been prepared according to the needs of the current client system.

2.1.0 User defined instrument types enable you to tag a particular type of instrument in TREP-DM, so that all can be treated the same way. In other words, you can create a relationship between instrument types that does not otherwise exist.

2.1.0 A new Task Viewer page in Data Ops Manager gives you access to tasks that have been configured in Tech Ops Manager. This enables the user to start the execution of Business Transaction Events from Data Ops Manager.

2.1.0 You can now work with Calendars from within Data Ops Manager. Calendars originating in Data Ops Manager are able to link to (and use the rules from) Calendars managed by the Integration Server and Tech Ops Manager.

2.1.0 A new IMAP adapter has been developed that downloads email messages and attachments from an IMAP email server.

2.1.0 The Platform API has been enhanced to perform GET and PUT operations for the following payload types:

Identifiers

Ratings

Indicative Data

2.1.0

The RMDS adapter has been enhanced to enable the automatic setup of Cap, Floor, and Collar instruments.




2.1.0 The DataScope Select (DSS) and DataScope Equities (DSE) feed handlers have been enhanced to support the following instrument types:

Derivatives:

Equity Indices

Credit Indices

Commodity Indices

Commodity Futures

Options

Index Options

Commodity Options

2.1.0 The Message Analysis functionality in Tech Ops Manager has been enhanced to enable payload enrichment in TREP-DM.

2.0.1 The P&R DMM web site is integrated with the Activity Monitor. The new web site has been rebranded as “Data Operations Manager”.

2.0.1 TREP-DM is now available in two versions:

Platform Only

Platform + Pricing and Reference Data Management module

2.0.1 Added support for Windows Server 2008 64 bit

2.0.1 Added support for SQL Server 2008

2.0.1 Platform API now includes Get Identifiers

2.0.1 A new web sample client is available for the new pricing API is now available.

2.0.0 beta For ForEx instruments, base and transactional currency data is no longer stored or retrieved at the Pricing level. Currency details can be retrieved from a ForEx instrument’s Profile page (also known as Indicative data). It is no longer necessary to specify a currency when adding a ForEx instrument to a Client System, when configuring its price tolerances, or when adding a manual price.




2.0.0 beta The following change is made in the behavior of the Scrubbing Results Report search filters:

Previous Behavior:

When the value of Scrubbing Action Type is set to No Action Required or Pending Maker Action, the Start Date and End Date filter applies to Price Evaluation Date.

When the value of Scrubbing Action Type is set to Maker Action Complete/Pending Checker Action, the Start Date and End Date filter applies to Maker Action Date.

When the value of Scrubbing Action Type is set to Checker Action Complete, the Start Date and End Date filter applies to Checker Action Date.

New Behavior

The Start Date and End Date filter always applies to Price Evaluation Date.

The Scrubbing Action Type setting does not affect the Start Date and End Date filter.


Chapter 3 Closed Issues


The following table lists the issues that were resolved in the current and previous releases of TREP-DM:

Issue Number

Closed in Release

Description

2890 2.2.1 After firing an event, in Tech Ops Manager the first line item turns red, indicating an error. However, everything goes through as it should. The DataTrans logs contain no error.

4375 2.2.1 Excel sample client shows only a subset of ratings

4450 2.2.1 Vendor Hierarchy for the Client System is ignored when it is set for all Instrument Groups

4473 2.2.1 Server error is displayed after attempt to search for results on Activity Monitor->Data Flows page when [Status] drop-down is not equal to Unspecified'

4552 2.2.1 Unsuccessful Bulk Insert operation of MarkIt data is not raised as a failure on the report pages.

4628 2.2.1 When a Platform API Put is executed on the Ratings Payload, an error that says "attempt complete, pending authorisation" may be displayed

4774 2.2.1 The scrubbing results page timed out when accessed from the Client System menu or from the Interactive Feed Management page. This has been fixed.

5168 2.2.1 Incorrect Feed Id value is displayed for indicative scrubbing results in some situations on the Indicative Scrubbing Results screen

5173 2.2.1 In the Web Sample Client > Indicative (T&Cs) > Get, an exception is displayed when performing a Get operation on certain instruments

5195 2.2.1 Any external client program making calls into the Work Item Management Service may occasionally get a connection error

5262 2.2.1 Prices which fail a scrubbing rule were still showing up in the latest price screen. This has now been addressed

5330 2.2.1 Vendor sources that display the list of Curve identifiers are not displayed in the Curves > Identifiers > Vendor sources tab in the Client System view

5423 2.2.1 Only the required fields are sometimes displayed on Instrument profile.

5431 2.2.1 On the Matching Results page, results are duplicated for each element that is configured in the rule though the data itself is not duplicated

5432 2.2.1 The Curve constituents page on the Data Ops Manager may sometimes display duplicate entries though the data itself is not duplicated

5444 2.2.1 Mid Price was not appearing on the Latest Prices screen. This has been addressed

5457 2.2.1 The Priority (Weight) filter on the Advanced Queue Browser is ignored when performing searches

5461 2.2.1 On the Pending Indicative screen there was no ability to perform a bulk operation on the entire page. The ability to do an "Authorise All" and "Reject All" has now been introduced.

5462 2.2.1 On the Pending cross references screen there was no ability to perform a bulk operation on the entire page. The ability to do an "Authorise All" and "Reject All" has now been introduced.



Issue Closed in Description

Number Release

5467 2.2.1 Changed values of any modified fields are displayed even if they still have pending status though the data updates are awaiting Checker authorization in reality

5471 2.2.1 Errors are displayed during authorization of the pending Indicative changes. Nevertheless, the data updates are performed correctly

5504 2.2.1 Stale price records are sometimes marked as failed even if prices of compared days are different.

5517 2.2.1 Records in [Xref Identifier] column are shown incorrectly for Get request on [Identifiers] tab in the Excel Sample Client

5521 2.2.1 Two price values from different sources may be returned for the same price type when golden copy data is requested

5543 2.2.1 On the Indicative Issue and Market Level Pages, a message saying "The given key was not present in the dictionary" may sometimes be displayed.

5548 2.2.1 In the Platform Only version the location of databases and logs can be entered in the grid as well as in the header section. This could cause confusion

5556 2.2.1 An “Unhandled Exception” message appears when a user tried to authorize a manual price that has already been approved. This has now been addressed.

5587 2.2.1 When assigning an Instrument to Client System on the DOM UI, Market was a mandatory field. This field has now been made optional.

5647 2.2.1 For Tolerance Types Bid Ask Comparison, Negative Value Check, Zero Value Check, Stale, Time Check and Price Range the Price Scrubbing Engine was mandating the existence of the previous day's price. This restriction has now been removed.

5648 2.2.1 The scrubbing engine threw a "Divide by zero error" intermittently. This has been addressed.

5672 2.2.1 Incorrect Exchange ID in incoming RMDS data was causing Scrubbing to skip prices. This has been addressed with a mapping workaround.

5682 2.2.1 Derived Mid price was displayed on the Price History screen but not on the Latest prices Screen. This has been addressed

5685 2.2.1 When a Watchlist was synchronized with a Client System, the Price Recalculation type picked was not being respected. This has been fixed.

5685 2.2.1 When a Watchlist was synchronized with a Client System, the Price Recalculation type picked was not being respected specifically for instruments that belonged to the Forex/MM Rates Instrument Group. This has been addressed.

5687 2.2.1 Stale Value Check was not displaying the correct compared-with information in the Scrubbing results screen. This has been addressed

5688 2.2.1 When two different Price Scrubbing Rules were configured for two different Instrument Types within the same Instrument Group the rule for the wrong Instrument Type was being selected by the Scrubbing Engine. This has been fixed.

5689 2.2.1 Relative Value Check was behaving wrongly when negative price values were encountered. This has been fixed.

5745 2.2.1 It was not possible to clear exceptions from Price scrubbing results screen. This issue has been addressed.




Number Release

5747 2.2.1 Relative tolerance rule was comparing the current Derived Mid Price against the previous day's Vendor reported MID Price. The algorithm has been changed now to compare the Derived Mid Price against the previous day's Derived Mid Price.

5747 2.2.1 Relative tolerance rule compared the incoming price against the previous day's MID Price in the universe rather than the Mid price for that Client System. This has been addressed.

5777 2.2.1 Public API for Indicative in the SuperPut mode for an existing instrument did not work. This has been addressed

5778 2.2.1 Public API - Indicative Put creation of a new Equity should not require Issuer to be provided. This has now been addressed

5810 2.2.1 An error was thrown while creating a new equity using the Public API. This was addressed by allowing authorization via the DOM of newly created manual instrument via the Public API.

5882 2.2.1 Last Traded and Settlement Price types were not displayed on the Price History Page and Latest Prices Page. This has now been implemented

5883 2.2.1 Cannot synchronize close price attribute to client system

5885 2.2.1 Cannot create scrubbing rules for Instrument Group, for certain Instrument Group/Type/SubType combinations. This has been addressed

5980 2.2.1 The Issuers - Parties Synchronization script was updated to make it more performant.

5981 2.2.1 Additional translations were included for the public API ratings Superput/Put were implemented. Error handling was enhanced and SQLite locking was introduced for concurrent access.

5982 2.2.1 This release fixes the following in release 3.8.0 of TREIE:

Zip Interceptor unzipping archives incorrectly.

Error on Task List page in DOM web site.

Error with date conversion in DOM on the Activity Monitor --> Data Flows

Error with date conversion in DOM on the Activity Monitor --> Processes

RFAGetHost enhancement to fix issue with long timeout when P2PS6 server connection is not available

Extended attributes are removed from receivers when doing an import

Fix for attempting to remove extended attributes from receiver properties

When the system has a lot of TXs the startup time of the ASH is adversely affected

4112 2.2.0 When creating a Web Service client for the REP API from popular Java environments such as NetBeans and Eclipse, the default code generation tools such as JWS fail to produce a working set of classes. This is caused primarily by the .NET DataTable that is used as the return type for the Excel API calls. The DataTable class produces XML “Any” properties produced as part of its schema.




Number Release

4433 2.2.0 When executing an event that has a TX with parameters, the grid displays parameter values at the bottom of the page. Related to 4521.

4450 2.2.0 Vendor Hierarchy for the Client System was ignored when it is set for all Instrument Groups. This has been addressed

4473 2.2.0 Server error was displayed after an attempt to search for results on [Activity Monitor]->[Data Flows] page when [Status] drop-down does not equal 'Unspecified'. This has been addressed.

4497 2.2.0 When services are restarted via Tech Ops Manager, an ASH service threw an exception due to a file being locked. This has been addressed




Number Release

4503 2.2.0 "[Indicative] > [Issue Data] > [Edit] – no changes were applied to the following fields:

amount_needed_to_convert

calculation_type_id

conversion_cost_cash

conversion_cost_cash_currency_id

conversion_cost_numeric

eps_diluted

eps_diluted_currency_id

eps_diluted_date

export_indicator

fmv

gics_code

next_capital_adjustment_marker_id

next_conversion_cost_cash

next_conversion_cost_cash_currency_id

next_conversion_cost_numeric

next_resultant_amount

next_resultant_amount_currency_id

next_resultant_amount_numeric

next_strike_price

next_strike_price_currency_id

y_id

ded_to_convert

original_wala

reg_d_indicator_id

resultant_amount

resultant_amount_currenc

second_exercise_date

value_amount_currency_id

value_amount_nee

This has been addressed.

4505 2.2.0 tion anager displayed the error “invalid username or

password”. This has been addressed

If the Management Service Layer (MSL) was installed in Enterprise Platform authenticamode, some pages in the Data Ops M




Number Release

4521 2.2.0 "Server error occurred when executing the following events from Technical Ops Manager:

Maintenance: Check for Scheduler Failover

Maintenance: Fail-over Occurred

Maintenance: Failure of Clear Logs

(Related to 4433)

This has been addressed.

4533 2.2.0 Ratings SuperPut showed two records on the RRDS website for every record manually inserted. This has been addressed

4554 2.2.0 Errors were given out when procedure markit_red_entities_pr is running. The root cause that generated the error has been addressed

4568 2.2.0 In the Client System view, users had to scroll to the right to view the Client system drop down box in some cases. This has been addressed

4670 2.2.0 Errors were reported in the event log when several RMDS requests for Intraday data sent since only 1 ASH server running in 64 bit environment. This has been addressed

4684 2.2.0 "Out of Memory" exception was thrown when RMDS data was requested using a large watchlist. This has been addressed

4693 2.2.0 TREP-API web client: put operations were blocked in Internet Explorer 8. This has been addressed

4369 2.1.1 (RMDS) The value of OPEN_PRC field is not being inserted to RMDS_TEMPLATE_77 table. For example, when RMDS data for .14JA (RIC) is requested, the raw data file contains <OPEN_PRC type="Double">97.6588</OPEN_PRC>, but no data is inserted to the OPENING_PRICE column of the RMDS_TEMPLATE_77 table

Note: There was a similar problem with the Total_Volume_2 field. This is fixed as well.

4528 2.1.1 Watchlists: Source parameter for an instrument was being added to a watchlist during back synchronization with a Client System. This is now fixed.

4590 2.1.1 Cannot Access file in compiled interceptor in RMDS feeds. This is now fixed.

4591 2.1.1 RMDS Intraday feed would not load reference data correctly. This is now fixed.

4592 2.1.1 RMDS load no longer fails with error “xml-file is used by another process”.

4648 2.1.1 RMDS Intraday loads no longer fail due to transaction timing out while stored procedure still running.

4669 2.1.1 Errors no longer occur when an executing business transaction attempts to use a component in the dtLibMod.dll assembly.

1731 2.1.0 In certain environments, exporting configuration would throw a constraint error. This is now fixed.




Number Release

2413 2.1.0 If a DSS, RMDS or a MarkIT data load fails, the jobs are now automatically resubmitted.

2599 2.1.0 CDS-Spreads can now be added, edited, and deleted in Data Ops Manager.

2703 2.1.0 In instrument search results in a client system, an error no longer occurs if the user tries to Edit or Delete an instrument created manually for ‘Universe and Client System’

2897 2.1.0 When adding a manual rating to an instrument in a client system, the system no lonthe rating with a client ID that is non-zero (i.e., non-Universe).

ger adds

3056 2.1.0 An issue with lack of filtering or ordering on indicative screens has been resolved.

3278 2.1.0 Graph X Axis on Price History For Almonth of data is plotted.

l Exchanges page is now readable when more than one

3394 2.1.0 Floating leg fields are now editable.

3481 2.1.0 REP is now able to process Bloomberg relative indices.

3684 2.1.0 Duplicate entries for call schedule have been corrected.

3779 2.1.0 Inactive Bonds have the status Active in RRDS although data This is now fixed.

are updated daily using RDSS.

3797 2.1.0 DSS Feed over REIEAPI now works with NLB network name

3823 2.1.0 id and Ask prices are auto accepted. In the case when the

scrubbing is performed and Bid or Ask price is failed, but accepted, the mid price is not Mid price is calculated only if B

calculated. This is now fixed.

3840 2.1.0 eds is inaccurate because a single record may be chosen to be “skipped” multiple times. This causes the skipped count to be The “Skipped” scrubbing count shown on Interactive Fe

incremented at every decision point. This is now fixed.

3971 2.1.0 ates RMDS Terms &Conditions adds identifiers cross-reference data for some Forex/MM Rwith exchange <> NA. This is now fixed.

3985 2.1.0 a value in the Market column, then when the watchlist is used to request DSS data,

The Market column in watchlists is supposed to be used in watchlist-to-client system synchronization only. However, if a security added to watchlist doesn't have [Source] valuebut hasthe extract will be requested for the specific exchange defined by the Market. This is now fixed.

3988 2.1.0 In the Advanced Scrubbing View, a Checker is unable to authorize or reject pending recorcreated by Maker. This is now fixed.

ds

3989 2.1.0 nchronization may not

security When using integrated authentication, the automatic user-group sywork if Active Directory returns a group name with trailing spaces. This results in the group not being added to the user as it should. This is now fixed.

3990 2.1.0 apter is cached, it would lose its connection to the server. When When the SFTP ad

reconnecting it would reconnect on the default directory, as opposed to the target directory. This is now fixed.




Number Release

3993 2.1.0 In the Advanced Scrubbing View, prices accepted on this page (by both maker and checker) are no longer shown as pending on scrubbing results page.

4004 2.1.0 Memory usage of w3wp.exe process is constantly growing on Web Server. This is now fixed.

4006 2.1.0 -bit environment, after importing the configuration and registering the BTH, the first In a 32

time the BTH is restarted it would sometimes throw an error and fail to start. This is now fixed.

4007 2.1.0 Watchlist-to-client system synchronization stops running when it tries to add a duplicate security to client system; no errors/messages given out. This is now fixed.

4061 2.1.0 RMDS Data Feed: When running in German locale fractions would not load (BCP failsThis is now fixed.

)

4062 2.1.0 ion

dtLog..procFindAllLogsPageFiltered not updated when upgrading REIE configuratdatabases from 3.5.4 to 3.6.0. When upgrading dtLog from 3.5.4 to 3.6.0 the dtLog..procFindAllLogsPageFiltered procedure is not updated. This is now fixed.

4103 2.1.0 The Platform Only Install now allows users to specify the target database folder.

4125 2.1.0 Incorrect mapping of volatility and strike for Tullett instruments. This is now fixed.

4126 2.1.0 Instrument identifiers not being mapped from DSS Terms and Conditions. This is now fixed.

4127 2.1.0 Manually editing indicative data is not client system specific. This is now fixed.

4129 2.1.0 Reference data for money instruments not complete (tenure). This is now fixed.

4141 2.1.0 Missing evaluation date and time for contributed RICs. This is now fixed.

4142 2.1.0 uled events not running when they are supposed to. This is now fixed. Sched

4324 2.1.0 Incorrect transactional currency in lookup table for Argentine Peso deposit rates. This is now fixed.

4351 2.1.0 CDS Issuer Spreads sort order needs to change to descending order. This is now fixed.

4449 2.1.0 Wrong finish time of price load in interactive feeds screen. This is now fixed.

1237 2.0.1 When API client requested pricing data from REIE, field names of the requested data would start with security group name. This is now fixed.

2599 2.0.1 b interface. CDS-Spreads: can now be added, edited, and deleted in the we

2792 2.0.1 Incorrect value was passed into [gdi..client_system_securities] -> [currency_rate_type_id] field after adding security into client system. This is now fixed.

3326 2.0.1 frequently. This is now fixed. RRDS MarkIT Red Entities Import would fail

3516 2.0.1 Strike price data from RMDS Terms and Conditions loads are now being mapped from GEN_TEXT16 for CAP/ FLOOR instruments.

3517 2.0.1 Options, Currency data from RMDS Terms and Conditions load are now being mapped GV2_TEX

from T for CAP/ FLOOR and Swaption instruments.

3518 2.0.1 Bonds loaded from DSS were being mapped as Equities. The instrument group is now editable.




Number Release

3520 2.0.1 Manually added reference data is now auditable.

3533 2.0.1 'Out of memory exception' in REIE. This is now fixed

3645 2.0.1 occur while running the RMDS adapter manually via the REIE Intermittent failures wouldevent. This is now fixed.

3681 2.0.1 Strike price for caps are now saved as a part market data and not static data.

3729 2.0.1 Bond Schedules files A "Transaction was deadlocked" error would sometimes occur when 15were dropped into the DSS SingleRequestIn folder. This is now fixed.

3733 2.0.1 ould result in the ASH When the ASH service timed out when executing a TX unit, it cbecoming unresponsive to further requests. This is now fixed.

3743 2.0.1 es occur on the Interactive Feed Management page when RMDS Intraday data is loaded, Bulk insert errors sometim

3331 2.0.0 beta g leg fields were not editable for Derivatives IRS - Interest Rate Swap. This is now Floatin

fixed.

3580 2.0.0 beta a [Export as RMDS request] functionality of WEB UI cannot be consumed by RMDS. XML files generated vi


Chapter 4 Known Issues


The following table lists the known issues in TREP-DM 2.2.1:

Issue Number

Description Workaround

430 The InstallShield installer for the RRDS web application currently sets the ASP.NET version number to 2.0.50727 for all web sites hosted by the web server on which the RRDS web application is installed.

Manually restore the previous version number for all other sites if applicable.

1369 When authorizing issuer mergers, RRDS can generate an error.

None.

3208 On the Scrubbing Results page, Upper and Lower Limits for Tolerance type "Relative" shows percent values. For example, if tolerance limit is set to 20 percent Lower limit is shown as 0.0000 and upper limit as 0.2000. A price of 1.5 will show up as passed. This is misleading.

None.

3537 It is not possible to add more than one tolerance into client system with single difference in [Price Selection Type].

None.

3994 When viewing the Activity Dashboard in Tech Ops Manager, the Data Ops Manager page header is displayed.

None.

4112 When creating a Web Service client for the REP API from popular Java environments such as NetBeans and Eclipse, the default code generation tools such as JWS fail to produce a working set of classes.

This is caused primarily by the .NET DataTable that is used as the return type for the Excel API calls. The DataTable class produces XML “Any” properties produced as part of its schema.

Generate code from a different tool; or write the wrapper classes manually; or call the Web Service in a less well-defined manner, such as by using direct HTTP POSTs.

4368 Data with "&" symbols are incorrectly inserted to RMDS_TEMPLATE tables

None.

4433 When executing an event that has a TX with parameters, the grid displays parameter values at the bottom of the page. Related to 4521.

None.



Issue Description Workaround

Number

4497 When services are restarted via Tech Ops Manager, an ASH service throwing an exception due to a file being locked.

Restart the services from Services on the Windows Server application box where the ASH services are installed.

4503 [Indicative] > [Issue Data] > [Edit] – no changes are applied to some fields.

List of fields for which changes are not being applied.

amount_needed_to_convert

calculation_type_id

conversion_cost_cash

conversion_cost_cash_currency_id

conversion_cost_numeric

eps_diluted

eps_diluted_currency_id

eps_diluted_date

export_indicator

fmv

gics_code

next_capital_adjustment_marker_id

next_conversion_cost_cash

next_conversion_cost_cash_currency_id

next_conversion_cost_numeric

next_resultant_amount

next_resultant_amount_currency_id

next_resultant_amount_numeric

next_strike_price

next_strike_price_currency_id

original_wala

reg_d_indicator_id

resultant_amount

resultant_amount_currency_id

second_exercise_date

value_amount_currency_id

value_amount_needed_to_convert

None.




Number

4505 If the Management Service Layer (MSL) was installed in Enterprise Platform authentication mode, some pages in the Data Ops Manager will give an error of “invalid username or password”. This is due to the web site using Windows Authentication while the MSL is using Enterprise Platform authentication.

In the configuration file for the MSL service (m35.Management.Service.exe.config), modify the epdmSecurity node (near the bottom) by adding the following attribute:

ignoreBlankPasswordInEpdmMode = True

The node should now appear as follows:

<epdmSecurity authenticationMode="Epdm" ignoreBlankPasswordInEpdmMode="True"" />

In Tech Ops Manager, the users that use Data Ops Manager need to be created/recreated so that the user name includes their full domain name. For example, for a user name joe.smith in the Foo domain, the format should be foo\joe.smith.

4516 Tasks with names "nnn Call" (i.e. RMDS Feedhandler IntraDay Event Call), are not returned for searches containing “call”. In addition, searches for tasks containing 'all' return only the "Maintenance: Clear Logs" task.

None.

4521 Server error occurs when executing the following events from Data Ops Manager:

Maintenance: Check for Scheduler Failover

Maintenance: Fail-over Occurred

Maintenance: Failure of Clear Logs

Related to 4433.

None.

4554 Errors given when procedure markit_red_entities_pr is running.

None.

4670 Errors in event log when several RMDS requests for Intraday data sent since only 1 ASH server running in 64 bit environment.

None.

4693 TREP-API web client: put operations are blocked in Internet Explorer 8.

None.

4707 DataScope Select data loads sometimes do not terminate as expected.

None.

4717 Exceptions thrown in RFA-out files are not reported on the Interactive Feeds page, in Tech Ops Manager, or in the event log.

None.




Number

4719 Sometimes the generated RFA-out files are missing entries for some RICs.

None.

4748 Identifier fields are not case sensitive. None.

4770 TREP-DM accepts invalid combinations of Ratings data (such as Agency, Rating, and Status) that are supplied by the DSS feed handler. However, invalid combinations that originate from Data Ops Manager or from the Excel and Web API Sample Clients result in an error and are not accepted.

None.

5158 Work Item Management Service is not Uninstalled when the user removes the service from Add/Remove Programs

Run C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\installutil -u "C:\Program Files\Thomson Reuters\Enterprise Platform - DM Exception Management Framework Service\EmfServic.exe" at command prompt to remove the service from the Windows Services Applet. 2) delete the folder: "C:\Program Files\Thomson Reuters\Enterprise Platform - DM Exception Management Framework Service"

5405

5866

An incorrect Feed ID value may be displayed for indicative scrubbing records on the Indicative Scrubbing Results page in some situations. As a consequence, the corresponding scrubbing result cannot be acted upon unless additional filter criteria are applied to narrow the results to the specific record.

Narrow the results to the specific record using additional filter criteria

5441 Server error is shown after clicking the Run button for tasks that contain a value with hyperlink in edit box.

None.

5464 Integration Engine processes remain blue in color although finished.

None.

5465 Last Update date and Started date are swapped in the Tasks status for RMDS adapter

None.

5500 The Profile page allows deactivation of "key fields" on Manually created instruments

Ensure that the fields "Required by System" are not deactivated on Manually created instruments unless there is at least one other feed provided value for such fields.

5509 A "No such file or directory" error may occur when multiple DSS feeds are started simultaneously

Retry the feeds that displayed this error.




Number

5519 [Rating] > [Details] > [Add New] – Rating records with some combinations of Agency, Type and Rating cannot be added manually

None. A validated set of Rating Agency, Type and Rating combinations are allowed from the UI. The feed handlers on the other hand bring in feed provided data without this validation.

5523 User group with [Class Group]='Superput' is not applied for client system of user.

Restart IIS.

5525 In the Excel API Client Put Prices operation does not generate pending records when a PUT is performed for two or more identifiers

None.

5528 In the Platform only Installation, the WEB UI asks the user to enter the user name and password repeatedly when the Home page is opened.

Modify the permissions on the Silverlight package (Web.DataAnalytics.Dashboard.xap) has read access. For details refer to the Chapter on Installing Web Server Components in the Installation Guide.

5546 Search does not work on the Task List page None.

5547 Some application settings (e.g. DataTransServer) are not available/visible to view or edit in the Platform Only version

Make the necessary edits in the key_value_pair table in the rep_common2 database.

5553 While editing an Instrument Profile, manually entered values in fields containing formatted data (e.g. dates) cannot be deactivated.

Manually edit the value on the field to the desired value.

5580 Several prices with different exchanges and evaluation dates may be created by the RMDS adapter for a few instruments.

None.

5635 If a party is opened within a Client System that has [Use Available Source Indicator] = ‘Yes’ and which doesn’t have Parties Vendor Hierarchy, no data is shown on [Profile], [Rating], [Names] tab of this party.

None.

5658 Get or Put operations via the Public API may not be performed for parties ratings with a Rating Type of 'N/A'.

None.




Number

5678 Some ratings are not shown when requesting ratings that were added using methods other than the public API. The message may return 'WithErrors' and some of the ratings returned may contain the following message:

Party X: rating mapping not found (type[X], subtype[X], group[X], agency[X]).

Party X: rating status mapping not found (agency[X], status[X]).

Party loaded from identifier X has an invalid mapping - lookup is not supported.

None.

5829 Some issuer identifiers migrated to parties may incorrectly match against an existing party, or in some cases, create a duplicate party.

None.

5862 Some specific commodities (e.g. Zinc, Nickel, and Gold), when associated with an instrument as a currency, may not be get/or put via the Public API because they are not defined by an ISO code.

None.

5930 When the Matching Configuration is too broad, a large number of instruments may be flagged as potential matches. As a consequence, the Matching Results page may display an OutofMemory exception.

Narrow the Matching criteria in the Matching Rules configuration.

5937 When DSS Counterparties data is loaded, a warning that includes the text "Cannot insert duplicate key in object 'dbo.address'" may sometimes appear when data for an existing address is (re)downloaded.

None.

5940 While performing a PUT operation, the Public API for Parties may insert an invalid Country cross reference

None.

5959 Get or Put operations via the Public API may not be performed for parties with an Entity Type or Entity Subtype of 'N/A'.

None.

5960 API Client – Generic Message > [Parties] – Put –Errors occur when creating Party when putting a new address: It was not possible to add the state to the repository State / Region X is not valid.

None.





Number

5965 When the third instance of the ASH service (ASH3) starts, an error about failing to load the configuration may be logged in spite of the service starting correctly.

None. Ignore the error if the service started.

5968 Excel Sample Client: WSDL for REPAPI Excel Data Service needs to be updated.

None.

5979 When using the Public API to perform a PUT operation for Cross References, the function may mis-identify the primary Source ID. This could cause a re-add of an existing Identifier or to not add a new Identifier

None.

© 2008 - 2011 Thomson Reuters.

All rights reserved. Republication or redistribution of Thomson Reuters content, including by framing or similar means, is prohibited without the prior written consent of Thomson Reuters. 'Thomson Reuters' and the Thomson Reuters logo are registered trademarks and trademarks of Thomson Reuters and its affiliated companies.

Thomson Reuters uses your data in accordance with Thomson Reuters privacy policy in the privacy footer at www.thomsonreuters.com. Reuters Limited is primarily responsible for managing your data. As Reuters is a global company your data will be transferred and available internationally, including in countries which do not have privacy laws but Reuters seeks to comply with its privacy policy. If you wish to see or correct data held on you or no longer wish to receive information about developments in Reuters Group products and services, such as free trials or events or you wish to change your preferred method of receiving a communication, please email [email protected] writing “Personal Details” in the subject title.

FOR MORE INFORMATION:

SEND US A SALES ENQUIRY AT

www.about.reuters.com/productinfo/salesenquiry

READ MORE ABOUT OUR PRODUCTS AT

www.about.reuters.com/productinfo

FIND OUT HOW TO CONTACT YOUR LOCAL OFFICE

www.thomsonreuters.com/about/contact_us

TREP221RN.110 Date of issue: 14 January 2011

Thomson Reuters Enterprise Platform for Data Management · The Thomson Reuters Enterprise Platform...

Documents

Transcript of Thomson Reuters Enterprise Platform for Data Management · The Thomson Reuters Enterprise Platform...