Java and IMS on System Z - IMS UG May 2012 Stockholm, Helsinki


Published on

Published in: Technology, News & Politics
  • 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

Java and IMS on System Z - IMS UG May 2012 Stockholm, Helsinki

  1. 1. Kyle CharletSTSM, IMS SOA and and IMS on System z © 2011 IBM Corporation
  2. 2. Trademarks, Copyrights, DisclaimersIBM, the IBM logo, and are trademarks or registered trademarks of International Business Machines Corp.,registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or othercompanies. A current list of other IBM trademarks is available on the web at "Copyright and trademark information" at company, product, or service names may be trademarks or service marks of others.THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY.WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATIONCONTAINED IN THIS PRESENTATION, IT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY,WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANYDAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHERDOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, NOR SHALL HAVE THEEFFECT OF, CREATING ANY WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS ORLICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF ANY AGREEMENT OR LICENSE GOVERNING THEUSE OF IBM PRODUCTS OR SOFTWARE.© Copyright International Business Machines Corporation 2011. All rights reserved. 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.2 © 2011 IBM Corporation
  3. 3. Session Objectives and Agenda Objectives – Review and validate IMS and Java strategy Agenda – Java z/OS platform strategy – Java and IMS strategy and direction – Future enhancements © 2011 IBM Corporation
  4. 4. Current Java Support z196 and Java6.0.1: Engineered Together Up to 2.1x improvement to Java throughput Reduced footprint Tighter integration with z/OS facilities Improved responsiveness in application behavior J9 R2.6 Virtual Machine Significant enhancements to JIT optimization technology z196 exploitation of instructions and new pipeline New Balanced GC policy to reduce max pause times – Default GC policy changed to genconz/OS Unique Enhancements Performance JZOS 2.4.0 2.1x improvement to multi-threaded workload z/OS Java unique security enhancements 1.93x improvement to CPU-intensive workload © 2011 IBM Corporation
  5. 5. IBM J9 2.6 and z196z196: Hardware for Java New Out-Of-Order pipeline design New larger cache structure Higher clock speed (~5.2GHz)J9 R26: JRE for z196 Reducing pressure on the data/instruction cache – Enables better exploitation of new OOO compute bandwidth – Mitigates effects of cache latencies for leveraging core speed Concurrency improvements – Better scalability General optimizer and codegen improvements – Reduced path-length © 2011 IBM Corporation
  6. 6. IBM J9 2.6 Technology Enhancements: Garbage Collection: Balanced PolicyImproved responsiveness in application behavior – Reduced maximum pause times to achieve more consistent behavior – Incremental result-based heap collection targets best ROI areas of the heap – Native memory aware approach reduces non-object heap consumptionNext generation technology expands platform exploitation possibilities – Virtualization – Group heap data by frequency of access, direct OS paging decisions – Dynamic reorganization of data structures to improve memory hierarchy utilization (performance)Recommended deployment scenarios – Large (>4GB) heaps – Frequent global garbage collections – Excessive time spent in global compaction – Relatively frequent allocation of large (>1MB) arraysInput welcome: Help set directions by telling us your needs © 2011 IBM Corporation
  7. 7. z/OS Java SDK 6.0.1 performance Aggregate HW and SDK improvement z10, z196, Java6 to Java6.0.1 z/OS Multi-Threaded 64 Bit Java Workload ~7x aggregate 90 improvement 80 from z10, z196, 70 Java6 and z196 SDK 6.0.1 60 J9 2.6 LP CR Java6.0.1 z10 SDK 6 SR4 Throughput 50 J9 2.4 LP CR z10 SDK 6 GM 40 J9 2.4 z9 Java 5 SR5 30 J9 2.3 20 10 0 1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 Threads (Controlled measurement environment, results may vary) © 2011 IBM Corporation
  8. 8. IMS JMP region performance Aggregate SDK and SW improvement IMS JMP ETR Improvements Java 5, Java 6, Java 601, Java 7 11% ~2.5x aggregate 10000 throughput 81% 9000 1315 improvement 8000 930 608 from Java5 to 7000 Java 7(bigger is better) Throughput 6000 zAAP 5000 9389 CP 4000 191 8074 7518 6992 3000 2000 3900 1000 0 Java 5 (2009) Java 6 (2010) Java 6.0.1 (2011) Java 7 (2011) Java Release (year) 2 GCP + 2 zAAP (Controlled measurement environment, results may vary) z196™ – z/OS V1.12 © 2011 IBM Corporation
  9. 9. Java and IMSJava is an integral component of the IMS modernization strategy Enable customers to quickly achieve IMS value while significantly reducing development costs and improving productivity IMS leverages the IBM JVM for System z and integrates it into the IMS runtime containersIMS family has a long-term commitment to Java Investing over 50 FTEs (full-time equivalents) in Java technology moving forward – IMS dependent region types (JMP, JBP, MPP, BMP, IFP) – Java EE platform (WebSphere Application Server) – z/OS and open systems access to IMS assets © 2011 IBM Corporation
  10. 10. Java and IMS – IMS 7 to IMS 12 (highlights) Dedicated investment for IMS Catalog well over a decade…and Increased application scalability JDBC 4.0 continuing Java support in MPP/BMP/IFP V12 DB2 JCC support in MPP/BMP/IFP JDBC 3.0 V11 DB2 access from JDRs V10 JDBC 2.0 Universal Java EE, JDBC, DLI drivers V9 JDR resource adapter Improved language interoperability V8 Java callout support (JMS) Java z/OS partnership Remote access V7 Initial Java support JDR API JDBC 1.0 © 2011 IBM Corporation
  11. 11. Java and IMS moving forwardJava z/OS stakeholder Continued partnership to maximize synergy between IMS and Java z/OSPerformance Aggressive performance analysis and cooperative approach to continue h/w and s/w exploitationEnterprise modernization Language interoperability Universal drivers/JDR resource adapterIntegration Aggressive approach to horizontal integration across IBM portfolio – Rational – Cognos – Data Studio – InfoSphere © 2011 IBM Corporation
  12. 12. Java and IMS moving forward Continued modernization of the core system IMS catalog Database versioning Dynamic database Native SQL Programming models © 2011 IBM Corporation
  13. 13. Who – Worldwide bank Business Challenge • Core banking system managed by IMS TM/DB – Modernize existing core services and written mostly in COBOL – Offer new services framework to business partners – Impaired ability to deliver new functionSolution – Leverage the JDR resource adapter and Universal JDBC and Universal DLI Benefits drivers for IMS – Leverage abundant Java domain – Integration of existing assembler modules common to the application framework knowledge in industry – Deployment in JMP regions – Dramatically increased time to market – Initially no language interoperability (pure – IMS API consistency with relational Java) databases • Future direction © 2011 IBM Corporation
  14. 14. Who – Bank in US Business Challenge • Several banking channels managed by IMS and written – Introduce additional core services to support mostly in COBOL new banking channels – Impaired ability to deliver new functionSolution – Introduce a new banking channel implemented in Java using the Benefits Universal JDBC and Universal DLI – Leverage abundant Java domain drivers for IMS knowledge in industry – Deployment in CICS JCICS regions – Dramatically increased time to market – Initially no language interoperability – IMS API consistency with relational (pure Java) databases • Future potential © 2011 IBM Corporation
  15. 15. Who – German bank Business Challenge • Framework mainly PL/I with conversational – Integration of 3rd party credit checking technology transactions that was part of a Java packageSolution – Leverage the deferred program switching support in Java class libraries to switch conversation Benefits iterations from MPP to JMP regions – Ability to leverage decades of existing and back assets and add in new Java-based services into the architecture transparently – Just another service – In production within a month with this solution © 2011 IBM Corporation
  16. 16. Who – Caterpillar Business Challenge • Core manufacturing system managed by – Required open systems access to IMS database assets IMS – Error-prone process to accomplish task • Unloaded databases and did manual entry into open system databaseSolution – Leverage IMS Open Database technology and the Universal JDBC driver Benefits – Real-time access to data – Confident decision making – Trusted information © 2011 IBM Corporation
  17. 17. Who – Northwest Airlines/Delta Business Challenge • Largest airline in the world – Integrate critical applications after merger with Delta • Technical operations – Implement a distributed application front-end using managed by IMS SOA on top of existing z/OSSolution – Implement IMS/JDBC on z/OS to integrate technical operations data via ESB and WebSphere Benefits Application Server – Technical infrastructure is much more open and primed for integration across the enterprise – Smooth integration of all critical applications running on z/OS after merger with Delta © 2011 IBM Corporation
  18. 18. SummaryThe partnership of IMS and Java technology is capable of handling mission- critical workload IMS is an important stakeholder in the IBM Java on System Z strategy Java running in IMS regions has been benchmarked at 9400 transactions per secondIMS and Java infrastructure is future-proof with a compelling roadmap as we move forward Constantly validating the roadmap with customersMany customers are modernizing their IMS application development patterns and access paradigms around Java as the primary language of choice Over 40 proof of concepts in the last year alone © 2011 IBM Corporation