The purpose of this blog is to briefly discuss legacy IBM mid-range server application software that is still in operation, and its users still need help with documentation, programming, and modernization.
Disclaimer: IBM i is an operating system. iSeries and AS400 are servers. I use these terms interchangeably to make it easier for folks to find the information they are seeking on the internet.
Legacy Applications Are Still Active…And VERY Useful
Despite the emphasis on new technology and modernization of legacy applications, surprisingly there are still businesses that manage their operations on custom software that was developed in the 1980’s and the 1990’s.
Legacy Software From System/36 And Early AS400 Days
This is not just isolated to small businesses that still run on the System/36 (yes, there are still many companies that run variations of 5360, 5362, 9402-236, 9402-436 and System/36 environments on IBM i servers). In fact, I have encountered a number of larger businesses, even divisions of Fortune 500 companies, that still rely on this legacy software.
How come?
Why The Legacy Software Is Still With Us
While many IT experts I have spoken to might think systems can easily be replaced by low-cost accounting software like QuickBooks, popular client-server software or even industry-specific software, these legacy systems incorporate the “unique magic” that makes their owner’s business work smoothly.
We have a number of such clients.
For example, one client has software to track unique wood treatment processes for their offerings that include trusses, telephone poles, railroad ties, and bridges.
We have a Florida client who has software customized to handle the sale of products by route for convenience stores in their region.
We have another Pennsylvania client that has created software for import and resale flowers. As you may imagine, this is very unique software to get the flowers to the store with enough time for sale. (Flowers are perishable).
Another example is a Kentucky company that makes blended Vodka and requires specialized software to track vat ID’s by date for blending the various ingredients to make and age their libations.
In short, these are software solutions developed for very specific needs. There are NO off-the-shelf solutions for these unique needs.
I have also seen an increasing number of these special custom systems within Fortune 500 companies; smaller companies that have been purchased in the last 10 years that still use their legacy software. Despite being told they will be moving to SAP or Oracle, I am here to tell you that ain’t gonna happen because these special niche companies cannot be satisfied with SAP or Oracle. (We have sat on the sidelines over the last 15 years and watched companies spend $5 million to $20 million and more with no end in sight to force fit unique legacy systems into SAP or Oracle.)
If You Have Legacy Software Like This, You May Need Help To Give It New Life
The trend I now sense with users of legacy software like this, is that their programmers are going away. They have retired, will retire or have passed on.
Many of the custom solutions use System/36 programming techniques or third-party software tools. Commonly, these custom solutions were not properly documented. Perhaps there are basic use instructions; just not detailed records of files, records and programming instructions.
So what?
What To Do If Your Custom Software Is Not Well Documented?
Poorly documented software has several issues:
1) If it breaks, can you find someone to fix it if they do not understand what you have?
2) If you do not fully understand your software, how can you find a replacement?
3) If you do not fully understand your software, how can you migrate to a replacement system?
4) If you do not fully understand your software, how can you continue to adapt it to the unique characteristics that make your business work?
You Can Contact Us For Help
If you are aware that you have legacy System/36 or AS400 software, we still have the expertise on hand that knows how to decipher, program, and enhance these variations of programming.
This is important to know.
We are currently working with several clients that have System/36 legacy software to get it documented and brought forward to run native on a supported version of the IBM i operating system.
In doing so, we can now move these clients from legacy servers (System/36 and AS400), from operating systems that are no longer supported (SSP, OS400 V4R4, etc.) to supported versions of IBM hardware and i OS.
Further, as we document these legacy systems, our clients have a better understanding of the software and its related nuances. This is very helpful for planning either software enhancements or to prepare to better evaluate replacement software options.
Generally speaking, most of these clients with legacy software continue to use their custom solutions because it is far less expensive to enhance a system that works well than find a replacement.
Need Help With Your Legacy Software?
You can email me at blosey@source-data.com or call me at (714) 593-0387.
Leave a Reply