AS/400 · IBM i · iSeries

A modern interface for your AS/400 — without migrating off it

Green-screen 5250 sessions still run order entry, stock and invoicing in thousands of companies because they are fast and they are correct. The problem is not the machine — it is that every task is a menu number and a function key, and new staff need months. We put a modern web interface on top and leave IBM i exactly as it is.

TODAY — 5250 DISPLAY SESSION

ORDER ENTRY                        OE100
──────────────────────────────────────
CUSTOMER . . . : 10428
ITEM . . . . . : 40871
QTY  . . . . . : 2
WHSE . . . . . : 01
──────────────────────────────────────
F3=Exit  F4=Prompt  F6=Add  F12=Cancel
CPF4328: FIELD NOT VALID FOR THIS ORDER

Through the new interface

One customer page

Search by name, phone or number. Discount, terms, vehicles, open orders and history on a single screen.

Real search on items

Type part of a description instead of the exact item number, with live stock from the same files.

Plain answers

CPF codes are translated into a sentence a new hire can act on.

The order number comes from IBM i

Nothing is confirmed in the interface until the original program has answered.

What the day looks like today

Menu numbers and function keys

Every task is a path through numbered menus, and the same detail is typed again on the next screen.

Training takes months

The knowledge lives with the staff who have used the system for twenty years, not in documentation.

Replacing it is a huge project

A new ERP means rebuilding every integration, converting decades of data and risking the business stopping.

How the connection is made

Terminal sessions are the easy case

IBM i already speaks over a network session. A local agent logs in with the user's own profile, sends the exact keys and fields, and reads the response screen back.

Or the existing programs and APIs

Where you already have RPG service programs, stored procedures or a data queue, we call those instead of driving screens.

Your authority scheme is kept

Each user acts with their own IBM i profile and object authorities, so the journal still shows who did what.

Nothing is written behind the program's back

We never update files directly. The same validation and business rules the program has always enforced still run.

IBM i keeps being the source of truth. If you ever switch the new interface off, staff sit down at the same green screen as before — nothing to undo, nothing migrated.