Displaying items by tag: jcl

No change in business logic.
Reduction in overhead costs. 
Continuous development during and after migration.

These are a few modernization concepts that Scott Pickett, TSRI’s Vice President of Product Operations and Service Delivery, discussed on his recent appearance on Amazon Web Services’ APN TV channel. 

“TSRI allows for an ability to do automated transformation of not only your language, but your application to the cloud environment, allowing you to bring in skilled, modern technology to your legacy implementations, being able to drive down the cost point associated with ongoing operational costs, and being able to deliver new applications, new functionality, new screens, and new capabilities in that modern language,” he said in his talk. 

So what does that mean, exactly? 

In TSRI’s modernization of a major European bank to the cloud, that meant they modernized approximately 80,000 lines of code at 99.7% automation. In other words, only 384 of those lines of code were hand-written. That's big for a project of this size—but it's huge when you're talking about applications with hundreds of thousands or even millions of lines of code!

For any organization, whether in commercial enterprise organizations like the banking client mentioned above, or in government agencies, modernization reduces risk. 

“You're able to bring a new skill set, new experts that know Java and know CI and CD tools and apply them to your legacy application that's been modernized,” Scott said. “It literally also allows for the ability to drop tens of thousands, and even hundreds of thousands of dollars, off your monthly costs.” 

 

 

As Scott also noted in his presentation, “we can not only transform code quickly…because there are very, very few manual changes, but it also means that you can migrate to the cloud and then be able to not have any business logic change associated with that migration.” 

Maintaining business logic is a big deal when it comes to systems that measure their age in decades rather than years and the original programmers have long since moved on. 

One other interesting point Scott brought up is how TSRI’s tools have enabled customers to maintain agility and competitive advantage by providing its clients with the modern, cloud-based applications they need—all while reaching back to its legacy DB2 database that supports the applications that have yet to be modernized. 

Throughout the talk, Scott also pointed to how TSRI has adopted a step-wise model, which modernizes small applications or pieces of an application, tests for validity, then pushes into production before the next applications are transformed. Such a methodology allows the client to continue to develop in the legacy language, maintain a common data set, and minimizes business disruption to almost zero. 

 

 

“There’s no big delay. You can continue developing the legacy and we can migrate those legacy applications while the transformations are happening and migrate them into your modern environment,” he said. 

Scott also explains the steps of an automated migration in layman’s terms and how a TSRI transformation integrates cleanly into cloud services like AWS using containerization and microservices. 

We of course don’t want to spoil the presentation by giving everything away, so head over to APN TV and watch for yourself to learn about how automated modernization to the cloud will save your organization time, money, and the headaches from continuing to maintain legacy systems. 

Watch Scott’s APN TV appearance 

 

TSRI is Here for You

As a leading provider of software modernization services, TSRI enables technology readiness for the cloud and other modern architecture environments. We bring software applications into the future quickly, accurately, and efficiently with low risk and minimal business disruption, accomplishing in months what would otherwise take years.

See Case Studies

Learn About Our Technology

Get Started on your Modernization Journey Today!

 
 
Published in AWS

The original LifeComm application was written by CSC for Alico of Japan. Following the acquisition of Alico by MetLife, it was determined that the LifeComm application would require modernization. To support this, MetLife first needed to better understand this legacy application. MetLife engaged TSRI to provide an Application Blueprint® of the LifeComm application.

  • Customer & Integrator: MetLife / Alico Japan
  • Source & Target Language: COBOL, JCL, Assembler & Fortran to Java
  • Lines of Code: 14,066,925
  • Duration:  4 months
  • Services: Transformation Blueprint®Application Blueprint® 

Published in Case-Studies
Thursday, 10 September 2009 16:35

COBOL to C++ - STG Inc. - WSMIS-MICAP

As part of the Logistics Management System, the Weapon System Management Information System (WSMIS) is responsible for tracking combat capability and impending parts problems. The system was well regarded during Desert Storm for its ability to expedite repair or procurement of critical items. However this legacy COBOL system requires modernization to continue to fulfill its mission.

Customer:  STG Inc.

Source & Target Language: COBOL to C++

Lines of Code: 39,654

Duration:  4 months

Services: Code Transformation, Automated Refactoring, Database Transformation, Testing and Implementation Support, Transformation Blueprint®

 

 

Published in Case-Studies

With maintenance costs increasing for the national crime information tracking system, a significant portion of the agency's crime fighting budget was required for hiring staff with experience maintaining mainframes, non-adherence to the Common Operating Environment (COE) adding to costs, and aging technology (IBM Mainframe, DB2, CICS, CA-GEN, COBOL, Assembler, C, MQ Series, JCL) making enhancements difficult to perform, the nation crime fighting agency initiated a Legacy Migration study to assess migration from the current legacy application architecture to an open Java/JEE application architecture.

Customer:  Criminal Justice Information Services Division

Source & Target Language: Coolgen/COBOL to Java/JEE

Lines of Code: 4.3 Million

Services: Tuned JANUS Studio® to customer code, Coolgen/COBOL and C to Java/JEE Code Transformation, Coolgen/COBOL and C to Java/JEE Transformation Blueprint®

 

Published in Case-Studies