Elevating Application Performance with Latest IBM COBOL Offerings. Tom Ross Captain COBOL March 9, 20017

Transcription

1 Elevating Application Performance with Latest IBM COBOL Offerings Tom Ross Captain COBOL March 9, 20017

2 Agenda Why the need to stay current with compiler technology? COBOL V6.1 ABO V1.2 Benefits of Using COBOL & ABO together Q&A 2

3 Where did application performance improvements come from in the past? Very little performance improvement came from Applications: Applications Effort required to improve application performance HIGH Bulk of the performance improvement came from: Hardware Software Stack Software Stack Hardware MEDIUM LOW 3

4 Adapting to the new reality Requires more effort to achieve performance gains Recompile Refactor In the past Now and the future Effort required Applications Applications HIGH Software Stack Software Stack MEDIUM Hardware Hardware LOW 4

5 Value of IBM Compilers on z Systems Reduce CPU utilization by improving performance of applications Exploitation of z/architecture (z10, z196, zec12, zbc12, z13) Advanced Optimization Support next-generation Applications Modernize business critical System of Record applications to support new System of Engagement applications (e.g. web, mobile, cloud ) Support latest IBM Middleware (CICS, IMS, DB2 ) Improve Productivity New programming features New problem determination features 5

6 Old binaries cannot take advantage of latest z/architecture z10ec/z10bc ARCH(8) Decimal Floating Point (DFP) Wider immediate data z196/z114 ARCH(9) Distinct Operand Conditional Load High Word Instructions zec12/zbc12 ARCH(10) Decimal- Floating-Point Zoned- Conversion Facility z13/z13s ARCH(11) Decimal-Floating- Point Packed- Conversion Facility SIMD 6 Default ARCH level in Enterprise COBOL v6.1 is now ARCH(7) - IBM System z9ec (2094-xxx models) IBM System z9 BC (2096-xxx models)

7 Modernize business critical applications Extend Business Critical COBOL Applications to support new System of Engagement (SoE) Applications Increase performance of SoR Applications to handle increase in transaction volume Systems of Engagement (SoE) Apps Systems of Record (SoR) Apps Databases XML, JSON, Web Services, APIs C/C++, COBOL, PL/I, Java 7

8 COBOL on z Systems Two complementary offerings designed to improve performance of business critical COBOL applications Enterprise COBOL for z/os Compile and Optimize from COBOL source code Automatic Binary Optimizer for z/os Optimize existing program modules 8

9 Architecture Exploitation COBOL V4 and below generates base ESA/390 level code Optimized Programs COBOL V6 and ABO generates code up to z13/z13s ARCH(11) ARCH( ) ARCH(11) z13/z13s ARCH(0) Original Compiled Programs Using COBOL V6 or ABO to optimize COBOL applications will allow them to access over 600 new hardware instructions already on clients machines

10 Enterprise COBOL V6.1 An overview

11 Customer POLL #1 What are your plans for upgrading to Enterprise COBOL V6? In process of upgrading Planning to upgrade in 2017 Planning to upgrade in the next 2 years No Plan 11

12 Introduced major infrastructure changes in V5/V6 Advanced Optimization Framework COBOL Runtime Object and Debug formats Program Objects - Requires PDSE DWARF debug format Maintains source and binary compatibility Correct COBOL programs will compile and execute without changes and will produce same results Old and new code can be mixed within an application Removed some old language extensions and options Supports the ecosystem of programming tools supplied by IBM and ISVs. 12

