Transforming mission-critical applications on mainframes for innovation


Published on

[This presentation is available without detailled notes at]

Eranea's solution can be used to "clone" legacy applications (mainframe, Cobol) to x86/Java/web to delliver many flavours of innovations.

Those innovations - required by digital transformation of traditional large corporations - then smoothly integrate to existing mission-critical processes in order to spread quickly and be efficient at scale.

1 Like
  • Be the first to comment

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

No notes for slide

Transforming mission-critical applications on mainframes for innovation

  1. 1. Legacy transformation for agile innovation From legacy to Web, Java, Linux and cloud computing July, 2015 © Eranea 2015 - The aim of this presentation is to demonstrate that the advantages of Eranea's technology extend beyond the global global transformation of mainframe Cobol applications to java on x86 with maximum cost savings as priority #1. We want to demonstrate here that it also can be used to provide rapid innovation at scale on top of existing legacy systems For a technical description of our technology and its toolig, check out
  2. 2. 2 / 27© Eranea 2015 – agenda ● starting point ● needs of CIO / CDO ● deliverables ● rapid (& solid) innovation – examples ● methodology In subsequent pages, each time the user sees “Cobol”, he should read “the legacy language processed / transformed by Eranea”. It can be Cobol, JCL, BMS / 3270 maps, Assembler, RPG, PL/1, PacBase, CoolGen, etc. Cobol has been chosen here as a common name for the sake of brevity but also because it is by far still the most used of all programming languages in the world. According to public studies, more than 220 billions of lines of source code (and growing...) are active across legacy systems on the planet.
  3. 3. 3 / 27© Eranea 2015 – starting point ● a (very) large mission-critical application ● embedding the entire business expertise and driving key operational processes ● bullet-proof after 10 / 20+ years of continuous activity ● representing massive investments (10s, 100s, 1'000s men-years of development) ● doomed to technological obsolescence ● highly expensive compared to 2015 standard systems (x86) As usual starting point, the customer has a very solid mission-critical application: ● serving current business needs properly ● containing lots of intellectual property and representing massive investments through all this homegrown software (tens of millions of lines of Cobol) ● driving operational business processes efficiently at very large scale BUT ● far away from current technology standards. ● consequently, rather siloed / isolated from the rest of the IT system of the company. ● this application also creates a recruiting problem as people mastering mainframes and Cobol are all very close to retirement
  4. 4. 4 / 27© Eranea 2015 – needs of CIO / CDO ● rely on existing, solid and proven mission-critical systems to innovate and add more value to the business in a sustainable manner ● but, innovate quickly and on top for core processes but not aside : – become multi-channel : web, mobile, etc. – integrate 3rd parties : in-house packages, Internet services (SaaS via APIs: SalesForce, etc), – enterprise global connectivity : holistic BPM, global SOA, etc. – leverage innovation / economics of lowest layers : cloud computing, Big Data ● become economically eicient at the same time CDO and CIO do not want to create “islands of innovation” unable to scale up as they were tested / built separately from core systems and daily business processes. They rather want to innovate on top of the existing daily mission-critical IT activities to improve them but also to leverage their proven efficiency and reliability. “Agile Innovation in the core” is the goal. Additionally, the reach of maximum financial efficiency by leveraging optimal economics of new systems (x86) is also a target. Frugality is the menu of the day.
  5. 5. 5 / 27© Eranea 2015 – deliverables of Eranea (1) ● tactical : – massive cost savings → 80-90 % (capex + opex of M/F initial TCO) – back to standards → alternative suppliers rather than monopoly, leverage on innovative « boiling» of x86 / cloud platform – adequation with 2015 competences : M/F + Cobol getting (very) seldom → java, web and linux highly abundant Eranea's solution simultaneously to transcode Cobol/3270 to > Java/web delivers simultaneously on various targets: ● generate huge savings in costs : efficient use of Open Source software, competitive h/w (x86 / cloud) can divide initial mainframe costs by 10. ● transformation of Cobol to Java makes the application os-agnostic and h/w-agnostic. So, it can run on most efficient platform of 2015 (x86 + linux) as well as on many other possible platforms that support Java. ● Intense competition and boiling innovation on this x86 / linux market brings permanent improvements at no effort or cost. ● Additionally, teams can be reinforced by young engineers just out of university as the needs of the transformed application match their skills.
  6. 6. 6 / 27© Eranea 2015 – deliverables of Eranea (2) ● strategic : – technological transformation : x86, html/js, java, linux, etc. – functional improvements : ● new usage : tablets, mobile phones ● rich & lexible UI : state-of-the-art web interface – agility : core processes easily interoperable (soap, rest) via web services – elasticity / lexibility : new private cloud architecture can easily adapt to workload increase / change – attractiveness for recruiting IT staf: opportunity for learning of skills – etc. Tactical objectives (see previous page) are not sufficient for an optimal transformation project : long-term strategic needs must also be addressed. In that sense for example, a limited and raw replatforming of the Cobol application to x86 is irrelevant. Consequently, Eranea also delivers a deep technological transformation allowing new uses, rapid innovation on top of existing core system (see examples in next pages), elasticity (growth is embedded into the cloud architecture of the new cloud-based system) Last but not least, attractiveness is addressed : top engineers can be recruited to work on state-of-art technologies used to operate a very large scale system.
  7. 7. 7 / 27© Eranea 2015 – business case / ROI example 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% cpu peripherals (disks, tape drives, printers, etc.) 3rd party software IBM software (z/OS, Cics, DB2, etc..) factor 10 5.1 MEuros / year identical savings on numerous projects : minimum 80% and up to 90% ! project : international media group 500 kEuros / year via x86, Linux, Java (→ > 4.6 MEuros / year savings !) This slide is a standard business case when shifting from mainframe to x86. These massvie savings are driven by the efficiency and economics of the x86 platform combined to Open Source Software (linux, Java, etc.) In all our projects, TCO of initial system is divided by 10 when the transcoded application is operated the new system. In the mainframe case, it means tens of millions saved each year for large configurations with many thousands of Mips. As the picture demonstrates, largest savings comes from s/w (2/3 → ¾) rather than from s/w (1/3 → ¼) when transforming a mainframe to x86.
  8. 8. 8 / 27© Eranea 2015 – rapid but solid innovation Our solution doesn't require all-or-nothing approach: ● can address only top priorities of customer : – quicks wins or pain points ● can deliver visible results early on : – large scale transformation as second priority ● can start at (very) small scale : – and gradually extend to entire core IT ● ... but remains at all time fully integrated with core systems / processes Innovation is not afterthought in Eranea's transformations : it is often the initial driver of projects decided by customers. Consequently, our technology is designed to allow many smaller-scale subprojects to happen early on, strictly aligned with customer's innovation priorities. According to needs, the “pain points” or “quick wins” can be handled first, before the large-scale and global transformation happens. But, those early innovation always rely on amd leverage existing and proven processes (as cloned to the new Java/x86 platform)
  9. 9. 9 / 27© Eranea 2015 – rapid innovation #1 ● quick win on all our projects ● for internal & external users ● new web interface ● new use cases : tablets, mobile From « green screen » to rich web / mobile interface (= tip of the iceberg) Example : most of our projects The first innovation leveraged by all projects is the transformation of UI from passive / « green » screen (3270 / 5250) to rich web interface. The core IT is now fully integrated in the corporate Intranet as it gets accessible via the browser. It also respects the corporate graphical look-and-feel. this new UI technology can be used to enhance the interface to make it look like the applications that all corporate users are used to access on their tablet / mobile phone. It can also be used to allow new use cases : workers mobile in factories / warehouses can now interact constantly with the core IT via a tablet rather only when at their desktop via their computer. This is really the « tip of the iceberg » : most visible and often most appreciated innovation even if not most complex topic.
  10. 10. 10 / 27© Eranea 2015 – rapid innovation #2 Cobol JAVA data WS interface (generated) Integration of 3rd party package Example : large private bank new PMS integrated with core banking ● integration of 3rd party package ● integration into corporate ESB / SOA ● leverage of core processes / data ● can happen early on (not all users migrated) REST / SOAP migrated users non- migrated users (not yet!) In that case, the Cobol programs transformed to Java are equipped with a web service front-end (that is automatically generated by our tooling) to be accessible via soap or rest protocols from peripheral servers. The legacy application becomes part of the corporate Service-Oriented Architecture (SOA) or ESB (Enterprise Service Bus) It can also easily feed 3rd party packages as soon as they get installed : their added-value is consequently maximum since they can work at full scale with synchronous access to all corporate data from day 1 : no need for data mirroring generating synchronization issues.
  11. 11. 11 / 27© Eranea 2015 – rapid innovation #3 Cobol data Self-service / internet access for customers Example : international media group advertising management accessible on the web ● web interface leveraged for Internet access ● ditto for mobile access via employees ● can happen early on (not all users migrated) migrated users non- migrated users (not yet!) JAVA + web a corollary / consequence of innovation #1 : the legacy system now gets accessible from the most ubiquitous interface technology : web browser. So, mission-critical and corporate data can be easily exposed “live” (no copies / mirror required) on the web according to the security rules that are enforced by ad hoc policies and devices.
  12. 12. 12 / 27© Eranea 2015 – rapid innovation #4 Example : international media group processes distributed across partners integration in distributed BPMS (SaaS) JAVA WS interface (generated) REST / SOAP Cobol ● easily integrate / orchestrate internal core processes with partners ● tightly monitor entire process scope data Similar to innovation #3, innovation #4 is aimed at machine-to-machine (M2M) interconnection : it allows integration of mission-critical systems with external 3rd party platforms (like Salesforce or any marketplace) iin order to maximize the efficiency of internal processes.
  13. 13. 13 / 27© Eranea 2015 – rapid innovation #5 Example : Leading retailer improved inventory management integration Big Data Hadoop Cobol ● Batch programs transformed Cobol → Java can run on Hadoop (natively written in Java) ● Massive speed up : 6 hours to 10 min (example) ● More sophisticated calculations possible HDFS / HBase transformed batches (Java) data data synchronisation Innovation #5 is based on the fact that new source code for the application is Java (transcoded from Cobol). The batch programs become then compatible with Hadoop (natively written in Java) and can easily run on such a Big Data cluster. The immediate effect of this new compatibility with Hadoop is a huge boost of performances as data access gets massively parallel. This huge boost can then be used to speed up processes and get close to “real-time business” with all its advantages (reduced inventory, etc.) Additionally, the saved time can be leveraged to increase sophistication computations done in those batch programs.
  14. 14. 14 / 27© Eranea 2015 – rapid innovation #6 Example : Marketing company / ISV loyalty program management / industrial ERP New channels / clients Cobol ● application no longer tied to high-end infrastructure ● can be sold / rented on standard / simple infrastructure ● new customers can be reached data JAVA + web dbms « shadow version » (automatic) New channels / clients
  15. 15. 15 / 27© Eranea 2015 – methodology
  16. 16. 16 / 27© Eranea 2015 – Eranea's value proposition ● deep technological transformation while guaranteeing : – investment protection : application software and human business expertise – massive cost reduction (> 80% of initial TCO) ● via a unique migration path : – allowing continued maintenance (no stop) during project execution – luid, incremental and secure progress : no big-bang (iso- functionnality, very small granularity) – industrial and repeatable process (100% automated application transformation) ● with advanced and complete tooling for project execution and subsequent operations on new system : – NeaControlCenter + associated components see htttp:// for more details
  17. 17. 17 / 27© Eranea 2015 – cornerstones ● 100% automation : – repeated N times per day to keep M/F & x86 in full synch ● strict iso-functionality : – exact same results (to the « last bit ») on M/F and x86 – processing location becomes irrelevant ● incremental migration : – enabled by combination of automation & iso- functionality – no Big Bang : no risk. see htttp:// for more details
  18. 18. 18 / 27© Eranea 2015 – incremental migration (1) DB2 TP / batch z/OS DB2 / ORCL TP / batch Linux DB2 TP / batch z/OS TP / batch Linux time migration : users & jobs N months DB migration mainframe stop x86 setup install transco + NCC initial tests maintenance in Cobol maintenance in Java unique DB at all time start end see htttp:// for more details
  19. 19. 19 / 27© Eranea 2015 – incremental migration (2) part 1 part 2 part 3 part N part 1 part 2 part 3 part N tests + rollout overlapping and combined migration ... start end  reduced duration  early hands-on  rapid feedback  quick savings test rollout time completion 0% 100% continuous offload progress Part N = set of programs used by role in enteprise : clerk, sales person, plant manager, etc. see htttp:// for more details
  20. 20. 20 / 27© Eranea 2015 – incremental migration (3) Y weeks time activity Cobol on z/OS Java on x86 100% X months (X defined by customer) Cobol remains reference Java = reference datamigration tolinuxdbms stop mainframe CICS progressive migration big bang avoidance → critical success factor instantaneous way-back 0% cost reduction (if MLC)! JAVA DB2 see htttp:// for more details
  21. 21. 21 / 27© Eranea 2015 – project : standard steps initial presentation(s) technical workshop(s) in-depth analysis Proof of Concept proposal / contract solution / installation part 1 / part N client OK global validation detailed concept + business case / ROI N transactions + batch jobs fully running by customer see htttp:// for more details
  22. 22. 22 / 27© Eranea 2015 – conclusion ● « Innovation in the core » is possible ● at no risk ● with early visible results ● ... while doing in-depth transformation ● ... bringing massive savings
  23. 23. 23 / 27© Eranea 2015 – Thanks ! ● questions ? Eranea | Lausanne (Switzerland)
  24. 24. 24 / 27© Eranea 2015 – technological core “Cobol” support SQL support CICS Emulation Display support Tracing / logging Internal Object implementation Java Program (incl SQL) XML Screen DBMS Lexical Analysis Syntax Analysis Semantics Analysis NeaTranscoder NeaRuntime SOA / BPM Online Batch 2 distinctive features : 100% automation + strict iso-fonctionnality remains after project XCL Code Generation Cobol copy Cobol pgm BMS desc JCL disappears after project ws front-end (soap, rest) see htttp:// for more details
  25. 25. 25 / 27© Eranea 2015 – architecture (1) production BATCH sources repository DB ERIT NeaControlCenter (+ standard console) migration factory CI engine application code DB2 production TP analyze, transcode, compile, package run tools installed on-site → “continuous migration” multi-layer processing cluster : (unification, distribution, processing) JDBC / DRDA feedback (jmx, snmp) private cloud (CloudStack,OpenStack,etc.) « engineered x86 system » : Cisco UCS, IBM Flex, Oracle Exa, EMC VCE, HP CloudSystem, etc. deploy (war, zip) synchronous data mirroring (real time) backup datacenter RACF / TopSecret LDAP see htttp:// for more details
  26. 26. 26 / 27© Eranea 2015 – architecture (2) DB2 scheduler agent DFS server mail server HFS docs server print server SAN DB access shared files access common services access storage access logical conditions management + job launching remote synchronous mirroring backup SAN z/OS scheduler (ex : TWS, Control/M Autosys, CA7,etc.) Architecture / structure : ● scheduling logic and organization fully preserved ● dynamic (optimized) worker sheduling via agents ● centralized supervision / reporting on NeaControlCenter ● file sharing with z/OS (via HFS) as needed ● ad hoc (= out of plan) job launching via NeaControlCenter scheduler agent scheduler agent scheduler agent see htttp:// for more details
  27. 27. 27 / 27© Eranea 2015 – tests for transactional & batch CICS DB2 XML screen / kb data 3270 XML screen /kb data HTML XML screen / kb data bug fix : runtime / application (1) (2) (3) (4) if (1) & (3) different DRDA to DB2 (via JDBC) capture replay (batch or TP) code coverage measurements to quantify tests exhaustivity 100s / 1'000s captures JAVA example: 35'000 screens to cover 10M lines at 90% level application programs sometimes still have bugs ... XML modified db lines triggers see htttp:// for more details