Displaying items by tag: cobol

Using money from the Technology Modernization Fund (TMF) under the Modernizing Government Technology Act disbursed by the General Services Administration (GSA) of the U.S. government, the Department of Housing and Urban Development (HUD) sought to modernize several of its remaining critical systems on a legacy Unisys mainframe written in COBOL with a flat-file DMS-II database.

Customer: Department of Housing and Urban Development and Salient CRGT Source & Target Language: Unisys COBOL to Java Lines of Code: 1.3 Million Duration:  8 Months Services: Automated Code Transformation, Automated Refactoring, Integration and Testing Support, Enginerring Support, Software Maintenance Agreement, Transformation Blueprint®, Application "As-Is" Blueprint®,

How do you transform the slow pace of technological innovation within a federal agency into an opportunity for innovation and IT systems modernization? Start by taking a cue from the partnership between TSRI and GovCIO. With backing from the Federal Government’s Technology Modernization Fund (TMF) our joint teams propelled the US Department of Housing and Urban Development (HUD) from an outdated twentieth-century Unisys COBOL system into modern, service-oriented Java that was performant and functionally equivalent.

TSRI worked with GovGIO on their process designed to successfully migrate the applications to the Microsoft Azure cloud. They started by defining the five key project goals and taking an inventory of system components, including intersecting platforms. Once we had identified what the unique technical challenges were and how to address each, we created testing strategies and migrated the data stores for each system. Finally, we executed an automated code conversion and refactored the legacy COBOL code.

TSRI’s partnership with GovCIO executed a rapid, holistic mainframe migration process for HUD that has improved their organizational performance while minimizing risk. On day one after the productions systems were switched over from the Unisys mainframe to the Microsoft Azure cloud, the new system supported 25,356 users and 299,715 transactions with only three user problems reported. These are the HUD systems that manage, store, and protect all the personal financial and employment-related eligibility information for FHA insured financing. Given the criticality of the data managed every day by HUD, it was important that the migration run without impact on operations. The result could be seen in the first 30 days during which the new system disbursed just over $2.7 billion dollars in HUD program funds without a single error.

Review the details of how TSRI and GovCIO successfully executed this complex modernization project in our recently published case study.

The 9 Low-Risk Steps That Led to Success

You might be surprised that HUD and other government agencies still run their IT on mainframes using COBOL (first released in the 1950’s), or MUMPS (from the 1970’s). Running on these aging platforms presents an extensive list of challenges to these agencies: data management, growing storage, collaboration, security, etc. The modernization process typically involves risk, time, and significant expense. It’s understandable that a large agency like HUD would want to select a partner they knew could deliver a low-risk, high-accuracy result.

Working together, we adhered to GovCIO’s nine-step best-practices process that resulted in modernizing systems to modern cloud architectures that can now evolve with HUD, while preventing negative impacts to their mission, day-to-day operations, and security.

For more details on the nine-step process that enabled HUD to enter the cloud age, read our latest white paper with GovCIO.

A first-person account of HUD’s modernization process with Roger Knapp – Executive Vice President and HUD Program Manager

Only a few engineers know what it feels like to lead a major government agency through an automated mainframe modernization. Roger Knapp is one of them and has been working in the field for over 30 years. As Executive VP of Engineering & Service Delivery at TSRI, Roger has unique insights on the HUD project. He sat down to share them in an interview with GovCIO as part of their Partner Spotlight.

In a short chat, he shares how the TSRI-GovCIO team overcame the challenges not only of modernizing a nationally mission-critical system at risk of obsolescence, but also how to deal with the presence of dynamic SQL data in the legacy application logic.

Get the story straight from Roger in his interview with GovCIO.

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!

The U.S. Air Force uses the Integrated Logistics System – Supply (ILS-S), of which the Standard Base Supply System (SBSS) is a major part, as a mainstay of their supply chain. The SBSS program includes over 1.5 million lines of COBOL, as well as smaller numbers of C and Assembly, all of which are to be transformed into Java. 

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. 

Using automation to modernize mainframe applications will bring a codebase to today’s common coding standards and architectures. But in many cases, modernization to an application’s functional equivalent isn’t always enough. Organizations can do more to make their modern code more efficient and readable. By building refactoring phases into their modernization projects, organizations can eliminate the Pandora’s box of dead or non-functional code that many developers don’t want to open, especially if it contains elements that just don’t work.

Using TSRI’s automated refactoring engine, remediation was complete in an hour.

What is Refactoring and How is it Used?

Refactoring, by definition, is an iterative process that automatically identifies and remediates pattern-based issues throughout a modernized application’s codebase. For example, unreferenced variables or unnecessary redundant snippets could exist throughout the application. This scan, known as dead/redundant code refactoring, will find repetitions of any of this unusable code to flag, then remove it from the codebase. One of TSRI’s current projects found 25,000 instances of a similar issue that would have required 15 minutes of manual remediation per instance—not including the inevitable introduction of human error that would require further remediation. The number of development hours would take more than a year for a single developer to complete.