13 Enterprise COBOL for z/os V6.1 GA March 18 th, 2016 Improved Scalability Expanded capacity to compile and optimize very large COBOL programs Compiler is now itself a 64-bit application utilizing increased address space and memory to optimize large 31-bit COBOL programs Deliver release-to-release performance improvement Fully supports z13 and z13s hardware Well-structured, compute intensive batch applications running on z13 compiled with COBOL V6.1 have shown CPU time reduction of up to 5% over the same applications compiled with COBOL V5.2; up to 40% over the same applications compiled with COBOL V4.2 1 New capability to generate JSON documents directly from COBOL Extend business critical (System of Record) applications written in COBOL to support mobile (System of Engagement) application where preference is REST/JSON New COBOL 2002 language features Improved migration from COBOL compilers prior to Enterprise COBOL V5 Improved reporting on invalid data and out of bounds checks to help clients detect errors in existing source Our experience with a beta version of COBOL V6.1 shows that this compiler allows us to successfully compile very large COBOL modules previously limited by COBOL V5. The new 64-bit infrastructure in COBOL V6.1 liberates the full functionality of the compiler in every scenario we ve tried. A COBOL DPP participant Performance results are based on an internal IBM compute-intensive test suite. Performance results from other applications may vary.

14 Performance COBOL V6.1 Reduces CPU and Elapsed Time & Service Units Consumed COBOL 6.1 Reduces CPU Time up to 40% compared to COBOL V4.2 35% 40% COBOL V4.2 COBOL V5.2 COBOL V6.1 Internal Benchmarks : Mix of Compute and I/O Bound Applications z13 Well-structured, compute intensive batch applications running on z13 compiled with COBOL V6.1 have shown CPU time reduction of up to 5% over the same applications compiled with COBOL V5.2; up to 40% over the same applications compiled with COBOL V4.2 The CPU time reductions will vary by application but expected to average around 10-15% Elapsed time and service units also decrease similarly *Performance data contained herein was generally obtained in a controlled, isolated environments. All benchmarks were compiled with ARCH(11), OPT(2), STGOPT,AFP(NOVOLATILE),HGPR(NOPRESERVE). level. Actual performance, cost, savings or other results in other operating environments may vary.

15 Customer Experiences Strong adoption >500 customers Positive feedback on performance of batch applications CPU reduction of 10% to 20% Best case: CPU reduction over 60% (Elapsed time reduction over 70%) reported by a major FSS customer in US #IBMz #DevOps #ibminterconnect HDZ-4449: Reducing CPU Usage for Critical Applications with IBM s Cutting-Edge COBOL Offerings - Mon, 20-Mar, 11:15 AM - 12:00 PM, Mandalay Bay South, Level 2 Breakers J (2 customers will be sharing their COBOL V5 experiences) 15

16 COBOL Offerings Through Time Compiler Front end Back End ABO Eligibility OS/VS COBOL 74 Std 1 st generation VS COBOL II 85 Std (new) 2nd generation (new) ABO 1.2 (must be LE enabled) COBOL/ Std (same) 2 nd generation (same) COBOL for OS/390 V2 85 Std (same) 2 nd generation (same) COBOL for z/os V3 85 Std (same) 2 nd generation (same) COBOL for z/os V4 85 Std (same) 2 nd generation (same) COBOL for z/os V5 COBOL for z/os V6 85 Std (same) Select 2002 Std 85 Std (same) Select 2002 Std 3rd generation (new) 3rd generation (same) ABO 1.2 ABO 1.2 ABO 1.1 or later ABO 1.1 or later Intend to support in future Extra work is needed when migrating across the thick lines because of infrastructure changes OS/VS COBOL migration new generations is the most difficult Migration from 2nd generation to 3rd generation is difficult Migration within the generation, is very easy, including from v5 to v6 Compiler Terms: Front End handles parsing and language rules Back End handles optimization and code generation 16

17 Migrating to COBOL V6.1 Migrating from older compilers (COBOL V4 or older) to V6 (or V5) Needs advance planning System setup (e.g. PDSE, memory requirements ) Identify and resolve old syntax removed in COBOL V6 Migrate applications compiled by OS/VS COBOL and VS COBOL II NORES to Enterprise COBOL Fix Invalid Program and Data Issues Re-compile Regression Test This is a one time investment Migrating from COBOL V5 to V6 is the same easier process as was migrating from COBOL V3 to V4 Consult Migration Guide or ask your IBM rep. to arrange a Migration Workshop 17

