2011 06 evolution of the ims database_nyc_toronto_ug

655 views
525 views

Published on

Marilene Roder's presentation on the evolution of the IMS DB, Toronto IMS RUG meeting on June 30, 2011

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
655
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

2011 06 evolution of the ims database_nyc_toronto_ug

  1. 1. Marilene Roder – Software Engineermarilene@us.ibm.com Evolution of the IMS Database From the Moon to the Cloud © 2011 IBM Corporation
  2. 2. IMS Database Progress JDBC Access Distributed Access 2011+ Web Services > 2500 Transactions Per Second ~28000 Transactions Concurrent Per Second Image Copy APPC/IMS Remote Site > 1000 Transactions Per Second Multiple Systems Coupling (MSC) Recovery ... Java Data Base Dependent Parallel Concurrent Update Regions Systems From Multiple N-Way User/ 2-way Data Data Sharing System Exploit MP Sharing Batch Architecture Two DBMS Phase 1968 Commit Deadlock Detection © 2011 IBM Corporation
  3. 3. Agenda IMS Databases: overview Database Quiesce (IMS v11) Open Database (IMS v11) XML DB (IMS v9) and XQuery (IMS v10) Integration with other Tools © 2011 IBM Corporation
  4. 4. IMS/DB is a Database Management System A Database Management System – is a collection of programs for storing, organizing, selecting, modifying, and extracting data from a database. IMS DB is organized hierarchically – To optimize storage and retrieval – To ensure integrity and recovery – Segments are implicitly joined COURSE C 1 CLASS A L 11 INSTRUCT STUDENT B C D I 11 S 11 12 12 13 13 14 15 16 17 © 2011 IBM Corporation
  5. 5. IMS Database Access Methods Sequential Access Indexed Sequential Access HSAM HISAM SHSAM SHISAM GSAM Direct Access Indexed Direct Access HDAM PHDAM HIDAM DEDB PHIDAM MSDB © 2011 IBM Corporation
  6. 6. HALDB - What Is It? Large Databases – Databases are partitioned • Up to 1001 partitions per database • Partitions have up to 10 data set groups • Partition definition separated from database structure definition High Availability Databases – Partition Independence • Allocation, authorization, reorganization and recovery by partition – Self-Healing pointers • Reorganization of partition does not require changes to indexes or logically related databases which point to the partition Partitioned Database Data Sets – PSINDEX • 1 data set - secondary index data set – PHDAM • 2 minimum/11 maximum - 1 for data, 1 for indirect list data set – PHIDAM • 3 minimum/ 12 maximum - 1 for data, 1 for indirect data set, 1 for primary index data set © 2011 IBM Corporation
  7. 7. IMS HALDB Highlights Database types – PHDAM - partitioned HDAM – PHIDAM - partitioned HIDAM • Index is also partitioned – PSINDEX - partitioned secondary index Hierarchic structure is maintained – A database record resides in one partition Partition selection – By key range or by user exit routine ... © 2011 IBM Corporation
  8. 8. IMS HALDB Benefits Usability Greater database capacity – "Unlimited" capacity – Partitions may be modified as requirements change Increased database availability Availability – Shortened reorganization process – Option of Online Reorg (IMS V9+) – Batch window may be shortened with concurrent processing Improved performance Performance – Concurrent processing against partitions Application program changes are not required Compatibility © 2011 IBM Corporation
  9. 9. Customer Examples – German Bank France – 600 GB total capacity of all – Avant 01/2004 en France databeses, therefrom •AGF, Euroinformation, Natixis, – 512 GB for all HALDBs Renault, Pole Emploi •Largest HALDB: 340 GB – Après 2004 •GCA, … German Customer – 17 HALDB UK Insurance – Largest HALDB: 630 GB with 90 – Largest HALDB: 140GB partitions and 2 secindex with 55 partitionen … © 2011 IBM Corporation
  10. 10. IMS HALDB Information Redbook: – The Complete IMS HALDB Guide, All You Need to Know to Manage HALDBs • SG24-6945 – June 2003 • http://www.redbooks.ibm.com/abstracts/sg246945.html?Open Presentations and articles on the Web – IMS High Availability Large Database (HALDB) • http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS185 – Migrating to IMS HALDB – Refreshed 2009 • http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS693 – Application Design and Programming with HALDB • http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/PRS490 – Using GENJCL.USER to Allocate IMS HALDB Data Sets • http://www-1.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TD100491 © 2011 IBM Corporation
  11. 11. Online HALDB ReorganizationIntegrated OnLine Reorganization of HALDBs ƒ HALDB OLR provides 100% availability of the largest databases in the world! ƒ OLR provides non-disruptive reorganization of HALDB PHDAM and PHIDAM partitions Concurrent IMS updates are allowed while OLR is active ƒ Planned data outage not required © 2011 IBM Corporation
  12. 12. Relationship between Input and Output Datasets © 2011 IBM Corporation
  13. 13. Agenda IMS Databases: overview Database Quiesce (IMS v11) Open Database (IMS v11) XML DB (IMS v9) and XQuery (IMS v10) Integration with other Tools © 2011 IBM Corporation
  14. 14. Database Quiesce Improved Improved Reduced Usability Availability Complexity Offers the ability to stop access to a Database, HALDB Partition, DEDB or Area, or Datagroup, allowing a single coordinated recovery point to be established – Without taking the resource offline! No /DBR is required • Type-2 UPDATE DB|AREA|DATAGRP command is used to start and stop quiesce – The recovery point will be coordinated across the IMSplex to create one common recovery point – Allows an image copy to be taken while the database or area is online Reduces the complexity in establishing a recovery point for a database © 2011 IBM Corporation
  15. 15. Database Quiesce… Improved Improved Reduced Usability Availability Complexity Creating a recovery point without Database Quiesce… – Issue /DBR on each IMS to establish a recovery point •Each IMS will record a DEALLOC time in the RECON •Database resource is closed and data sets are deallocated – Check to make sure the database or area was successfully taken offline on each IMS – Issue /STA on each IMS to allow database to be used •OPEN option on /STA command is required to allocate and open the data sets Otherwise first access will open the data sets IMS RECON IMS IMS © 2011 IBM Corporation
  16. 16. Database Quiesce… Improved Improved Reduced Usability Availability Complexity Creating a recovery point with Database Quiesce… – Issue UPDATE DB|AREA|DATAGRP START(QUIESCE) command •Command is processed by one IMS (command master) in the IMSplex Databases and data sets are not closed and deallocated Command waits for active use of the resource to reach a commit point and then quiesces the resource Coordinated across the IMSplex, OLDS are switched on each IMS by default RECON updated by one IMS with common DEALLOC timestamp on behalf of all the IMS systems » New allocations for FP areas done on local IMS IMS » For FF databases, a new ALLOC is created at first database update after releasing the quiesce IMS Command master communicates with IMS systems toRECON resource available again make IMS © 2011 IBM Corporation
  17. 17. Agenda IMS Databases: overview Database Quiesce (IMS v11) Open Database (IMS v11) XML DB (IMS v9) and XQuery (IMS v10) Integration with other Tools © 2011 IBM Corporation
  18. 18. IMS Open Database Innovative Improved Open Usability Standards Solution Statement – Open new avenues to IMS • Offer scalable, distributed, and high-speed local access to IMS database resources Value – Business growth • Allow more flexibility in accessing IMS data to meet growth challenges – Market positioning • Allow IMS databases to be processed as a standards-based data server Key differentiators – Standards-based approach (Java Connector Architecture, JDBC, SQL, DRDA) – Solution packaged with IMS Enables new application design frameworks and patterns – JCA 1.5 (Java EE) – JDBC © 2011 IBM Corporation
  19. 19. Integrating IMS DB in a composite application 1. Channel: Web User Interface 2. Process Services 4. Operational Data Store: IMS DB 3. Master Data Management Services ACCOUNT ACCTID ACCTNAME BALANCE CONTRACTID TERMS PRODID © 2011 IBM Corporation
  20. 20. IMS Open Database Innovative Improved Open Usability Standards J2EE JDBC Universal drivers Direct Mainframe DLI IMS IMS IMS IMS J2EE TCP/IP JDBC Universal drivers DLI TCP/IP Mainframe Distributed (e.g.; LUW) IMS IMS IMS IMS z/OS © 2011 IBM Corporation
  21. 21. Solution highlights – connectivity Innovative Improved Open Usability Standards Type 4 drivers – Universal drivers support type 4 connectivity to IMS databases from TCP/IP enabled platforms and runtimes • WebSphere Application Server • Windows • zLinux • z/OS • Standalone Java SE Type 2 drivers – Universal drivers will support type 2 connectivity to IMS databases from z/OS runtimes • WebSphere Application Server for z/OS • IMS Java dependent regions • CICS – All environments zAAP eligible © 2011 IBM Corporation
  22. 22. Solution highlights – Universal drivers Innovative Improved Open Usability Standards Three Universal drivers –Universal DB resource adapter • J2EE deployment • Standard Java SE deployment –Universal JDBC driver • Standard Java SE deployment –Universal DLI driver • Standard Java SE deployment © 2011 IBM Corporation
  23. 23. Solution highlights – J2EE deployment Innovative Improved Open Usability Standards Universal DB resource adapter –JCA 1.5 • XA transaction support Manage multiple datasource connections in a single UOW • Local transaction support Manage multiple datasource connections each in their own UOW • Connection pooling Pool released connections for future use • Connection sharing • Multiple programming models available JDBC (Universal JDBC driver incorporated) CCI with SQL interactions CCI with DLI interactions © 2011 IBM Corporation
  24. 24. Solution highlights – JDBC Innovative Improved Open Usability Standards Universal JDBC driver – Significant enhancements to classic JDBC offered in IMS 9 and IMS 10 • Standardized SQL support • XA transaction support (type 4) • Local transaction support (type 4) • Concurrency control Control release of distributed locks • Updatable result set support • Batching support Fetch multiple rows in a single network call • JDBC metadata discovery support Standard SQL and metadata discovery enables significant integration opportunities for IMS © 2011 IBM Corporation
  25. 25. Solution highlights – DLI Innovative Improved Open Usability Standards Universal DLI driver –Java implementation of DL/I API –Complete DL/I support for database access –All IMS command codes supported –Can mix usage of JDBC and DLI drivers in the same application • SQL cannot always express what DLI offers © 2011 IBM Corporation
  26. 26. Solution highlights – Java dependent region deployment Java dependent region resource adapter – Java framework for applications operating in an IMS container • Message queue processing • Program switching Deferred and immediate • Transaction demarcation • GSAM support • Additional IMS call support necessary for IMS transactions INQY INIT LOG Etc – Shipped with type 2 Universal drivers © 2011 IBM Corporation
  27. 27. Open Database Environment Innovative Improved Open Usability Standards z/OS LPAR A Evolution ODBM IMS Distributed S O PC C D CTL IMS DB I B A WebSphere S Universal DB T LPAR B Resource C O Adapter P A J C XCF I P A 1.5 P TCP/IP LPAR C IMS Connect T C S P C I I P © 2011 IBM Corporation
  28. 28. Open Database Environment Innovative Improved Open Usability Standards z/OS LPAR A IMS IMS 11 Solutions z/OS WAS Universal Traditional ODBA DB Resource O ODBM Distributed T Adapter D S B C PC S O PC CTL C J C D IMS DB P C A I I B I A A WAS on Any Platform P 1.5JEE Universal XCF S DB T LPAR B IMS Resource Traditional ODBA C O Adapter IMS Universal Drivers P A J JDBC ODBM PC P C I S O CTL IMS DB A P C D 1.5 I B DLI A IMS Universal Drivers LPAR CNon- JDBC IMSJEE TCP/IP IMS Connect ODBM S O T PC DLI S C D CTL IMS DB C C I B P TCP/IP I A I P RYO DRDA Appl. © 2011 IBM Corporation
  29. 29. IMS Open Database – Performance Considerations Scenario Description IBM SVL Lab NotesA) SysZ Java DLI Same call, 7892 TPS Both COBOL & Java Same platform, meets business vs. vs. Different language requirements.SysZ COBOL DLI 9980 TPSB) DIST JAVA DLI Same call, 4000 TPS System Z was vs. Same language, approximately 2 times vs. Different platform faster SysZ JAVA DLI 7892 TPSC) DIST JAVA DLI Same language, 4000 TPS The JDBC and SQL vs. Same platform, layer only adds vs. Different interface approximately 5%DIST JAVA SQL 3800 TPS overhead © 2011 IBM Corporation
  30. 30. Agenda IMS Databases: overview Database Quiesce (IMS v11) Open Database (IMS v11) XML DB (IMS v9) and XQuery (IMS v10) Integration with other Tools © 2011 IBM Corporation
  31. 31. IMS XML Database View/map native IMS hierarchical data as XML documents Allows the retrieval and storage of IMS Records as XML documents with no change to existing IMS databases XML Evolution over XML Revolution – Run XML transactions concurrently with traditional workload XML Schema IMS DBD book PCB: BIB21 @year seq BOOK XML xs:date title choice publisher price YEAR TITLE PUBLISH PRICE IMSDocuments 0:oo 0:oo xs:string author editor xs:string xs:decimal AUTH LAST FIRST EDIT LAST FIRST AFFIL Data seq seq last first last first affiliation xs:string xs:string xs:string xs:string xs:string © 2011 IBM Corporation
  32. 32. IMS XML-DB Metadata “Natural” mapping between hierarchic XML data and hierarchic IMS database definitions. XML Schema <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ims="http://www.ibm.com/ims" xmlns="http://www.ibm.com/ims/PSBName/PCBName" targetNamespace="http://www.ibm.com/ims/PSBName/PCBName" elementFormDefault="qualified"> <xsd:annotation> PSB <xsd:appinfo> <ims:DLI mode="store" PSB="AUTPSB11" PCB="AUTOLPCB" dsg="DATASETG" meanLength="1000" numDocs="100"/> mapping </xsd:appinfo> </xsd:annotation> <xsd:element name=“A”> <xsd:complexType> DBD <xsd:sequence> <xsd:element name=“field1" type="xsd:int"/> <xsd:element name=“field2"> XML view of IMS <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:maxLength value="30"/> data </xsd:restriction> … XML document definition IMS DB definition © 2011 IBM Corporation
  33. 33. Agenda IMS Databases: overview Database Quiesce (IMS v11) Open Database (IMS v11) XML DB (IMS v9) Integration © 2011 IBM Corporation
  34. 34. Integration IBM Mashup Center Offered by the – Web 2.0, Data as a service IMS Explorer Data Source Explorer – IMS connectivity via Generic JDBC – Database exploration – View/Edit data Data Project Explorer – SQL scripting • Graphical • Content assist Cognos – Operational business intelligence and reporting – IMS Connectivity via Generic JDBC © 2011 IBM Corporation
  35. 35. IBM Mashup Center - Data as a service Web 2.0 support for IMS data – Develop an IMS RESTful service/feed • Generate meta files from IMS DB • IMS Web 2.0 Editor in InfoSphere MashupHub © 2011 IBM Corporation
  36. 36. Web 2.0 support for IMS Data (Mashup Center) Enterprise Database Plugin – Allows users to create feeds from any Database that supports a JDBC driver Supports the following databases: – DB2 – Microsoft SQL – Derby – MySQL – IDS – Oracle – IMS © 2011 IBM Corporation
  37. 37. Web 2.0 support for IMS Data (Mashup Center) Features: – Support both managed and unmanaged connections – Can store connection profile information for reuse © 2011 IBM Corporation
  38. 38. Web 2.0 support for IMS Data (Mashup Center) Supports generating SQL queries via a GUI interface © 2011 IBM Corporation
  39. 39. Operational Business Intelligence and reporting Type of BI that helps drive and optimize business operations on a daily basis – Extends the use of BI to a much wider user audience – Enables more timely business decisions; in relation to real time or right-time BI Processing – Allows business users to report on, analyze and optimize business operations – Reduces the time between the discovery of problems or opportunities and taking action on them Main pillars of BI are querying, reporting, OLAP, and business analytics © 2011 IBM Corporation
  40. 40. The T hree L evels of B usine ss Inte lligenc e © Claudia Imhoff © 2011 IBM Corporation
  41. 41. Reporting and OLAP ■ Enterprise Reporting • Supports multiple report types: Production, Managed, Ad-hoc, Financial, etc • Operates from a single metadata layer • Can be personalized and targeted • Can be distributed via email, portal, MS-Office, search application and mobile device • Can assist in the management and optimization of daily business operations • Capable of reporting on real-time data • Presents complex data in a business way so it is easy to understand ■ Analysis • Enables the guided exploration of information that pertains to all dimensions of your business • Moves from summary level to detail levels of information effortlessly • Analyzes and reports against online analytical processing (OLAP) and dimensionally aware relational sources • Gets to the “why” behind an event or action to improve business performance. • Identifies potential problems and recognizes business trends © 2011 IBM Corporation
  42. 42. Cognos and IMS Ability to leverage IMS assets within the Cognos product family can be a tremendous competitive advantage for any organization IMS 11 Open Database can enable this integration – Removes inhibitors • Prior to IMS 11, no built-in ad hoc query capabilities in IMS • Standard tools often did not support hierarchical data; left to write own interfaces and reports or had to purchase bridging tools • Must be skilled in IMS to integrate with IMS and write reports © 2011 IBM Corporation
  43. 43. IMS Value IMS “Value Proposition” 40+ years of Continuous Core Systems Improvement IMS “Value Proposition” 40+ years of Continuous Core Systems Improvement IMS is Efficient: 22K trans/sec on a single eight Most efficient run-time, maintains application way z9. Remarkable performance that translates investment protectionEfficiency to the most cost efficient run-time environment. Fully integrated into today’s AD toolsets Reusing IMS transactions and data saves money. Fully integrates with WebSphere Application Server/ ESB / Process Server IMS enables Growth: IMS SOA provides Open, standard interfaces allowing ‘any-to-any’ Fully supports SOA connectivity and access for new applications. Improved efficiency and reduced skill IMS supports Growth: with IMS scalability you Growth can just keep on growing. Customers have requirements for systems and development staff routinely handled peaks of 100 million transactions in a day. Flexibility: JAVA, COBOL, C, PL/I, XML, Web 2.0… IMS is Resilient: Customers report going Continuous improvement to Rock solid thousands of days without an unplanned outage. availabilityResilience One bank reports availability of 99.998% over 10 years, 1.5 hours for planned outages. Continuous improvement to operations and serviceability tools IMS and z/OS are secure Fully supported by IMS & Tivoli tools © 2011 IBM Corporation
  44. 44. The Message IMS continues to be a premier server with architected standard interfaces – New products and tools from a variety of vendors provide access to IMS transactions and data SOA is revolutionizing the way businesses are being designed and run. For it to make sense: – All assets must be easily accessible in a standard way – All data must be represented and manipulated in a standard way Our goal is to leverage IMS Database Manager as an integral part of the enterprise in the evolving business world through – Addition of support for complimentary standards surrounding IMS data connectivity, data representation, and application development And to allow you to realize the promises of building a Service Oriented Architecture: – Simplify the business environment – Respond to market changes more quickly and cheaply © 2011 IBM Corporation
  45. 45. © 2011 IBM Corporation

×