AD04 - Modernization Strategies for Mainframe Environments Alex Louwe Kooijmans Solution Architect Financial Services CoE E-mail: alexl@us.ibm.com
Notices This information was developed for products and services offered in the U.S.A. Note to U.S. Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces. 2
Trademarks This presentation contains trade-marked IBM products and technologies. Refer to the following Web site: http://www.ibm.com/legal/copytrade.shtml
Agenda Introduction? Accommodating new functional requirements in z/os New runtime environments for Java batch on z/os Summary and Q&A
Is still modern? is still widely used and in many cases the best paradigm for data processing. Examples are: generating reports of all daily processed data paying salary for all employees archiving of historical data at the end of month reorganizing data processing files with large amounts of data from a partner Advantages of processing are: A batch and an online window allow balanced system usage with almost constantly 100% utilization. This helps to optimize IT resources and save costs. In other words, you use the mainframe during the non-office hours for work that does not need immediate response, freeing up cycles during the office hours for transactions that need immediate response. programs are more efficient performing repetitive logic. Postponing transactions can help to achieve more business security, e.g. intervening into money transfers that could damage your business.
Is still modern? (2) Some reasons for making a function a batch program are: Real-time processing of the business logic is not possible because there is a dependency on something else that is not available at that time. In this case the input of the transaction is put aside in a file or a database and being worked on later on in a batch program. This approach is the result of the functional design of the application. There is a large amount of repetitive processing, for example calculating tax withholdings on all salaries paid to the employees of a large company. Deferring CPU cycles to a time of the day that the system is not in use by online users. A good example is preparing all the printed invoices for the orders placed during the day. Building interface files with logical grouping of records to be sent to partners that are not directly connected to the Information Systems. We see this a lot in the banking industry. is, like before, an essential part of most business application solutions.
The Challenge! is a typical workload on mainframe systems that means long running applications for mass data processing which run during the night. Current Processing Technique 8 am 8 pm 8 am Online But businesses move toward a 24h and 7 days a week model, the batch windows become smaller. and OLTP run concurrently during a 24x7 period becomes the norm. 8 am Modern Processing Technique 8 am Online 7
Agenda Introduction? Accomodating new functional requirements in z/os New runtime environments for Java batch on z/os Summary and Q&A
The z/os Infrastructure is superior and unique in its Kind, but did you ever try any of the following in your z/os Environment...? generating PDF files in COBOL, PL/I or ASM? creating *.xls or *.doc files in traditional Mainframe programming languages? generating diagrams or graphics? sending e-mails? using remote services via TCP/IP, HTTP or Web Services? processing XML? New technologies need to be introduced to the z/os landscape to make all of the above examples possible.
Approaches Approach 1: Using new functionalities in traditional programming languages Approach 2: Executing Java in containers Approach 3: Java stand-alone Approach 4A: WebSphere XD Compute Grid Approach 4B: WebSphere Application Server Feature Pack for Modern Approach 5: PHP with BPXBATCH
Approach 1 Using new Functionalities in traditional Programming Languages XML support (incl. specialty engine support) Interoperability between languages Unicode support Using container functionalities CICS Web Services IMS Web Services
Approach 2 Executing Java in Containers Java in IMS BMPs Transactional Check pointing Comprehensive programming model IMS DB access DB2 Java Stored Procedures Can be called from any application Transactional JVM is persistent Example: DB2 Java Stored Procedure
Approach 3 Java stand-alone JZOS Part of IBM Java SDK for z/os Integration in JES Support for DD Statements Development in Eclipse based tools possible
Approach 3 Java stand-alone Example
Approach 4A WebSphere XD Compute Grid Java combined with all functionality provided by the WebSphere JEE Container Extension on top of WebSphere Application Server for z/os Java stand-alone functionality plus WAS Container management security, transactions and connection management Check pointing Persistent JVM QoS, such as high availability Reuse of OLTP code in WAS XD Compute Grid Container
Approach 4A WebSphere XD Compute Grid
Approach 4B WebSphere Application Server Feature Pack for Modern WebSphere Compute Grid Feature Pack for Modern batch WAS V7 What it is Java-batch programming model for development and deployment of batch applications What it offers Reduce cost of infrastructure due to concurrent execution of batch and OLTP workloads using shared business logic on a shared infrastructure integrated with WebSphere Application Server Reduced operational cost due to integrated administration of OLTP applications and batch job High throughput and low resource consumption on z/os for Java when collocated with data subsystems WebSphere Application Server Feature Pack for Modern
Approach 5 PHP with BPXBATCH Scripting language Port for z/os with full support available DB2 z/os integration Straight-forward development in Eclipse Many skills available Many applications available based on open source
Agenda Introduction? Accomodating new functional requirements in z/os New runtime environments for Java batch on z/os Summary and Q&A
Benefits of Java () on z/os zaap eligible Specific Java APIs for z/os Dataset and VSAM access Condition Code passing DFSORT support Writing Logstreams Triggering of Jobs from Java RACF APIs Local DB2 Database driver for high throughput Access to many Java skills Effective and efficient development tools available Availability of many classes, libraries, frameworks and apps based on open source Interoperability with other programming languages on z/os
z/os Runtime Environment (New) A new option for running batch work in z/os 1.13 Provides a managed environment for integration of Java and COBOL Consistent with IBM WebSphere based batch A subset of the WebSphere programming model Incorporated in the OS DB2 resource manager
Execution Runtime Environment Java COBOL with DB2 Interoperability Ability to replace/add functions in current 3GL DB2 (e.g. COBOL DB2) application inventory with new Java DB2 code Requires local attach z/os DB2 connection sharing for common DB2 access Requires UOW (Transactional) integrity among the application components A generalized solution without requiring a specific run-time or middleware, i.e. a pure batch environment Implementation requires little or no changes to existing code! Only requires special callbacks for commit/rollback
Our z/os Topology JES Single Step based JZOS JVM z/os Container Submit JCL JES BCDBATCH Proc Transaction Service z/os Plugin z/os Container Execution Service z/os Plugin Policy/logs Process Job Step JDBC Commit Rollback JAVA/Cobol App RRS shared attach Local DB2
Compute Grid Overview diagram Workload Scheduler (e.g. TWS) Jobs Online Applications APIs public submit(job j) { _sched.submit(j); } Workload Connector Parallel Job Manager Jobs Jobs Jobs Console Jobs Job Scheduler Job Job Job Jobs Jobs Jobs Jobs Jobs Jobs Container Container Container Compute grid provides parallel job management Per Line of Business Jobs are written in XJCL, an XML version of a job control language.
CICS Support for WebSphere Compute Grid Job Management Console Command Line Interface xjcl WebSphere Job Scheduler Job management console Web Application JAVA Job Logs JAVA CICS TS Grid Endpoint CICS TS Grid Endpoint Config JDBC Grid Endpoint Database (DB2) 2 3 xjcl Job Dispatcher Job Logsc Config Programmatic (EJB, JMS, OR Web Services) Job Logs WAS Config JDBC z/os JCL 1 WSGrid Client Job Scheduler Database (LRS) Job Logs WebSphere Grid Endpoint J2EE WebSphere WAS Config JDBC Container Database (LREE) Job Logs Grid Endpoint J2EE WAS Config
IMS Mixed Language Applications - Supported Scenarios Java Calls OO COBOL module (COBOL Compiler generates Java Wrapper and Shared Library containing COBOL code) with Enterprise COBOL for z/os V4.2 OO COBOL program can call Java Classes Procedural modules can be called from OO COBOL program PL/I modules can be called from Java through JNI (Java Wrapper must be created) PL/I modules can call Java trough JNI API
IMS - Interoperability in Java Regions IMS Java can be used to call COBOL and PL/I modules through JNI Server-Side Presentation Management Server-Side Business Logic IMS TM IMS JMP Region IMS JBP Region TCP/IP or SNA Control Region IMS Connect IMS z/os Platform IMS Application Server Java Applicat ion ClassforName(DLIDriver) get.connection(ims psb) Select From Where Close JNI JDBC Drivers Java Applicat ion ClassforName(DLIDriver) get.connection(ims psb) Select From Where Close DLI / DB2 JDBC Drivers OO COBOL Class or PL/I Module
Interoperability in IMS MPRs IMS MPR COBOL JVM created implicit Java code can be embedded Parameters to and from Java prepared through JNI API PL/I JVM created through JNI API Parameters to and from Java prepared through JNI API Java class called with JNI API Mixed Case COBOL Module calls Java Class or embeds Java code PL/I Module IMS MPR JVM executing Java Class JVM executing Java Class
Participate in the System z Expert and Superhero contest! Fill in your answer to the question below on the scorecard and deposit your card in the box! Running Java programs on z/os is possible: a.only if you have JZOS installed b.only if you have WebSphere Application server installed c.in various runtime environments, such as CICS and IMS regions, and native z/os d.only if you are using Open Source, such as PHP
30
Traditional Chinese Thai Russian Thank You English Bedankt Nederlands Merci French Obrigado Gracias! Spanish Arabic Brazilian Portuguese Danke German Simplified Chinese Japanese 31