18 COBOL Migration Assistant Provide step-by-step guidance on migrating to COBOL V5V6 Allow users to log migration progress Cloud based - Hosted on Bluemix IBMid required for free access Visit 18

19 Automatic Binary Optimizer V1.2 A brief overview NEW

20 Customer POLL #2 Have you heard about Automatic Binary Optimizer? Yes No 20

21 Automatic Binary Optimizer (ABO) V1.2 Announced on Oct ; GA Nov. 11, 2016 Optimizes performance of load modules compiled with COBOL v4 and below Increases application performance Reduces CPU usage and operating costs Requires no recompilation, or source migration Targets latest z Systems (e.g. zec12,zbc12 & z13, z13s) Requires significantly less testing effort Complementary to COBOL V6 & COBOL V6 VUE ABO Original Program Binaries (Base ESA390) Optimized Program Binaries (Latest z Systems) 21

22 ABO performs global optimization ABO CSECT 1 Original Executable CSECTN Unbind Binary IR* Verify Verify Optimize Optimize Optimize IR Binary Rebind Done Optimized Executable CSECT 1 CSECT N *IR - Intermediate Representation 22

23 ABO Compatibility and Testing Binary As Input Options Unchanged Full Interoperability ABO optimizes the original binary so exact behavior of the original program is known. No compile options (performance or otherwise) are being changed Optimized program would run faster and would behave the same as the original program. Strong compatibility assurance for the modules produced by ABO Testing Requires System Verification and Performance Tests Only If something goes wrong, revert to using original program Users can optimize objects in test environment and to deploy executable to production environment 23

24 What s new in ABO v1.2? Optimization coverage Optimize programs compiled with VS COBOL II V1.3 & 1.4 (LE enabled) COBOL/ COBOL for MVS & VM V1.2 COBOL for OS/390 & VM V2.1 & v2.2 Enterprise COBOL V3 and V4 Optimize program modules containing CICS HANDLE ABEND & CICS HANDLE AID Link Libraries - Optimize partially bound program modules Scalability - Reduced ABO CPU usage by up to 9X and memory up to 35% Usability - Allows selection of objects to optimize IBM tooling support Compiler listings, SYSDEBUG or LANGX side files of original programs can be used along with ABO listings to create new side files that enable IBM tools to work with programs optimized by ABO. 24

25 Link Library Optimization Optimize partially bound (CALL=NO) program modules A1 A2 A3 Z1 Z2 Z3 COBOL Source code COBOL compilers generate A1 A2 A3 Z1 Z2 Z3 COBOL modules Binder generates A1 B3 M7 ~ ~ Z4 Mod1 A1 M7 C6 K3 :: Mod2 :: A1 J2 D9 F3 :: :: Mod121 A11 M7 C6 Mod122 K3 :: A1:: M7 X2 F3 :: :: Now A1 and M7 are optimized only once within the linked library instead of multiple times in the fully bound modules reduce ABO processing time Partially bound COBOL modules Fully bound COBOL program modules

26 User Scenario 1: Current Process COBOL Development, Compilation, Test and Deployment Change Management 1) Compile and Test Application COBOL Source COBOL Compiler Generates Compiled Application Binaries Testing Validates 2) Load + Run Application JCL z/os v2.1/2.2 Loads + Runs Compiled Application Binaries

27 User Scenario 2: Binary Optimization Process Optimization, Test and Static Selection Change Management 1) Optimize and Test Application (similar procedure to example 1) Selected Compiled Application Binaries (e.g. Performance Sensitive) ABO Generates Optimized Application Binaries (+debug metadata) *Testing focus on performance/scalability and less on business logic Testing* Validates 2) Static Selection: Load + Run Application JCL Modified JCL Pointing To Optimized + Original Application Binaries z/os v2.1/2.2 Loads + Runs Optimized + Original Application Binaries

