Ims continued modernization - Columbus RUG September 2012


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Ims continued modernization - Columbus RUG September 2012

  1. 1. IMS User Group Meeting – Fall 2012IMS Continued ModernizationNancy Stein – IBM IMS ATS © 2012 IBM Corporation
  2. 2. More than 75% of the world’s100 Top 25 companies listed in the Fortune 100 entrust their business to IMS every second © 2012 IBM Corporation 1
  3. 3. IMS – an IBM Icon of Progress © 2012 IBM Corporation 2
  4. 4. IMS – from Apollo to XRF MFS 3270s Scheduling by Scheduling by intent on intent on segment type Multi-regionIMS architecture database360 FP Mixed Mode Fast Path AOI and CMD calls MSC DBRC Parallel DLI SMP VSAM GSAMIMS VS Secondary Index Appl. Chk/Restart Program VSAM Buffer Pools Isolation XRF VSCR DASD Logging Data Sharing DLI SAS IRLM 31 Dependent regions PROCOPT GON/GOTIMS VS ISC MSC VTAM © 2012 IBM Corporation 3
  5. 5. IMS – from DBCTL through the present day Shared Queues 999 Dependent PRPQ for Y2K Regions Support Parallel Sysplex OTMA APPC DBCTL ETOIMS ESA IMS Catalog 64-bit FP Buffer Open DB Management DB Quiesce DRD IMS-to-IMS TCPIP Support ACBLIC Dynamic HALDB OLR MSC Bandwidth Fast Path Secondary Index Allocation Common Service Integrated Global Status IMS Enterprise Suite Transaction Expiration HALDB Layer IMS Connect Management IMS Web 2.0 SolutionsIMS Global Online Change © 2012 IBM Corporation 4
  6. 6. Compatibility• Application compatibility – Programs written in 1969 still work – IMS does not require recompiles for new IMS releases• Database compatibility – Databases do not require upgrades for new IMS releases• IMS has allowed users to grow their applications in lieu of forcing major conversions © 2012 IBM Corporation 5
  7. 7. Adaptability• And yet IMS also keeps up with technological trends – Provides a TCP/IP socket server – IMS Connect • For access to IMS transactions and databases – Allows IMS applications to be either clients or servers – Delivers adapters that run in JEE, SOAP, etc. environments • Pluggable components that provide easy interfaces to IMS resources – Supports type-2 and type-4 universal drivers for access to IMS DB• Provides application programming interfaces – Unique to IMS • DL/I calls to access IMS resources: message queues and data • IMS applications can be written in: COBOL, PL/I, Assembler, C/C++, Pascal, ADA, REXX, Java – Portable – Java classes and JDBC © 2012 IBM Corporation 6
  8. 8. And …• That is why IMS continues to be current – Application programs that were written for IMS 5, 10, 15, 20, 40… years ago can continue to run today • Even when they are now invoked from the web – Or continue to be invoked from older 3270 devices or emulators – The same application, without change, can be accessed from any type of connection mechanism or network that can access IMS• The IMS architecture allows communication components and even database components to be exchanged or replaced – Without affecting the application in IMS © 2012 IBM Corporation 7
  9. 9. How does a 44-year old software product continue to thrive?• Revolutionary Architecture – Multiple regions “You build – Separate database definitions from applications sophisticated – Separate communication management from structures around applications IMS……when• Persistent Compatibility you lift the covers – An application program written in 1969 still runs on on those IMS IMS 12 – No application recompile or rebind is required after transactions, they migrating are incredibly – No database conversion required after migrating sophisticated in• Programming interface what they do…..” – Database definitions maintained in DBDs – Application views and access limitations maintained in PSBs – DLI calls used for both database access and input/output messaging• Adaptability Steve Mills, Senior VP and Group Executive Software & Systems, at IBM IMPACT 2012 Conference Keynote © 2012 IBM Corporation 8
  10. 10. 15 million gigabytes of production data managed by IMS $3.0 trillion ($US) per day transferred through IMS, by one customer 200+ million users served every day 375 million accounts…..for one customer 46,000 transactions per second…..on a single IMS system © 2012 IBM Corporation 9
  11. 11. IMS Evolution Strategy New IMS interfaces IMS interfaces IMS and models Installation SQL / JDBC JCL IMS and ISPF TM Operations IMS Tools SDSF and Rational JES DB User Mods Application Optim User Exits Developmen t DBDGEN Cognos PSBGEN Database InfoSphere ACBGEN Reporting OLC and J2EE DRD Analysis DLI pureQuery Reduce the need for special, in-depth IMS skills © 2012 IBM Corporation 10
  12. 12. IMS Evolution / Simplification• Deliver more intuitive UIs and interfaces to talk to IMS – Eclipse-based tooling for Application Development – IMS Explorer and IMS 12 – SQL support from Java with Open Database in IMS 11 – More operational consistency with z/OS, CICS, DB2, RDz, and Omegamon for IMS• Reduce planned outages and manual tuning – Dynamic Database Buffer Pools – IMS 12 – Database Quiesce – IMS 11 – Dynamic allocation of ACBLIB data sets – IMS 11 – Dynamic Resource Definition – IMS 10 – Online Reorganization – IMS 9 © 2012 IBM Corporation 11
  13. 13. Rapid IMS Application Development• Extending IMS Application Development to Business Analysts – Make decisions based on up-to-the-minute data• Business Rules – ILOG BRMS support – code generation• Mashups – IMS Web 2.0 Solutions for Mashup Center – Available in V10 for IMS TM feeds, IMS 11 for IMS Data feeds – Ability to easily integrate multiple RESTful services, widgets, data• COGNOS – Real time query of IMS data – Business analyst with no IMS skill can make decisions based on data supplied by IMS © 2012 IBM Corporation 12
  14. 14. IMS 11: Distributed Access to IMS Data• IMS Open Database enables access to IMS databases anywhere in the IMSplex, directly from z/OS and distributed Java clients !!! – Using industry standard Distributed Relational Database Architecture (DRDA) to communicate with IMS Connect – Universal DB Resource Adapter • JEE environments (e.g. WebSphere Appl. Server) - JCA 1.5 • SQL Calls – Universal JDBC Driver • Non-JEE and JEE environments • SQL Calls – Universal DLI Driver • Non-JEE and JEE environments • DL/I call concepts (SSA, command codes) – RYO (Roll Your Own) • Program sends DRDA commands directly to IMS Connect – IMS Connect becomes the gateway to IMS Transactions and IMS Data Makes Application development and Connectivity much simpler! © 2012 IBM Corporation 13
  15. 15. IMS JDBC Support • JDBC 3.0 • Standard SQL implementation for the SQL subset – Keys of parent segments are included in tables as foreign keys • Updatable results set • Local commit/rollback support • Metadata discovery API implementation – Uses metadata stored in the IMS Catalog – Enables JDBC tooling to work with IMS DBs as with DB2 DBs © 2012 IBM Corporation 14
  16. 16. IMS Open Database and DRDAIMS Connect and Open Database Manager work together as a DRDA server forIMS dataAllows distributed access to IMS Databases via TCP/IP using the IMS UniversalDatabase DriversEnables use of SQL database query language for access to IMS Databases DRDA z/OS IMS Application ServerIMS Universal DB Drivers Application DRDA IMS Connect DLI IMS Requestor DDM Calls DB’s TCP/IP ODBM IMS TCPIP SCI TCP/IP DRA DRDA or Client ODBA PORT IMS CAT © 2012 IBM Corporation 15
  17. 17. Open Database Manager - ODBM • z/OS address space – Common Service Layer component • Functions – Receives database connection requests from IMS Connect – Translates incoming database requests from DDM protocol to DL/I calls – Manages ODBA or DRA interface to IMS – Sends/receives byte string to/from IMS – Translates responses into DDM protocol for the client – Send results set back to client • Provides isolation of application containers from IMS – Abend of container during DL/I call does not cause IMS U0113 abend • Distributed Syncpoint (global transaction) requires RRS on z/OS • Use of RRS with ODBM is optional – If RRS=Y (default), ODBM uses ODBA interface – If RRS=N, ODBM uses DRA interface (like DBCTL interface) © 2012 IBM Corporation 16
  18. 18. IMS Open Database LPAR DRA CICS TCP/IP DRA CICS Java Appl. Appl. Traditional DRA IMS Java Appl. Appl. CCTL JEE Traditional ODBA CCTL ODBA SCI TCP/IP Java Appl. Appl. ODBMJEE DB ODBA or DRA SCI WAS for z/OS ODBA TCP/IP WAS z/OS or distributed Non-JEE (DB2 SP) CAT Java Appl. Java Appl. Appl. SCI ODBA Traditional ODBANon-JEE IMS ODBA TCP/IP TCP/IP Java Appl. SCI Connect Assembler Macro Appl. ODBA or DRA RYO DRDA Appl. TCP/IP ODBM DRA LPAR IMS DB SCI CAT © 2012 IBM Corporation 17
  19. 19. IMS 12: THE IMS CATALOG• HALDB PHIDAM / OSAM Database – Contains metadata about IMS database and program resources, and application information – Database Metadata • describes a physical database (ie. organization, segments, keys) – Program Metadata • describes a programs view of the database (ie. access, authority) – Application Metadata • describes an applications view of the data in the database – Fields not defined in DBD – Arrays and Structures – Field data types and data type conversion – Field redefines – Alternative Field maps for a segment – New ACBGEN • Generates ACB member and populates the catalog metadata in a single UOW © 2012 IBM Corporation
  20. 20. IMS Catalog• The IMS catalog is a key component of the IMS growth strategy: – Trusted IMS source for IMS database, program and application information – All Universal drivers leverage the IMS catalog • Direct access to IMS metadata in the catalog • No need for separate Java metadata classes on client platforms • Metadata no longer file-system dependent • Catalog metadata is kept up-to-date via new ACBGEN – Metadata discovery and exchange via IMS Open Database and the IMS Explorer for Development – Scalable Open Database solutions – Broad IMS integration with the IBM and ISV portfolio of tools (Optim Development Studio, Rational Asset Analyzer, InfoSphere Data Architect, etc) IMS Catalog available as of 2Q2012 for IMS 12! © 2012 IBM Corporation
  21. 21. IMS Enterprise Suite• IMS Enterprise Suite is a product within the IMS SOA Integration Suite – IMS Enterprise Suite DLIModel utility plug-in – IMS Enterprise Suite SOAP Gateway – IMS Connect APIs – Java Message Service (JMS) API – IMS Enterprise Suite Explorer for Development • IMS Explorer V2.1.1.3 download available as of 06-22-2012• Supported with SMP/E and the IBM Installation Manager• Supports IMS 10, 11 and 12 © 2012 IBM Corporation
  22. 22. IMS Enterprise Suite Explorer for Development • Visualization and editing of IMS DBD and PSB definitions – Provides graphical editors to: • Display IMS database hierarchical structures • Display/create/edit PSBs • Change/add fields on a DBDs – Import Cobol CopyBooks and PL/I Structures to a database segment* – Generate DBD and PSB source • Easily access IMS data using SQL statements – Leveraging IMS Universal JDBC driver • Access the IMS Catalog for metadata discovery • Connectivity to the z/OS system – Browse a Data Set and submit JCLs – Import / export DBD and PSB source from a data set to IMS Explorer • Supports cross-product integration: – IBM® Rational® Developer for System z® – IBM Optim™ Development Studio – IBM Problem Determination Tools Plug-ins for Eclipse Simplify IMS application development tasks *Requires RDz 8 © 2012 IBM Corporation
  23. 23. IMS Explorer: Revolutionizing IMS application development Graphically-driven editors to display and update IMS program and database definitions Graphical interface to easily access and manipulate IMS data using standard SQL See database relationships Generate SQL Change DBD and to access IMS PSB definitions data © 2012 IBM Corporation 22
  24. 24. IMS EXPLORERHANDS-ON LAB © 2012 IBM Corporation