Mainframe Integration Myth #5

by | Nov 17, 2021

We recently tackled the viability of using screen scraping as an integration approach. Now we’re wrapping up our Myth series with one of the most common misconceptions.

#5 – Robust integrations require a vast and complex set of tools

Legacy technology – and really, technology in general – comes with added complexity. In the world of legacy tech, there’s a myth that a complex set of tools is needed to accomplish successful integration. Some tools are created by taking existing tools joined with “virtual duct tape” to create a “platform” for customers to achieve their integration goals.

Often, the tools being pushed are just a repurposing of an outdated tech that adds complexity to an already intricate environment – something most users are trying to avoid. No one wants to invest more time and resources into configuring an old platform to work with the business application. The most common complaint we hear from management teams about the mainframe is that it slows down innovation. The systems engineers, application designers and programmers working in the mainframe tend to be risk averse and operate out of caution when testing concepts for fear of mistakes that could bring the entire system down.

A happy medium approach that can satisfy both groups is having a single platform that simplifies processes and reduces the timeframe in which integration can be achieved. The less tools needed, and the more processes can be run off the mainframe – especially for proof of concept – the better. Using one comprehensive platform provides an advantage for more innovation and increases buy in from upper management.