Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

IMS DB Futures - IMS UG September 2012 Omaha


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

IMS DB Futures - IMS UG September 2012 Omaha

  1. 1. Kyle CharletSTSM, IMS SOA and DB Update and Futures © 2012 IBM Corporation
  2. 2. Please note IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.2 © 2012 IBM Corporation
  3. 3. AgendaIMS modernization overview IMS database solutions Portfolio integration Modeling and query generation DataPower and IMS connectivity3 © 2012 IBM Corporation
  4. 4. IMS Modernization Solutions IMS access anywhere IMS TM and DB Resource Standards-based data server and TM Adapters Open systems access Web services Web 2.0 (Mashup Center) WebSphere TM/DB access Universal JDBC Java API driver T IMS C P Java Universal DLI / C API driver Catalog I TM Access DB access P RYO z/OS DataPower IMS SOAP Gateway TM access4 © 2012 IBM Corporation
  5. 5. IMS Open Database Solution statement Extend the reach of IMS data – 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) JDBC5 © 2012 IBM Corporation
  6. 6. IMS Open Database JavaEE JDBC Universal drivers DLI Direct IMS JavaEE Universal DRDA over TCP/IP z/OS JDBC DRDA over TCP/IP drivers DLI DRDA over TCP/IP Open Systems (e.g.; LUW) IMS z/OS6 © 2012 IBM Corporation
  7. 7. Solution highlights – JEE deploymentUniversal 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 interactions7 © 2012 IBM Corporation
  8. 8. Solution highlights – JDBCUniversal 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 supportStandard SQL and metadata discovery enables significant integration opportunities for IMS8 © 2012 IBM Corporation
  9. 9. Solution highlights – DLIUniversal 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 offers9 © 2012 IBM Corporation
  10. 10. Open Database and the Universal driversDeep synergy with the IMS catalog – Direct access to IMS metadata in the catalog – Virtual and cloud deployment capabilities • No longer file-system dependent for metadata – Industry-leading data type support • Complex and flexible – Mapping supportDeep synergy with Java z/OS and z196 – Significant performance improvements – Continued partnership with Java z/OS labContinued SQL standardization and support – Including similar connection parameters as DB2 for commonality across IBM drivers – More to comeContinued integration across the IBM portfolio10 © 2012 IBM Corporation
  11. 11. Data typesData types have multiple metadata elements – Application data type • Universal drivers use application data type to present data to clients – Physical data type • Universal drivers use physical data type to marshal/unmarshal data to and from the database – Example • Application data type is DECIMAL(10,2) [decimal with precision 10 and scale 2] • Physical data type is a signed packed decimal (AD community doesn’t need to know this)New data type support – Structs (nested n levels with no constraint on element data types) • Accessed via SQL and DLI – Arrays (nested n levels with no constraint on element data types) • Accessed via SQL and DLI – User-defined • Name of UDT can be defined to the catalog and intended to be used at runtime by Universal drivers to marshal/unmarshal data • Can be part of a Struct or Array element11 © 2012 IBM Corporation
  12. 12. MapsMapping support – A Map is metadata that describes how a field (or set of fields) are mapped for a particular segment instance – Metadata captures the various cases and for each case defines the set of fields to be used for that case – Maps can be defined to the catalog – Example •Insurance segment mapped multiple ways depending on value of a ‘Policy Type’ field Policy Type Property Type Rooms Value Address Make Model Year Value Color M - - - - Ford Escort 1989 2K Red 555 Disk Drive H Single Family 5 500K - - - - - Way, 9514112 © 2012 IBM Corporation
  13. 13. Additional enhancements SQL – FETCH FIRST <n> ROWS ONLY – INNER JOIN <table2> ON <table1.col1> = <table2.col2> Connection properties – currentSchema – maxRows – fetchSize – Tracing • traceFile, traceFileAppend, traceDirectory, traceLevel Variable length segment support – VL segments contain a two byte length (LL) field that will identify the size of the segment instance – Universal Drivers are now sensitive to the LL field of a VL segment and will manage the IO area of the segment instance on all CRUD calls13 © 2012 IBM Corporation
  14. 14. IMS Open Database environment z/OS LPAR A IMS Open Systems ODBM S O PC C D CTL IMS DB WebSphere I B Universal A T S DB Resource C O Adapter A P LPAR B J C I P A P 1.5 XCF DRDA LPAR C IMS Connect T C S P C I I P14 © 2012 IBM Corporation
  15. 15. IMS Open Database environment z/OS LPAR A IMS Universal Traditional ODBA WAS z/OS DB Open Systems Resource adapter O ODBM T D S PC S O PC CTL C J B C C D IMS DB WebSphere P C A I I B I Universal A A P JEE S DB Resource T 1.5 XCF adapter C O J P LPAR B IMS A Traditional ODBA P C I IMS Universal drivers A P JDBC ODBM PC 1.5 S O CTL IMS DB C D I B DLI IMS Universal drivers A JDBC LPAR CJava SE IMS IMS Connect ODBM DLI O S PC T S C D CTL IMS DB DRDA C C I B P I I A RYO DRDA Appl. P 15 © 2012 IBM Corporation
  16. 16. IMS 12 catalog Trusted IMS metadata information Comprehensive view of IMS database metadata (including application metadata) managed by IMS with standard access patterns (JDBC/SQL) Offers metadata discovery and exchange via IMS Open Database and the IMS Explorer for Application Development Scalable Open Database solution – large scale deployment into virtualized production and test environments Enables broad IMS integration into the IBM and non-IBM portfolio of tools (Optim Development Studio, Rational Asset Analyzer, InfoSphere Data Architect, etc) PSB PSBGEN source PSBLIB ACBLIB IMS ACBGEN IMS Explorer DBD DBDGEN source DBDLIB Catalog16 © 2012 IBM Corporation
  17. 17. IMS catalog – intended support PSB PSBLIB source DDL IMS Explorer Catalog ACBLIB DBD DBDLIB source IMS • IMS DB changes start with catalog • IMS loads resource information from catalog • ACBLIB/PSBLIB/DBDLIB updates will be the by-product of catalog updates • Tools that use these libraries can continue to operate, but should migrate to catalog • PSB and DBD source can still be optionally generated from PSBLIB and DBDLIB17 © 2012 IBM Corporation
  18. 18. Dynamic database - Data Definition Language SQL incorporates DDL to modify the schema of a database Authoring DDL is straight-forward with sophisticated tooling support in the industry SQL/DDL can be used to update/add metadata in the catalog without the need of a GEN – Directly update the catalog IMS can be notified of such an update and load the new definitions It is our intention to offer this type of dynamic definition for IMS18 © 2012 IBM Corporation
  19. 19. IMS ModernizationIMS Explorer for Development IMS Explorer for Administration (Eclipse) (Web Browser) Developers Administrators ISPF19 IMS © 2012 IBM Corporation
  20. 20. IMS Explorer for Development20 © 2012 IBM Corporation
  21. 21. IMS Explorer for Development21 © 2012 IBM Corporation
  22. 22. IMS Explorer For Development22 © 2012 IBM Corporation
  23. 23. IMS Explorer For Development23 © 2012 IBM Corporation
  24. 24. IBM Portfolio Integration 2012-2013 Database Modeling & Creation Governance Access Analytics IMS Explorer InfoSphere Data Optim Designer Data Studio Cognos 10 BI Architect• Catalog integration • Logical & physical • Data privacy • SQL authoring • Operational BI modeling • Extending value of• zExplorer • Data management • pureQuery IMS data integration • Resource discovery • Query explain• Advanced data type • Model sharing support•Physical modeling &resource discovery•Database resourcecreation24 © 2012 IBM Corporation
  25. 25. Premier System z web service enablement through DataPower SOAappliancesIBM cross-brand initiative Deep synergy between DataPower, System z, Rational and Common Transformation tooling to support DataPower as the premier System z gateway for IMS, CICS and DB2 Intended support for IMS DB access Intended support for top-down service approach for inbound and outbound IMS transactional requests Native z transports Network-level HA and Protocol transformation distribution DataPower Processing Flow IMS RACF-centric XI50z CICS security DB2 WS Monitoring Transaction distribution XI5225 © 2012 IBM Corporation
  26. 26. Java dependent region deploymentJava dependent region resource adapter Allows new IMS transactions (JMP, JBP) to be written in Java and managed by the IMS transaction manager Complete 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 drivers26 © 2012 IBM Corporation
  27. 27. .NET access to IMS DB – intended support Solution – Ability to directly access IMS Databases from .NET applications using SQL Value – Simplifies application development for .NET environments – Lower cost and complexity • No need for intermediate steps/tools to access IMS databases • SQL access • Transparent to application – Standards Based • Enables tools to work without any additional work for IMS27 © 2012 IBM Corporation
  28. 28. Native SQL – intended support Solution – Enable SQL as API for COBOL and PL/I programs to access IMS database • Support for COBOL and PL/I in addition to the current Java-based IMS applications – Provide native SQL processing in IMS • Still perform DLI call processing underneath Value – Simplify application programming to allow SQL programmers to access IMS Database in a similar method to what is used for relational databases – Expand IMS database usage to a wider group of application and database developers • Take advantage of SQL skills without requiring in-depth IMS database knowledge28 © 2012 IBM Corporation
  29. 29. Alter for IMS HALDB – intended support Solution – Allows IMS HALDB structure changes without unload/reload of the database • Adding a field to a segment • Increasing a field length • What about adding a new segment type? – Built on HALDB Online Reorganization Value – Improves IMS HALDB availability by providing structure changes without taking the database offline – Provides flexibility in rolling database changes into the system A A B C B C29 © 2012 IBM Corporation
  30. 30. Alter for IMS Data Entry Database – intended support Solution –Allows DEDB Area changes without unload/reload of the area • Dynamic change for UOW and ROOT parameters of an existing Area • Split/Add Areas –Provides new DEDB dynamic change utility • Performs changes while the Area is online Value –Improves DEDB Area availability by providing definitional changes without taking the Area offline –Provides flexibility in rolling Area changes into the system30 © 2012 IBM Corporation
  31. 31. Database versioning – intended support Solution – Allows programs to use different versions of the same database • Provide the support for multiple views of the physical data • Allows old applications to remain unchanged when the physical structure of the database changes • Make database structure changes and only compile programs referencing changed fields/segments • Requires the catalog • Applies to HALDB, Full Function DB, Fast Path DEDB Value – Provides greater flexibility in rolling out new versions of programs and databases – Allows new programs to get out faster without waiting for all programs to be updated to the new database structure31 © 2012 IBM Corporation
  32. 32. Database versioning – intended support CHAR(4) CHAR(8) BINARY(8) Base version A B C CHAR(4) CHAR(8) BINARY(8) BINARY(4) Version 1 A B C D Add field to end of segment CHAR(4) CHAR(8) BINARY(8) BINARY(8) Version 2 A B C D Increase size of field D32 © 2012 IBM Corporation
  33. 33. Enhanced query capabilities – intended support Allow predicate processing of every field in a segment –Catalog contains all segment information –Every segment position searchable –No longer require field to be defined to IMS in the DBD –SQL and DLI support • Catalog contains metadata for all fields (columns) in a segment (table) Extend GUR support (get unique record) to all database types –Retrieve an entire IMS database record in a single request • XML or binary output possible33 © 2012 IBM Corporation