- DescribeYour clerk explains the job“When a PO comes in, I open option 1 and key each line.”
- Learn and testThe agent finds the screensIt maps the fields on ORD100 and checks a test run against the clerk's.
- RunIt does the work, many at onceFixed steps repeat exactly, and on a credit hold it asks a person.
Damco's Agent 400 works your AS/400 like your best user It keys the work on your green screens, under every rule your RPG enforces
Session A · AS400PRD · [24 x 80]
FileEditViewCommunicationActionsWindowHelp
ORD100 Order Entry 10/23/26
AGT400OD 09:14:05
Type information, press Enter.
Customer . . . . . . . HALV-0042_ Halvorsen Supply Co.
Ship to . . . . . . . DOCK 3____ Newark, NJ
Customer PO . . . . . 88213_____
Requested date . . . . 10/27/26
Ln Item Description Qty Price
1 HX-2201 Hex bolt M8 x 40 12 18.40
2 HX-2209 Hex bolt M10 x 60 4 22.10
3 HX-3150 Flat washer M8 20 6.75
4 HX-2291 Hex bolt M8 x 45 10 19.20
More...
F3=Exit F4=Prompt F5=Refresh F10=Lines F12=Cancel
Order 4471209 created.
MA*a24/002
Connected to AS400PRD on port 992 (TLS)Signed on as AGT400OD
# order-deskHalvorsen Supply3 people · 1 agent
Maria Ortiz
Enter this purchase order and send me the order number.
PO-88213.pdf214 KB · 7 linesAgent 400AI agent
Ran on ORD1004 steps · 29s
- Read PO-88213.pdf, 7 lines
- Opened option 1, order entry
- Keyed the header and 7 lines
- Passed every screen check
Order 4471209 is in, 7 lines to Dock 3. Line 4 was discontinued, so I used HX-2291, the replacement your system suggested.
Email the confirmationOpen the orderMessage Agent 400
Start with the work that begins in a document Most AS/400 keying copies something from a PO, an email or a spreadsheet
Enter orders from purchase ordersIt keys the header and every line, then sends back the order number.
Apply policy changes from broker emailsIt makes the change on the policy screens and confirms it to the broker.
Answer status questions in seconds“Has order 4471209 shipped?” is read off the live screens.
Run bulk updates and list what failedPrice changes run across many records at once, with every exception listed.
Describe a task once, and the agent learns it It finds the screens, tests the steps, and keeps the task as a skill
First your team asks the agent instead of the screen Then you see what runs most and move it to APIs, without retraining anyone
How RapidIT proves the new code against the oldYour peopleOrder desk, 10 people
Agent 400AI agentEvery session logged
Green screensORD100 · CUS200 · PRC110
RPG programs and DB2Every check still runs
Now: your team asks the agent
It keys the work through every check a person goes through, and logs each session.
- Your team stops keying the tasks it learns
- You see which programs carry the load
- The busiest tasks run on APIs
Screens 100%
IllustratedEvery session shows you what to modernize next It ranks your busiest screens, so the first API goes where work piles up
ORD100Order entryORD300Order statusPRC110Price listsCUS200CustomersINV300InventoryBIL400InvoicesPUR200PurchasingRPT900ReportsVND050VendorsACC700Year-endUSR010User adminARC020ArchiveAgent 400 recommendsAI agent
- Order entryTen people key it 400 times a week. Build its API first.
- Price listsThe slowest run, at six minutes each. Build it next.
- Year-endIt runs once a year and rarely changes. Leave it on RPG.
Bring us one task your team keys every day
We'll show the agent learning it on a test session, and what your usage map shows.