Service · Software development

Replace your AS/400 with a modern platform.

Somewhere in your organisation, an AS/400 (now IBM i on Power Systems) is still running, with RPG programs driving inventory management, production planning or logistics on a DB2 for i database. Reliable, fast at batch processing, and running undisturbed for decades. The problem isn't the power of the system, but what has happened around it: a green-screen interface that no longer fits how people work, a shrinking group who still understand the RPG code, and business logic that is documented nowhere outside the code. We take stock of what is there and build a modern layer around it, or replace the system in phases, one business process at a time.

The system isn't the risk, the knowledge around it is.

An AS/400 that was installed thirty years ago and still runs the nightly processing flawlessly is not a bad system. IBM i, as the platform has been called since AS/400 and iSeries were renamed, is known for its stability and speed in batch processing. Wholesalers, manufacturers and logistics service providers build their core processes on it, often without ever having suffered a major outage. That is exactly why it has stayed in place: it works, and nobody wants to touch a working system.

The risks have emerged elsewhere. The 5250 green screens can be operated at lightning speed with the keyboard, but they no longer match what new employees are used to and offer no route to mobile or web. RPG developers, especially those who can still read RPG II or RPG III, are scarce and, on average, older than in almost any other technology. And under the bonnet sit thirty years of business rules that were never documented separately, exist only as code, and sometimes only as knowledge in the head of one person who is about to retire.

Our approach follows the same principle we use when we replace legacy software and modernise legacy software more broadly: first understand what is there, and only then decide what happens. For an AS/400, that means an inventory of the RPG programs and the DB2 for i data structure before we choose between a modern layer around it or a complete rebuild.

How we approach AS/400 projects.

Inventory first
Mapping the RPG programs and DB2 for i structure before we build
Layer or rebuild
A modern web/API layer on the existing core, or a complete rebuild
Process by process
One business process at a time, with the AS/400 still running everything else
Data ownership
Full migration from DB2 for i with validation and a fallback option

Three ways to tackle an AS/400.

Which route fits depends on how stable the RPG code still is, how many external systems integrate with it, and how much of the business logic is already known outside the system itself. The approaches below together cover the vast majority of the AS/400 projects we get involved in.

Approach 01

Taking inventory of RPG and DB2 for i

The start of every AS/400 project

We map out which RPG programs are running, in which variant (RPG II, RPG III or the more modern ILE RPG), how the DB2 for i database is structured, which batch jobs run overnight and which systems integrate with the AS/400. We combine code analysis with conversations with day-to-day users, because much of the business logic cannot be found in the code itself. We never skip this step, not even under time pressure.

RPG code analysisDB2 for i structureMapping batch jobsInventory of integrationsUser interviews
Approach 02

A modern web/API layer on the existing core

When the RPG logic is still reliable

If the business logic and the data still work well and the problem lies mainly with the interface and integration options, we build a layer that communicates with the existing RPG programs and DB2 for i: via direct database access, program calls to RPG modules, or a contemporary shell over the 5250 screens. Employees get a web interface, external systems get an API, and the proven core logic is left untouched. This is often also a good stepping stone towards a later rebuild.

API on DB2 for iProgram callsScreen modernisationWeb/mobile accessLow-risk route
Approach 03

Phased migration per business process

When full replacement is needed

If the RPG logic itself is outdated or opaque, or the AS/400 relies on an ISV package approaching end of life, we build a successor on a modern stack. Never in one go, but process by process: for example, stock administration first, then order processing, then production planning. Each process runs in parallel with the AS/400 before it goes live, with data migration from DB2 for i and a validation step that compares old and new.

Process by processRunning in parallelDB2 for i data migrationValidation stepPhased cut-over

What you're left with.

A modern system in production, or a modern layer on an AS/400 that stays in place for as long as it delivers value, and an organisation that no longer depends on one person who still understands the RPG code.

Production + staging

Two environments for the new layer or the new system, in your own cloud or hosted by us.

Documented business logic

The rules that were hidden in RPG, now explicitly documented and transferable.

Migration report

Which data from DB2 for i was migrated, which validations were carried out, and where deviations occurred.

Decommissioning plan

How and when the AS/400 is decommissioned process by process, and which archive remains.

Management (optional)

Monitoring, backups, security patches and further development under a maintenance contract.

When an AS/400 project becomes unavoidable.

Four patterns in which postponing is no longer the safest choice, and in which we are usually invited to carry out an assessment first, before anything concrete is planned.

Knowledge

The RPG specialist is retiring

One person, either in-house or at a small external firm, still really knows the RPG code well. New RPG developers are scarce, and getting someone up to speed on undocumented code often takes more time than building a modern layer or rebuilding.

Interface

The green screen no longer suits new employees

New employees don't know the 5250 terminal and need a long onboarding period. There is no mobile access, no way to log in remotely, and every expansion of the user group runs into the screen's learning curve.

Integration

Integrating with modern systems is getting harder and harder

