IBM i / iSeries / AS/400 services.
Same machine, four decades of name changes — and still the system of record for a surprising amount of banking, insurance, distribution, and manufacturing. We speak the platform fluently: RPG, CL, COBOL, Db2 for i, journaling, work management, and the open source you can run alongside it.
- ▸ IBM i 7.3, 7.4, 7.5
- ▸ Power 9, Power 10
- ▸ PASE (AIX runtime on IBM i)
- ▸ ACS, RDi, VS Code
The platform that quietly runs the business.
AS/400, iSeries, System i, IBM i — same machine, different naming generations. It's still the system of record for a surprising slice of banking, insurance, distribution, and manufacturing, and the engineering needed to keep it that way isn't going to come from a Power-shaped gap on someone's LinkedIn page.
We modernise without insulting the platform. That means exposing Db2 for i over REST instead of putting an ODBC connection on the internet, refactoring OPM RPG to ILE where it actually pays back, replacing the 5250 screens that genuinely cost the business money, and bringing in Node.js, Python, and Git on PASE alongside the green screens that still earn their keep.
Capabilities
RPG and ILE modernisation
- ▸RPG III → RPG IV → Free-Form modernisation
- ▸OPM to ILE conversion with realistic scoping
- ▸Service programs, modules, and binder language hygiene
- ▸Code analysis with ARCAD, X-Analysis, or open-source equivalents
Db2 for i and data access
- ▸Db2 for i exposure via REST (IBM i Services, integrated web services)
- ▸SOAP and REST stored-procedure wrappers
- ▸Db2 Web Query, embedded SQL, and SQE optimiser tuning
- ▸Modern data access patterns from .NET, Java, Node.js, and Python
5250 modernisation
- ▸Honest assessment of which 5250 screens are worth replacing
- ▸Web front-ends in React or modern frameworks, RPG back-ends preserved
- ▸Screen-scrape decommissioning and clean API replacements
- ▸Mobile and tablet front-ends for warehouse, sales, and field workflows
Open source on IBM i
- ▸Node.js, Python, and Git running natively on PASE
- ▸VS Code and Code for IBM i developer setups
- ▸ACS (Access Client Solutions) configuration and shipping
- ▸RPMs, yum, and dependency hygiene on IBM i
Work management and HA/DR
- ▸Subsystem design, job queue sizing, and routing entries
- ▸Journaling strategy and remote journaling for HA
- ▸PowerHA SystemMirror reviews and runbook authoring
- ▸Mimix (Precisely) configuration and switchover testing
Familiar situations.
- ▸The team that originally wrote the RPG retired and you'd like the code mapped, documented, and made changeable before something breaks.
- ▸Db2 for i needs to be exposed via REST for a new mobile app but you don't want to put the AS/400 directly on the internet.
- ▸Free-form RPG looks attractive but you've inherited 500K lines of fixed-form RPG IV and need a path that doesn't involve a wholesale rewrite.
- ▸5250 modernisation kicked off with high hopes and stalled — too ambitious in scope, not enough payback per screen.
- ▸Your HA/DR runbook hasn't been tested in years and you'd like a quiet review before the auditor asks.
IBM i estate worth a conversation?
Tell us about the platform — what it runs, what it's in the way of, what you wish you could do with it.
Get in touch →