1. 1 GSE DB2 Working Group meeting 27 March 2014 DB2 Connectivity at Euroclear

2. 2 Contents About Euroclear Infrastructure Workload As it was As it is The current challenges The future challenges Support Demanded Tools

3. About Euroclear Active in the financial transaction processing, Euroclear is the world’s largest provider of domestic and cross-border settlement & related services for bonds, equity and funds. Our clients are banks and financial institutions, brokers, dealers from over 80 countries. 3

4. Euroclear facts & figures 4 Number of employees: 3600 worldwide ► 2,500 in Belgium, and approximately 900 in IT Nationalities: >80 Average age: 37 Number of offices worldwide: 12 Countries in which we have clients: 80 Headquarters: Belgium ► Main office in Brussels, a 2nd office in Braine L’Alleud

5. Our offices and hubs worldwide 5

6. Who are we?

7. The Data Center Policy 7 First company in Europe running a three data centre infrastructure, spread over two countries and designed to be fully redundant and synchronized for critical production applications. We ensure integrity and consistency between mainframe and open systems in a 24/7 environment. 2 Active Data Center: ►Monthly SWAP ►Fully synchronized – At disk level ►Active-Passive configuration (mainly) 1 Data Center for Regional disaster recover

8. Infrastructure 8 Euroclear Infrastructures: 3 Business environments 36 DB2 subsystems running No data sharing Data Warehouse in EB Horizontal increase Vertical increase Joining of other DC

9. Workload 9 It depends… Mainly static SQL on the core subsystems Mainly dynamic SQL on the data warehouse Several tools generating the workload: Business Application Reporting tools Supported Tactical tools Unsupported Tactical tools Focusing on the Data warehouse Static SQL: < 5 % Online queries ISPF: 60 % (decreasing) Distributed: 40 % (increasing)

10. The need of the connectivity 10 There is a increasing need of sharing data across multiple platforms. Mutation from batch reporting to online reporting Improve user interaction with the data in “more appealing” environments The challenges: Keeping the core business on DB2 and sharing the data on different Platform Manage the jungle of queries/tools connecting from everywhere The demand of connectivity: The demand of connectivity is directed only toward the datawarehouse No users on the core back end

11. As it was 11 You can connect from everywhere. Advantages: Freedom Drawbacks: Contention for mistakes of users Hard to trace DB2 Unsupported Tools Tactical tools Applicative Tools UsersSASBI Tools

12. As it is 12 Access through a gateway Advantages: Traceable at gateway level Simpler interventions Possible to cut part of the workload Drawbacks: Additional hardware / software to maintain Bigger impact of the intervention DB2SAS SpawnerSAS Online DB2 Connect Gateway Citrix (ODBC)UsersTactical Tools Local DB2 Connect Gateway ODBCApplicationJDBCDocumentum.NETApplication Dedicated drivers Datastage EOC Framework

13. As it is 13 The rules to connect to DB2: All the users on Citrix connect through a gateway All the applications connect through a gateway installed locally SAS in passing through the SAS Spawner / SAS Access DB2 ►Evaluating connectivity through ODBC as a Citrix User – Direct ODBC connectivity increase the performance (testing) The gateways have dedicated network name and functional id ►Re-hosting of the old gateway network name on the new machine All the gateways are in cluster configuration Segregation of the connections: ►Split between Production and Test domain ►Link between Development and Production

14. The current challenges 14 Capacity: Limit the consumption of the users ►SYSIBM.DSNRLST01 – By default 17 CPU sec/SQL ►Many exceptions Mitigate the “Killing SQL” ►Detect the poorly written SQL – SQL Statement with 20 “with tables” Statements ►Reject SQL / Tool that are consuming too much ►Splitting the queries in procedures ►Monitor periodically the top queries from DISTSERV Expansion: Several new installation of the DB2 Connect Gateway ►Opening the doors to Mainframe ►Mentality shift: DB2 is easy to query as any other DBMS

15. The current challenges 15 Support: Welcome new requests ►Presentation about “DB2 & Mainframe : Opening the black box” ►Presentation about new features: – Temporal Tables, XML, Sequences, etc… ►Support for user creation and rights granting – Not easy for “distributed people” understand RACF ►Installation and setup of DB2 Connect Gateway

16. The future challenges 16 Governance: Migrate from thousand of small tools to a global tool ►Centralize / Organize the demand of data on a single Product/BI tool Re-acquire the knowledge inside the SQL ►Very hard to understand what a 600 lines of select is doing and why Exploit even further the XML Generation capabilities Adopt one infrastructure for end 2 end replication ►CCD Table ►Applicative Replication ►Table Replication

17. 17 For internal use Further questions? For questions ► Michelazzo.Mattia@euroclear.com

18. 18 For internal use