28 Example 2 In Depth: Binary Optimization Process Optimization, Test and Static Selection 1) Optimize and Test Application Selected Compiled Application Binaries ABO Optimized Application Binaries Testing Using ABO in the static selection case is a matter of selecting compiled programs to optimize by using straightforward new JCL JCL to compile all M* members from IN.LOAD to an OUT.LOAD for zec12 and one for z13 //OPTIMIZE JOB //OPT EXEC PGM=BOZOPT,REGION=0M //STEPLIB DD DSN=$HLQ.BOZ110.SBOZMOD1,DISP=SHR //SYSPRINT DD DSN=$HLQ.BOZOUT.LISTING,DISP=SHR //SYSIN DD * BOPT IN=$HLQ.IN.LOAD(M*) OUT=$HLQ.OUT.LOAD.ZEC12 ARCH=10 BOPT IN=$HLQ.IN.LOAD(M*) OUT=$HLQ.OUT.LOAD.Z13 ARCH=1

29 Example 2 In Depth: Binary Optimization Process Optimization, Test and Static Selection (targeting multiple hardware levels)... //STEPLIB DD DSN=$HLQ.OUT.LOAD.Z13:$HLQ.IN.LOAD,DISP=SHR... z13... //STEPLIB DD DSN=$HLQ.OUT.LOAD.ZEC12:$HLQ.IN.LOAD,DISP=SHR... zec12 2) Static Selection JCL Modified JCL Pointing To Optimized + Original Application Binaries z/os Loads + Runs Optimized + Original Application Binaries Static selection requires modifications to all JCL that contained the original modules(s) to be updated to point to new modules(s) for each architecture being targeted

30 User Scenario 3: Binary Optimization Process Optimization, Test and Dynamic Selection Change Management 1) Optimize and Test Application (similar procedure to examples 1 & 2) Selected Compiled Application Binaries (e.g. Performance Sensitive) ABO 2) Load + Run Application JCL Original JCL Pointing Only to Original Application Binaries Generates * SMF for tracking changes in Optimization configuration Optimized Application Binaries (+debug metadata) Optimization Configuration z/os V2.2 SMF * *Testing focus on performance/scalability and less on business logic Loads + Runs Testing* Validates Optimized + Original Application Binaries

31 Example 3 In Depth: Binary Optimization Process Optimization, Test and Dynamic Selection 1) Optimize and Test Application ABO Testing Using the Optimizer in the dynamic selection case only requires pointing to active configuration by specifying IEFOPZ in JCL Selected Compiled Application Binaries Optimized Application Binaries (+debug metadata) Optimization Configuration //OPTIMIZE JOB //OPT EXEC PGM=BOZOPT,REGION=0M //STEPLIB DD DSN=$HLQ.BOZ110.SBOZMOD1,DISP=SHR //SYSPRINT DD DSN=$HLQ.BOZOUT.LISTING,DISP=SHR //SYSIN DD * IEFOPZ OLDNEW ( OLD( DSNAME (HLQ.IN.LOAD) ) NEW( DSNAME (HLQ.OUT.LOAD.ZEC12) ARCH(10) ) NEW( DSNAME (HLQ.OUT.LOAD.Z13) ARCH(11) ) INCLUDEMEMBERS(M*) OWNER(IBM) INACTIVE )

32 Example 3 In Depth: Binary Optimization Process Optimization, Test and Dynamic Selection (targeting multiple hardware levels)... //STEPLIB DD DSN=$HLQ.IN.LOAD,DISP=SHR e.g. target z13 and zec12... Unchanged JCL 2) Load + Run Application JCL Original JCL Pointing Only to Original Application Binaries SMF z/os 2.2 Optimization Product Infrastructure Optimization Configuration OLDNEW ( OLD( DSNAME (HLQ.IN.LOAD) ) NEW( DSNAME (HLQ.OUT.LOAD.ZEC12) ARCH(10) ) NEW( DSNAME (HLQ.OUT.LOAD.Z13) ARCH(11) ) INCLUDEMEMBERS(M*) OWNER(IBM) ACTIVE ) zec12 z13 Optimized + Original Application Binaries Dynamic selection requires no modifications to JCL. The new z/os infrastructure will select the highest ARCH NEW dataset available for the current machine Configurations trackable/auditable/viewable by SMF records and DISPLAY IEFOPZxx

