The system is opaque
Years of changes have made it hard to tell which parts are valuable and which parts should change.
SYSTEM/38 → AS/400 → IBM i
LEGACY IS NOT THE PAST. IT IS AN ASSET.
Repair legacy assets without breaking them—and carry them into the future.
“Replace it because it is old” is not a strategy. Neither is “never touch it because it still runs.”
I identify the value built into IBM i systems and help shape their next practical step.
A complete rebuild is right for some organizations. For others, preserving the business knowledge already embedded in their systems—and improving the right parts first—is faster, safer, and more rational.
BEFORE REPLACEMENT
Companies are often told, “AS/400 is old. Move to an open system.” Sometimes that is the right answer. But when migration itself becomes the goal, years of refined business logic may be rebuilt at enormous cost—with no guarantee that the work will become better.
Years of changes have made it hard to tell which parts are valuable and which parts should change.
Fewer engineers can read RPG, so even necessary changes begin to feel unsafe.
“Leave everything alone” or “replace everything” are not the only choices.
HISTORY ≠ OBSOLESCENCE
Ferrari has a long history, but it does not keep building yesterday’s cars unchanged. It preserves what matters while continually advancing performance, safety, and control technology.
The IBM AS/400 followed the same principle. The product introduced in 1988 did not stand still; its hardware, operating system, database, and development environment evolved into today’s IBM i.
A long history≠An obsolete product
The real question is not when it was born, but what it does today, what value it holds, and how it can keep evolving.
FACT SOURCE IBM | The AS/400
ONE INTEGRATED PLATFORM
IBM designs and delivers the processor, operating system, database, and development and operations environment as one platform.
Instead of assembling independent components and continually testing their compatibility, IBM i is designed to work as an integrated whole. That integration is one reason organizations can rely on it for decades.
FACT SOURCE IBM | IBM i/IBM | Db2 for i
MAKE THE MOST OF IT
Protecting a system and changing it are not opposites. Preserve today’s value while identifying what truly needs to evolve.
UNDERSTAND
Source code, databases, screens, reports, and operations: discover the real specification from the working system, not from documents alone.
IMPROVE
Understand the impact, verify the behavior, and keep the workplace running. Small changes can produce very large results.
CONNECT
Free-Form RPG, external integration, and AI: connect proven assets to new technology and the next generation of engineers.
WHAT I WORK WITH
I understand IBM i from the inside and connect it to technologies outside the platform. The work starts with a real operational problem.
RPG III, RPG IV, and ILE. I read the intent of long-lived code and change it safely for today’s requirements.
I improve correctness and performance by understanding data structures and access paths, including SQL and logical files.
Jobs, objects, libraries, security, and operations—problems are considered across the whole platform.
I uncover specifications and impact areas inside complex source and improve the system without stopping the business.
Modernization is not cosmetic rewriting. It should make the code maintainable and understandable to the next engineer.
Manual work, waiting, transcription, and repeated checks: I turn “that is just how it is” into a solvable problem.
DX is measured by whether the work actually improves—not by whether a new product was purchased.
I treat AI as a practical tool for research, analysis, verification, and documentation—not as magic.
ABOUT THE ENGINEER
From System/38 to AS/400 and IBM i. Names and coding styles change, but the essentials do not: understand the business, make it run correctly, and support the people who use it.
I neither chase every new technology nor cling to old technology. I respect why a system has lasted, then keep looking for a better way forward.
SELECTED RESULTS
I can read old IBM i assets.
I can repair them without breaking them.
And I can bridge them to Free-Form RPG.
NOTES FROM THE FIELD
Technology alone does not tell the whole story. These are real experiences: successes, mistakes, unexpected discoveries, and a little laughter.
In November 2019, we completed a white-blood-cell morphology classification PoC using IBM PowerAI Vision. Specialists saw its potential, but it never reached production. Old blog entries and public records now tell the fuller story.
It read about 400 million records and looked up master data dozens of times for each one—yet the AS/400 still finished in 30 minutes. Redesigning the data access cut that to 20–30 seconds.
SYSTEMS SHOULD AGE WELL.
Read before discarding. Understand the value before changing.
Make today’s assets a foundation for the future—not an obstacle to it.
Yoshiochin.com will keep growing from here.