A new webshop, a modern WMS or a CRM package expects real-time APIs. The AS/400 has traditionally communicated through nightly batch exports and manual file exchange, so every new integration becomes a separate custom project.

Ecosystem

An ISV package on the AS/400 is heading towards end-of-life

Many AS/400 environments run not only on in-house RPG, but also on a package from an external vendor. If that vendor stops developing it, taking control yourself becomes a pressing question.

Risks we address explicitly.

An AS/400 project touches core processes that have often run undisturbed for decades. Four risk categories we identify up front in every project.

Data

Data loss when migrating from DB2 for i

Fields that have informally come to be used for something other than their original purpose, keys that no longer hold everywhere, historical records that the old system tolerated. We carry out a data audit up front and build a validation step that compares every migration against the source, with a fallback position after the switchover.

Logic

Hidden business rules in the RPG code

An exception rule for a single customer, a correction that was once meant to be temporary and stayed in place, a nightly job that nobody can explain any more but that turns out to be necessary. We interview every user group and run old and new in parallel, so that deviations become visible before a process is switched over.

Continuity

Disruption of batch processing and core processes

Inventory, production and logistics cannot simply stand still. We migrate process by process, schedule switchovers for quiet periods in the operation and keep a rollback scenario ready until a process is running stably.

Adoption

Resistance from experienced 5250 users

Operators who use the green screen blindfolded initially find a mouse-driven interface slower, even when it objectively makes more possible. We involve these users from the start, respect old keyboard shortcuts wherever possible and support the transition with targeted training.

How an AS/400 project works.

01Introduction→ 02Assessment→ 03Build & migration→ 04Cut-over & maintenance
Step 01

Introduction

Which processes run on the AS/400, who still knows the RPG code, and which pain point is most acute. A no-obligation conversation with IT and operations.

Step 02

Discovery

We analyse the RPG programs and the DB2 for i structure, interview users and choose, per process, between a modern layer and a full rebuild.

Step 03

Build & data migration

Working modules in sprints, running in parallel alongside the AS/400, and a validation step for the migration from DB2 for i, process by process.

Step 04

Cut-over & decommissioning

Phased transition per business process, fallback position ready, and the AS/400 emptied once all processes have been taken over.

From AS/400, RPG and DB2 for i to a modern stack.

We come across AS/400 environments alongside other legacy stacks, and the approach overlaps: first understand what is there, then choose between a modern layer or a full replacement. We follow the same pattern for COBOL systems and FoxPro applications, and the broader overview is under software development.

Starting point
RPG II / IIIILE RPG (RPG IV)CLDB2 for i5250 / green screenQuery/400
Target stack, frontend and backend
Next.jsAstroReactNode.jsPython.NET 8PostgreSQL
Migration & integration
ODBC/JDBC to DB2 for iProgram call APIsScreen modernisationETL pipelinesAnti-corruption layerDocker

Frequently asked questions.

Does our AS/400 system have to be replaced in one go?
No. We migrate process by process, starting with the process that has the fewest integrations and the best documentation. The AS/400 keeps running for anything not yet migrated, so your operations never depend on one big switchover.
Can the AS/400 keep running while we build a modern layer around it?
Yes, and often that is the first step. We build a web or API layer that talks to the existing RPG programs and DB2 for i, so users and external systems get a modern interface while the core logic stays intact. That layer can be temporary or permanent.
What happens to the data in DB2 for i?
First we take stock of files, fields and keys, and which data is still actively used versus archived. Then we migrate to a modern database, with a validation step against the source. The AS/400 remains available read-only as a fallback.
We no longer have an RPG developer in-house. Is that a problem?
That is the rule rather than the exception. We reconstruct the business logic through code analysis, user interviews and observing the system in real use. Not everything is written down, so we run the new system in parallel for a while to surface any discrepancies.
Is a green-screen interface a problem in itself?
Not necessarily. A 5250 screen is often fast for experienced users, and the logic behind it may be perfectly sound. The problem usually lies elsewhere: new staff, no mobile access, or systems that cannot integrate in real time. We decide case by case whether a new front end is enough.
How long does it take to replace or modernise an AS/400?
That depends on the number of processes, the documentation and the number of integrations. Because we migrate process by process, you will see a process in production after the initial inventory and the first sprints. We only give a timeline once that inventory is done.
What decides whether we build a modern layer or rebuild the system entirely?
Mainly how stable the RPG code still is, how many systems depend on it, and whether the pain is in the interface or in the logic as well. If the core logic works reliably, a layer is often enough. If the logic itself is outdated or tied to a package that is being discontinued, a rebuild is the obvious choice.
Will we own the new software and data?
Yes, entirely. Code, infrastructure, documentation and credentials are put in your name, in an environment you manage yourself or that is handed over to you. The migrated data also remains yours, with a documented export format for any future migrations.

Talk to us about your AS/400.

A no-obligation introductory call of half an hour. We listen to which processes run on the system, where it is under strain and what has prompted you to look at it now, even if it turns out parts of the system can safely stay as they are.

Edit content