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

© 2011 IBM Corporation

Java and IMS on System z

Kyle CharletSTSM, IMS SOA and [email protected]

© 2011 IBM Corporation2

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.

IBM, the IBM logo, and ibm.com 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 other companies. A current list of other IBM trademarks is available on the web at "Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml

Other 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 INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. 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 ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF ANY AGREEMENT OR LICENSE GOVERNING THE USE OF IBM PRODUCTS OR SOFTWARE.

© Copyright International Business Machines Corporation 2011. All rights reserved.

Trademarks, Copyrights, Disclaimers


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


Current Java Support

J9 R2.6 Virtual MachineSignificant enhancements to JIT optimization technologyz196 exploitation of instructions and new pipelineNew Balanced GC policy to reduce max pause times

– Default GC policy changed to gencon

z196 and Java6.0.1: Engineered TogetherUp to 2.1x improvement to Java throughput

Reduced footprint

Tighter integration with z/OS facilities

Improved responsiveness in application behavior

Performance2.1x improvement to multi-threaded workload1.93x improvement to CPU-intensive workload

z/OS Unique EnhancementsJZOS 2.4.0z/OS Java unique security enhancements


IBM J9 2.6 and z196

J9 R26: JRE for z196Reducing 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

z196: Hardware for JavaNew Out-Of-Order pipeline designNew larger cache structureHigher clock speed (~5.2GHz)


IBM J9 2.6 Technology Enhancements:Garbage Collection: Balanced Policy

Improved 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 consumption

Next 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) arrays

Input welcome: Help set directions by telling us your needs


z/OS Java SDK 6.0.1 performanceAggregate HW and SDK improvement z10, z196, Java6 to Java6.0.1

~7x aggregate improvement from z10, z196, Java6 and Java6.0.1

(Controlled measurement environment, results may vary)

z/OS Multi-Threaded 64 Bit Java Workload

0

10

20

30

40

50

60

70

80

90

1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32

Threads

Thro

ughp

ut

z196 SDK 6.0.1 J9 2.6 LP CRz10 SDK 6 SR4 J9 2.4 LP CRz10 SDK 6 GM J9 2.4z9 Java 5 SR5 J9 2.3


IMS JMP region performanceAggregate SDK and SW improvement

(Controlled measurement environment, results may vary) z196™ – z/OS V1.12

81%

11%

2 GCP + 2 zAAP

~2.5x aggregate throughput improvement from Java5 to Java 7

IMS JMP ETR Improvements Java 5, Java 6, Java 601, Java 7

3900

6992 7518 8074191

608930

1315

0

1000

2000

3000

4000

5000

6000

7000

8000

9000

10000

Java 5 (2009) Java 6 (2010) Java 6.0.1 (2011) Java 7 (2011)

Java Release (year)

Thro

ughp

ut

(big

ger i

s be

tter

)

zAAP

CP9389


Java and IMS

IMS 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

Java is an integral component of the IMS modernization strategyEnable 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 containers


Java and IMS – IMS 7 to IMS 12 (highlights)

V7

Dedicated investment for well over a decade…and continuing

Initial Java supportJDR APIJDBC 1.0

DB2 access from JDRsJDBC 2.0

IMS CatalogIncreased application scalabilityJDBC 4.0

Universal Java EE, JDBC, DLI driversJDR resource adapter

Java support in MPP/BMP/IFPDB2 JCC support in MPP/BMP/IFPJDBC 3.0

Improved language interoperabilityJava callout support (JMS)Java z/OS partnership

Remote access

V8

V9

V10

V11V12


Java and IMS moving forwardJava z/OS stakeholder

Continued partnership to maximize synergy between IMS and Java z/OS

PerformanceAggressive performance analysis and cooperative approach to continue h/w and s/w exploitation

Enterprise modernizationLanguage interoperabilityUniversal drivers/JDR resource adapter

IntegrationAggressive approach to horizontal integration across IBM portfolio

– Rational– Cognos– Data Studio– InfoSphere


Java and IMS moving forward

Continued modernization of the core systemIMS catalogDatabase versioningDynamic databaseNative SQLProgramming models


Business Challenge– Modernize existing core services

– Offer new services framework to business partners

– Impaired ability to deliver new functionSolution

– Leverage the JDR resource adapter and Universal JDBC and Universal DLI drivers for IMS

– Integration of existing assembler modules common to the application framework

– Deployment in JMP regions

– Initially no language interoperability (pure Java)

• Future direction

Benefits– Leverage abundant Java domain

knowledge in industry

– Dramatically increased time to market

– IMS API consistency with relational databases

Who– Worldwide bank

• Core banking system managed by IMS TM/DB and written mostly in COBOL


Business Challenge– Introduce additional core services to support

new banking channels

– Impaired ability to deliver new function

Solution– Introduce a new banking channel

implemented in Java using the Universal JDBC and Universal DLI drivers for IMS

– Deployment in CICS JCICS regions

– Initially no language interoperability (pure Java)

• Future potential

Benefits– Leverage abundant Java domain

knowledge in industry

– Dramatically increased time to market

– IMS API consistency with relational databases

Who– Bank in US

• Several banking channels managed by IMS and written mostly in COBOL


Business Challenge– Integration of 3rd party credit checking technology

that was part of a Java package

Solution– Leverage the deferred program

switching support in Java class libraries to switch conversation iterations from MPP to JMP regions and back

Benefits– Ability to leverage decades of existing

assets and add in new Java-based services into the architecture transparently

– Just another service

– In production within a month with this solution

Who– German bank

• Framework mainly PL/I with conversational transactions


Business Challenge– Required open systems access to IMS database assets

– Error-prone process to accomplish task• Unloaded databases and did manual entry into open

system database

Solution– Leverage IMS Open Database

technology and the Universal JDBC driver Benefits

– Real-time access to data

– Confident decision making

– Trusted information

Who– Caterpillar

• Core manufacturing system managed by IMS


Business Challenge– Integrate critical applications after merger with Delta

– Implement a distributed application front-end using SOA on top of existing z/OS

Solution– Implement IMS/JDBC on z/OS to

integrate technical operations data via ESB and WebSphereApplication Server

Benefits– 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

Who– Northwest Airlines/Delta

• Largest airline in the world

• Technical operations managed by IMS


Summary

The partnership of IMS and Java technology is capable of handling mission-critical workloadIMS is an important stakeholder in the IBM Java on System Z strategyJava running in IMS regions has been benchmarked at 9400 transactions per second

IMS and Java infrastructure is future-proof with a compelling roadmap as we move forwardConstantly validating the roadmap with customers

Many customers are modernizing their IMS application development patterns and access paradigms around Java as the primary language of choiceOver 40 proof of concepts in the last year alone