Can AI agents automate IBM i 5250 Applications?
IBM · on-prem · terminal-applicationline-of-businesslegacy
Highly automatable today via two complementary paths: terminal automation of the 5250 screens (EHLLAPI-based activities in every major RPA suite) for transactions, and direct Db2 for i SQL access via ODBC/JDBC — now wrapped by IBM's official ibmi-mcp-server — for data. What is missing is any per-application API: business logic locked inside display files is reachable only through the screens or a modernization effort.
Best path today: rpa · Overall automatability: 8/10
Modalities
| Modality | Status | Detail |
|---|---|---|
| API | partial | odbcjdbcibm-i-user-profile coverage: partial · docs |
| SDK | yes | cjava official: yes |
| MCP | yes | verdict: official mcp-server-db2i · maintained: True |
| Integrations | yes | power_automate |
| CLI | no | |
| Extensibility | yes | ehllapiacs-hod-macros webhooks: False |
| Data access | export: csv, xlsx · import: csv, xlsx | |
| RPA / UI automation | good | terminal-5250uipathblue-prismautomation-anywhereibm-rpapower-automate-desktop The most mature RPA target class there is: fixed 24x80/27x132 field-formatted text screens, deterministic keyboard states, and a 40-year-old automation API (EHLLAPI) implemented by every major emulator. All major RPA vendors ship dedicated terminal activities with IBM 5250 support. Caveat: IBM's own ACS 5250 emulator needs extra setup for EHLLAPI and does not provide the old HACL autECL COM objects; HOD macro scripting is its native path.
|
| Computer use | unknown | measured verdicts only — "unknown" means not yet probed by us |
Scores
| api | mcp | rpa | computer use | overall |
|---|---|---|---|---|
| 5 | 6 | 8 | — | 8 |
Evidence
| Fact | Tier | Source | Date |
|---|---|---|---|
modalities.rpa.vendor_support (UiPath Terminal activities, IBM 5250 + EHLLAPI emulators) | declared | source | 2026-08-15 |
modalities.rpa.vendor_support (Blue Prism mainframe integration via emulator COM APIs and HLLAPI) | declared | source | 2026-08-15 |
modalities.rpa.vendor_support (Automation Anywhere Terminal Emulator package, 3270/5250) | declared | source | 2026-08-15 |
modalities.rpa.vendor_support (IBM RPA connecting to emulators via HLLAPI) | declared | source | 2026-08-15 |
modalities.integrations.power_automate (terminal emulation actions, IBM 5250 host type, HLLAPI providers) | declared | source | 2026-08-15 |
modalities.sdk (EHLLAPI reference, Personal Communications Emulator Programming) | declared | source | 2026-08-15 |
modalities.extensibility.scripting (ACS 5250 macro scripting is HOD-based, differs from PCOMM) | declared | source | 2026-08-15 |
modalities.rpa.notes (EHLLAPI with the ACS emulator requires extra setup) | declared | source | 2026-08-15 |
modalities.rpa.notes (ACS 5250 provides no HACL autECL automation objects) | declared | source | 2026-08-15 |
modalities.api (Db2 for i access through ODBC/JDBC client interfaces) | declared | source | 2026-08-15 |
modalities.api + modalities.data_access (ACS Windows Application Package: ODBC, OLEDB, ADO.NET providers) | declared | source | 2026-08-15 |
modalities.sdk.languages (IBM Toolbox for Java / JTOpen, active) | scraped | source | 2026-08-15 |
modalities.mcp.first_party | scraped | source | 2026-08-15 |
modalities.mcp.first_party (IBM's own AI-for-IBM-i guidance) | declared | source | 2026-08-15 |
modalities.mcp.third_party | scraped | source | 2026-08-15 |
modalities.cli (community scriptable tn5250 client, p5250) | community | source | 2026-08-15 |
Last verified 2026-08-15 · volatility low · JSON record