Using TSRI’s automated refactoring engine, however, remediation was complete in an hour.

Calling refactoring its own post-modernization phase is, in some ways, misleading. Refactoring typically occurs all the way through an automated mainframe transformation. As an example, in a typical COBOL or PL/1 mainframe modernization, TSRI would refactor the code from a monolithic application to a multi-tier application, with Java or C# handling back-end logic, a relational database layer through a Database Access Object (DAO) layer, and the user interface (screens) modernized in a web-based format. Believe it or not, many legacy applications still run on 3270 green-screens or other terminals, like in the graphic below.

Once the automated modernization of the legacy application is complete, the application has become a functionally equivalent, like-for-like system. However, any deprecated code, functions that may have never worked as planned, or routines that were written but never implemented will still exist. A process written in perhaps 1981—or even 1961—may have taken far more code to execute than a simple microservice could handle today.

Situations like this are where refactoring becomes indispensable.

Where to begin?

Before a formal refactoring process can begin, it’s important to understand your goals and objectives, such as performance, quality, cybersecurity, and maintainability. This will typically mean multiple workshops to define which areas of the modernized codebase need attention and the best candidates for refactoring, based upon the defined goals. These refactorings will either be semi-automated (fully automated with some human input) or custom written (based upon feedback from code scanners or subject-matter experts.)

The refactoring workshops can reveal many different candidates for refactoring:

• Maintainability: By removing or remediating bugs, dead or orphaned code, or any other anomalies the codebase can be reduced by as much as one third while pointing developers in the direction of any bugs in need of remediation.
•  
• Readability: Renaming obscure functions or variables for a modern developer to fit within naming conventions that are both understandable and within the context of the code’s functionality.
•  
• Security: Third-party tools such as Fortify and CAST can be utilized to find vulnerabilities, but once found they need to be remediated through creation of refactoring rules.
•  
• Performance: Adding reusable microservices or RESTful endpoints to connect to other applications in the cloud can greatly improve the efficiency of the application, as can functionality that enables multiple services to run in parallel rather than sequentially.

What are the Challenges?

• Challenge 1: One reason refactoring must be an iterative process is that some functionality can change with each pass. Occasionally, those changes will introduce bugs to the application. However, each automated iteration will go though regression testing, then refactored again to remediate those bugs prior to the application returning to a production environment.
•  
• Challenge 2: The legacy architecture itself may pose challenges. On a mainframe, if a COBOL application needs to access data, it will call on the entire database and cycle through until it finds the records it needs. Within a mainframe architecture this can be done quickly. But if a cloud-based application needs to call a single data record out of millions or billions from halfway across the world (on cloud servers), the round trip of checking each record becomes far less efficient—and, in turn, slower. By refactoring the database, the calls can go directly to the relevant records and ignore everything else that exists in the database.
•  
• Challenge 3: Not every modernization and refactoring exercise meets an organization’s quality requirements. For example, the codebase for a platform that runs military defense systems is not just complex, it’s mission critical. Armed forces will set a minimum quality standard that any transformation must meet. Oftentimes these standards can only be achieved through refactoring. A third-party tool like SonarQube in conjunction with an automated toolset like TSRI’s JANUS Studio^® can be utilized to discover and point to solutions for refactoring to reach and exceed the required quality gate.
•  

In conclusion, while an automated modernization will quickly and accurately transform legacy mainframe applications to a modern, functionally equivalent, cloud-based or hybrid architecture, refactoring will make the application durable and reliable into the future.

--

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!

A $39 billion clothing retailer with 4,300 stores worldwide sought to modernize its suite of mainframe COBOL supply chain applications. These applications supported the client’s unique business process, which provided them with a major competitive advantage and fueled years of unprecedented growth. Today, the clients business logic was preserved and their services are hosted on Azure with data integration directly through service bus queues and scheduling handled via Logic Apps.

Customer:  Retail Client Source & Target Language: COBOL to C# Lines of Code: 86,000 Duration:  3 months Services: Code Transformation, Automated Refactoring, Testing and Implementation Support, Transformation Blueprint®

One of the largest Japanese Car Manufactures now uses TSRI’s modernization methods to increase efficiency in their manufacturing systems. With the help of systems integrator Comture Corporation, TSRI was able to successfully transform 120k lines of COBOL to Java, in a three-week time-period, with over 99% automation levels. 

Customer & Integrator: Comture Car Manufacturer Source & Target Language: COBOL to Java Lines of Code: 120,000 Duration:  1 month Services: Code Transformation from Multiple Legacy Languages, Automated Refactoring, Installation and Testing Support, Transformation Blueprint®​