33 Performance ABO Reduces Processing Time and CPU ABO 1.2 Reduces CPU Time and Service Units up to 35% 35% 25% 27% 29% Original ABO on COBOL V3/V4 ABO on COBOL V2 ABO on COBOL V1R2 ABO on VS COBOL II Internal Benchmarks : Mix of Compute and I/O Bound Applications z13 ABO produced modules perform the same amount of work but consume fewer CPU resources compared to the original module : reduce CPU usage reduce operating costs Beta/Trial customer results show reductions in CPU time between 5% 40% compared to the original program modules The CPU time reductions will vary by application but expected to average around 15% Elapsed time and service units also decrease similarly *Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary. 33

34 Tooling Support For The Optimized Modules What is changing in the optimized modules: New instructions will replace the original instructions An additional program literals area is created for use by the new instructions New language ID entries, timestamps and other metadata ABO IDRL is 5697-AB1 What is not changing in the optimized modules : All control blocks and data areas (e.g. TGT, DSA, working/local storage, original program literals) remain unchanged What ABO provides to support tooling enhancements: A listing transform to map original offsets/instructions to new offsets/instructions Retaining original metadata (e.g. language ID, timestamps, info signature bytes) in the optimized module New PPA4 section with information about the optimized module

35 Tooling Support For The Optimized Modules Listing Transform Walkthrough LEGEND: COBOL Program: COMPUTE WS-VAR-3 = WS-VAR-1 + WS-VAR-2. Source Line number in original program. CSECT offset of instruction generated by COBOL 4.2 Compiler CSECT offset of instructions generated by ABO COBOL v4.2 compiler listing: COMPUTE 00042C F247 D PACK 272(5,13),0(8,8) TS2=0 WS-VAR F D114 OI 276(13),X'0F' TS2= F247 D PACK 280(5,13),8(8,8) TS2=8 WS-VAR C 960F D11C OI 284(13),X'0F' TS2= FA44 D110 D118 AP 272(5,13),280(5,13) TS2=0 TS2= F D110 UNPK 16(8,8),272(5,13) WS-VAR-3 TS2= C 96F OI 23(8),X'F0' WS-VAR-3+7 Listing Transform: 00042C PACK 272(5,13),0(8,8) OI 276(13), C4 ED AA 00042C CDZT FP0,_WSA[0x12c] 0(8,R4),0x PACK 280(5,13),8(8,8) 00043C OI 284(13), CA ED AA CDZT FP1,_WSA[0x12c] 8(8,R4),0x AP 272(5,13),280(5,13) 0004D0 B3D ADTR FP0,FP0,FP UNPK 16(8,8),272(5,13) 00044C OI 23(8), D4 ED A C CZDT FP0, 16(8,R4),0x0 Input source instructions. Starts at column 1 Optimized Instructions. Starts at column 5 Each optimized instruction generated is also annotated with the source offset that it was generated for Allows tracking as instructions are re-ordered

36 Tools & Middleware Support IBM Application Delivery Foundation for z (ADFz) Provides Day-1 support SYSDEBUG of original programs can be used along with ABO Listings to create new side files to work with Fault Analyzer (FA) - Provide ABEND analysis of optimized load modules Debug for z - Allows users to step through and debug optimized programs interactively Application Performance Analyzer (APA) Allows users to compare the performance of original programs and optimized programs ISVs Tools Working with Compuware, CA, Macro 4 on ABO support Middleware DB2, CICS, and IMS FA APA Debug for z

37 ABO and COBOL V6 are complementary Recommendation : Use both offerings to increase time to value and ROI Use Case ABO COBOL V6 Improve performance without recompile, migration or options tuning No concerns for Interoperability/Legacy Compatibility Load modules, program objects, OS/VS COBOL etc No need to be limited by ARCH setting of DR* machine. Optimize for deployment machine and run original binaries on DR Source code not available New COBOL application development or modernize existing applications to work with new infrastructure (e.g. web, mobile.) Need source changes (e.g. defect fixes and/or minor enhancements) Maximize performance improvement *DR Disaster Recovery Machine Usually older hardware since it is only used in emergency situation. This limits Compiler ARCH setting used to compile the application. As a result, the application cannot be fully optimized deployment machine which usually is more current hardware.

