Legacy IBM i (iSeries/AS400) Application? Get Something To Replace It Or Modernize What You Have?

The purpose of this blog is to discuss factors that companies should consider before they decide to leave the IBM i (iSeries/AS400). I confess that I have a bias towards the IBM i platform. And after 2 decades I am astounded by the number of bad choices and unfulfilled promises made by the IBM i replacements. In most cases I have seen, the transition took way longer, cost a lot more (staggering how much more money it costs), and never worked as promised.

Disclaimer: IBM i is an operating system. iSeries and AS400 are server names. I use these terms interchangeably to make it easy for IBM user to research these topics on the web.

I have had several in depth conversations with legacy IBM i users in the last several weeks.

With the aging of IBM i professionals, many are concerned about the future of their applications.

Frequently I hear of companies that have been commanded to move to prominent Windows, UNIX or Linux based application software. What is alarming is that no in-depth analysis has been done to determine how good the fit is, what kind of resources will be needed for a successful implementation and the true nature of ongoing support costs.

In such cases, I expect the “2-year Implementation Plan” will take longer…MUCH longer. Cost far more than was ever budgeted. And does not deliver as promised.

I also expect that those who really know how things work will have retired or moved on rather than stay on another failed implementation.

That is what I have been witness to for close to 2 decades of users moving off IBM i.

Interestingly, I have spoken recently to some smart executives that understand the unique aspects of what makes their niche business successful and how well their legacy IBM i applications fit their specific needs.

In these cases, I have urged these businesses to:

1)     Document thoroughly their legacy systems so future developers can understand how to successfully make changes and enhancements to the core system, and

2)     Modernize their system.

This is not sentimental thinking on my part about the “good old days of AS400.”

Hardly.

I made these suggestions after listening carefully to the nature of their operation and how their companies uniquely capitalize on their niches. As they described their business I knew of nothing that was a good fit.

These businesses developed custom software because 20-30 years ago they could not find a fit from standard distribution or manufacturing software.

And, they still cannot find software to easily adapt to their niches.

Over the years, these IT teams refined these custom systems to better support their niche needs and adapt to the changing market. They have wonderful solutions that easily fit the business.

When we look at the options of moving to different software on different platforms, it becomes real evident that it will be far less expensive as well as less disruptive to the operation to document their current system for the future than to switch.

It is also far more cost-effective for new programmers to learn RPG as well as modernization tools for future customization. (I have read many cases of programmers that learned RPG in 4 months and marveled at its ease for programming business applications compared to Java, C, PHP and others. Yes, RPG can be learned.)

If you are facing a similar dilemma – move off the IBM i to a new software solution or stay with what you have – I encourage you to do your research to understand:

1)     the true cost to switch, as well as

2)     a fair and accurate assessment to document what you have and how to support it in the next 1-2 decades

If you conclude that sustaining your legacy system is best, be prepared to do thorough research to make your case. Include a solid ROI.

Insist the nay-sayers you may confront to also do thorough research and ROI to support their point of view.