The build · AS/400 & legacy modernisation
Deep in the systems most firms won’t touch.
IBM i, RPG and CL still run core operations at banks, credit unions, insurers and collections firms that have no intention of ripping them out this decade — and have a shrinking pool of people who can actually work in them. That’s a specialisation, not a legacy problem to apologise for. We work with these systems two ways: bring them under modern engineering discipline where they stand, or move them off the platform entirely.
01
Two paths, same platform
Modernise in place, or move off it. Not both half-done.
Most engagements need one of these, not a blend — knowing which one before you start is half the scoping work.
Bring it under discipline
The core stays on IBM i. What changes is whether it’s tested, monitored and understood the way a modern system would be — real test automation across the RPG core and whatever .NET or web layers sit around it.
Port it off entirely
Business logic re-implemented on .NET or Java, with the AS/400 domain model translated deliberately rather than transliterated line by line — because a literal RPG-to-Java port just moves the same problems into a language with more ceremony.
02
What this covers
Five sub-capabilities across both paths.
AS/400 test orchestration
An RPGUnit-based orchestrator running native on IBM i, so business logic gets tested where it actually executes, not in a simulated environment.
Green-screen automation
A tn5250j Java driver automating the terminal screens that still run daily operations at institutions with no plan to replace them this decade.
Modern layer testing
Playwright covering the .NET and web layers that sit alongside the legacy core — one discipline across both halves of a hybrid system.
Unified reporting
Allure aggregating results across RPG, screen-automation and web test suites into one report, instead of three tools reconciled by hand.
Porting to .NET or Java
Full migration off IBM i when that’s the actual goal — re-modelling the domain first, the same ontology-first discipline used everywhere else on this site, so the ported system is legible rather than an RPG program wearing a new syntax.
03
The stack
Built from real platform depth.
RPG · CL, native on IBM i
DB2 for i
RPGUnit for native business-logic testing
tn5250j (Java) driving terminal sessions
Playwright for .NET and web
.NET or Java, chosen against the client’s existing estate
04
Status, stated plainly
Capability built. First engagement in progress.
This isn’t hypothetical work — the architecture above has been specified in real technical depth, including against a live prospect’s environment. What hasn’t happened yet is production delivery, so we’re not publishing a case study until there’s a real one to publish, in the same format as every other case study on this site: named architecture, real numbers, what happened after.
Next