38 Using COBOL V6 and ABO together COBOL V6 Defect Fixes Refactoring New programming features Modernization Recompile for Performance 10 % Additional recompile when upgrading to COBOL V6 to improve performance 20 % Recompile due to Source Change 70 % No recompile Plan ABO Increase performance of programs that have not been recompiled for a long time No source risk Less testing effort Reduce scope of V5/V6 migration Generate ROI to invest in business critical applications and adoption of DevOps

39 Economics Increase performance of COBOL applications Reduce Processing Time & CPU usage Reduce Batch Window Lowers cost of all MLC software by driving down peak 4HRA workload (MSU) or reclaim capacity for other business critical applications COBOL Applications... DB2 CICS Peak 4HRA MLC cost is calculated based on peak 4HRA workload (MSU) Save $ COBOL Applications... DB2 CICS Peak 4HRA Increase performance of COBOL Applications lowers peak 4HRA workload (MSU). Lowers MLC cost for entire system Reclaim Capacity CICS... DB2 COBOL Applications Peak 4HRA Increase performance of COBOL Applications lowers processing time and CPU but does not lower 4HRA. However, it allows customers to reclaim capacity for other workloads No ABO No COBOL V6 With ABO and/or COBOL V6 COBOL applications drive peak 4HRA With ABO and/or COBOL V6 COBOL applications run in white space 39

40 Trials Enterprise COBOL V6.1 Automatic Binary Optimizer for z/os Offers no charge evaluation license for up to 90 days Will not start SVC clock for COBOL V6.1 Allows clients to assess the value of Offerings Offer same function as GA product Ships with latest PTF Code processed by trial versions cannot be used for production Available as standard offering from IBM through ShopzSeries and Cloud Trial Service Contact your IBM representative for ordering assistance #IBMz #DevOps #ibminterconnect Visit us at the ABO Open Lab at Interconnect

41 #IBMz #DevOps #ibminterconnect TOP 5 MUST ATTEND SESSIONS TO STAY UP TO SPEED! DevOps for z Systems Date/Time Location Sessio n Session Title Mon, 20-Mar, 03:15 PM - 04:00 PM Mandalay Bay South, Level 2 - Breakers J #5951 [Keynote Session] DevOps for z Systems Kickoff: Cognitive DevOps for the Hybrid Cloud Wed, 22-Mar, 11:15 AM - 12:00 PM Tue, 21-Mar, 01:30 PM - 02:15 PM Tue, 21-Mar, 04:45 PM - 05:30 PM Mandalay Bay South, Level 2 - Breakers K Mandalay Bay South, Level 2 - Breakers J Mandalay Bay South, Level 2 - Breakers J #2623 Adopting DevOps at Ameriprise - one step at a time #2400 #1949 State Street - multi platform DevOps - RTC, UCD, GITHUB all in use to drive to continuous delivery Deploying COBOL applications with RTC and Urbancode at Rabobank: We re live! Mon, 20-Mar, 04:15 PM - 05:00 PM Mandalay Bay South, Level 2 - Breakers J #5617 Using Analytics to Improve Software Quality Over 300+ DevOps topics to choose from including keynotes, breakouts, engagement center, meet the experts, panels, labs, & workshops that s a whole lotta DevOps! Register for your favorite session

42 Q & A

43 Resources Enterprise COBOL Product Page: Documentation: Trial: COBOL Migration Assistant : ABO Product Page : Documentation: Technote for running on z/os V2.1: Trial Page: Trial on Cloud: ABO Demo: ABO v1.2 Blog: _for_z_os_v1_2_designed_to_speed_up_business_critical_cobol_applications_and_save_you?lang=en RFE community: COBOL ABO 43

44 Thank You