IBM i / AS400 support
Keep the system that still runs the business supportable.
Whether you call it AS400, iSeries, System i, or IBM i, Treo provides the RPG programming, administration, integration, and modernization support that keeps IBM Midrange environments running, connected, and practical to evolve.
| Object | Work | Status |
|---|---|---|
| RPGLE | Order logic review | Mapped |
| DB2 | Index and query check | Stable |
| JOBQ | Batch ownership | Document |
| API | Modern reporting feed | Ready |
The goal is not to replace working business logic by default. The goal is to know what runs the business, reduce support risk, and connect the platform where the business needs it.
Why support becomes urgent
The platform still works. The staffing model around it often does not.
Many organizations still depend on IBM i because it runs critical business processes reliably and has been shaped around their operations over many years. The platform itself is not usually the problem.
The pressure comes from the environment around it: staff retire, newer systems need to connect, interfaces feel dated, and fewer people every year have the depth to support RPG, DB2 for i, jobs, and integrations confidently.
IBM i support today is less about defending the platform and more about keeping it practical, connected, and supportable as the rest of the business evolves.
Coverage
What Treo handles in IBM i environments
The scope depends on the environment, but the work usually falls into a small set of practical streams.
| Workstream | What it covers | When it matters |
|---|---|---|
| RPG and RPGLE programming | RPG III, RPG IV, RPGLE, CLP, CLLE, business logic changes, code review, and documentation. | Core applications still run the business but the code needs maintenance, enhancement, or knowledge capture. |
| System administration and DB2 for i | Platform configuration, DB2 for i management, jobs, monitoring, troubleshooting, access, and security settings. | The system is stable, but operational ownership, visibility, or routine administration needs to be strengthened. |
| Modernization and interface improvement | Web workflows, usability improvements, reporting, data access, automation, and practical user experience updates. | Green-screen or manual workflows create friction, but the underlying business logic still has value. |
| API development and integration | REST services, data exchange, Microsoft 365, ERP, cloud platform, and third-party system connectivity. | IBM i has become an island and other parts of the business need reliable access to its data or transactions. |
| ERP and business application support | Custom application support, Enmark Eniteo experience, report development, data extraction, and application troubleshooting. | The IBM i workload is tied directly to a production or operational application that needs steady support. |
| Continuity and knowledge transfer | Environment assessment, documentation, transition planning, support handover, and reduction of single-person dependency. | Critical knowledge is concentrated in one person or there is no clear plan for ongoing platform coverage. |
How the work moves
Support first. Then modernization with context.
The value is not just having IBM i skills available. It is knowing the order of operations so a stable platform does not get disrupted by a poorly understood change.
Understand the environment before making recommendations.
What applications are running? What RPG code is critical? Where is the knowledge concentrated? What integrations exist? The first step is a clear picture of what the platform does and where the risks are.
Make sure the platform is properly supported before changing anything.
Documentation, monitoring, access review, job ownership, and support coverage come before modernization when the environment has been running on institutional knowledge.
Connect the platform to what the business needs it to talk to.
Modern reporting, web applications, cloud systems, and other business platforms often need data from IBM i. Integration work connects the platform without disrupting what already works.
Improve the parts that create friction without replacing what still works.
Green-screen interfaces, manual processes, and dated workflows can be modernized practically. The goal is evolution, not a risky replacement of stable business logic.
Provide ongoing coverage so the platform does not depend on one person.
Steady RPG programming support, administration, and operational coverage reduce the continuity risk that comes from having critical platform knowledge concentrated in too few people.
Modernization stance
Do not replace working IBM i logic just to make it look modern.
Modernization is useful when it removes friction, improves access to data, reduces manual work, or helps the system integrate with the rest of the business. It is dangerous when it starts with the assumption that stable business logic must be thrown away.
Treo's approach is practical: preserve what is reliable, document what is fragile, and modernize the specific interfaces, integrations, and workflows that create business drag.
- KeepBusiness rules and RPG logic that still run correctly and carry operational value.
- ExposeData and transactions that need to serve reporting, cloud, ERP, or web workflows.
- ImproveInterfaces, manual steps, and support practices that make the platform harder to use or maintain.
- DocumentPrograms, jobs, dependencies, and tribal knowledge that should not live in one person's head.
Common questions
Questions organizations ask before bringing in IBM i help
Can you support RPG code that was written decades ago?
Yes. That is a core part of what Treo does on this platform. Many IBM i environments run RPG III and RPG IV code that has been in production for 20 or 30 years. Treo has the experience to work with legacy code, maintain it, and extend it when needed.
Do you recommend moving off IBM i?
Not automatically. If the platform is still running critical work reliably, the better path is usually to keep the business logic, modernize what creates friction, and improve connectivity. A full migration only makes sense when the business case is clear and the risks are understood.
What if our current IBM i person is retiring?
Treo can take over IBM i support when the person who knows the system is retiring, and this is one of the most common reasons organizations bring Treo in. Treo works alongside the outgoing person to capture knowledge, document the environment, and transition support so the platform does not become unsupported when they leave.
How does this connect to managed IT?
IBM i work usually sits alongside a broader managed IT relationship, where Treo handles both the platform and the surrounding environment, including users, Microsoft 365, security, and general infrastructure.
Need steadier support for an IBM i environment?
A conversation can clarify where support risk, modernization pressure, or integration needs are creating friction, and whether Treo is the right fit for your environment.