What Is IBM AS400 Software? The Complete History, Releases, Languages, Models, Uses, and Famous Programs

Start here ... what IBM AS400 software really means

IBM AS400 software is not one simple product download. In most searches, the phrase means several things at once ... the historic AS/400 platform itself, the operating system now called IBM i, the business applications that run on it, and the tools used to develop, secure, modernize, back up, integrate, and manage it.

That mixed intent is why search results can confuse beginners and still feel obvious to longtime IBM i teams. This page takes the broad interpretation on purpose. AS400Software.com is dedicated to AS400 Software as a category, so the useful answer is the full ecosystem answer, not a one-line definition.

• AS400 history and lineage ... The naming and release timeline behind AS/400, iSeries, System i, and IBM i.
• IBM i ERP software ... The core business application layer behind finance, operations, and system-of-record workflows.
• IBM i software directory programs ... The tools and packages used to modernize, secure, automate, report on, and integrate IBM i environments.
• IBM AS/400 hardware ... The server, storage, terminal, console, and infrastructure side of the same platform story.

AS400 release date, original name, and lineage

IBM's release life cycle records Rel 1 as announced on June 21, 1988 and generally available on August 26, 1988. AS/400 stood for Application System/400, and it was IBM's business platform successor to System/36 and System/38 thinking.

Over time, the naming changed faster than the workload base did. Many businesses kept the same core applications through AS/400, AS/400e, iSeries, System i, i5/OS, and IBM i. That continuity is exactly why old and new terminology still overlap in live buyer searches.

• AS/400 history timeline ... The original market identity and the easiest way to understand where the software lineage began.
• AS/400e ... enhanced late-1990s branding tied to a more internet-aware era.
• iSeries ... The server-era branding that kept the same business lineage alive.
• System i ... The bridge period where IBM kept the platform intact while changing the surrounding branding.
• IBM i ... The current operating system name running on IBM Power hardware.

Hardware generations and representative model numbers

Any serious AS400 software discussion eventually becomes a hardware discussion because IBM i release support, licensing tiers, performance, storage options, and modernization paths all depend on the machine generation underneath.

A practical model-number view is more useful than pretending the platform never changed. The families below are representative rather than exhaustive, but they show how buyers move from remembered AS/400 names into current Power planning.

• 1988 launch systems ... The B10 and B20 base processors that introduced the AS/400 family.
• Classic 9402, 9404, and 9406 families ... Representative early AS/400 hardware still cited from memory by long-time administrators.
• AS/400e and iSeries families ... Systems such as the 170, 2xx, 5xx, 6xx, 7xx, and 270 class machines that carried the installed base forward.
• System i and i5 era servers ... Examples include 9406-520 and the broader 515, 520, 550, 570, and 595 generation.
• Modern Power servers ... Current hardware discussions usually revolve around Power S914, S922, S924, S1014, S1022, S1024, and newer Power 11 class systems such as S1112.

Why the platform felt different from generic servers

What made the platform different was integration. IBM paired the operating system, database, security model, runtime environment, and management experience more tightly than many competing server stacks.

That design is still why IBM i teams often talk about the whole stack as one operating environment instead of a loose pile of software. The business result was fewer moving pieces for core transactional workloads and unusually long application life.

• Backward compatibility protected older business applications
• Db2 for i lived inside the platform instead of being bolted on as a separate database product
• Operations, security, commands, and menu workflows were standardized across the system
• The platform emphasized connected business users, jobs, printers, and networks instead of one isolated application

IBM AS400 software release history and milestone improvements

If you want the software history, the cleanest way to read it is by milestone release families rather than by every PTF or resave. The list below tracks the base releases and the breakout improvements people still reference when they talk about IBM AS400 software evolution.

This is the practical buyer's version of the history ... what changed the software story, the integration story, or the modernization story at each stage.

• Rel 1 ... announced June 21, 1988 and available August 26, 1988. This was the original OS/400 era: integrated business computing, strong compatibility, and the foundation that made the AS/400 name stick.
• V2 and V3 releases ... early 1990s through 1996. These releases matured the platform for larger networks, broader client connectivity, stronger relational workload handling, and the growing client-server world.
• V4R1 through V4R5 ... 1997 through 2000. Internet, Java, web serving, and e-business expectations became much more important, and the software stack adapted to that shift instead of staying a closed midrange island.
• V5R1 through V5R4 ... 2001 through 2006. The iSeries generation emphasized consolidation, partitioning, storage growth, and broader integration with the rest of IBM's server strategy.
• IBM i 6.1 ... Announced January 29, 2008 ... the rename that moved the platform into the Power Systems era while preserving application continuity.
• IBM i 7.1 ... announced April 13, 2010. This release became a long-running base for many shops and extended the life of mature environments that needed stability first and modernization second.
• IBM i 7.2 ... announced April 28, 2014. IBM i kept moving toward newer infrastructure, SQL services, and integration patterns while customers still depended on decades of existing code.
• IBM i 7.3 ... announced April 12, 2016. A major long-life release for many IBM i estates, later extended by Technology Refreshes that carried newer hardware and security improvements forward.
• IBM i 7.4 support and compatibility ... Announced April 23, 2019 and generally available June 21, 2019, with long-tail compatibility that kept it heavily deployed into 2026.
• IBM i 7.5 ... announced May 3, 2022 and generally available May 10, 2022. This release continued the current modernization track and supports active cross-version planning around current Power hardware and availability tooling.
• IBM i 7.6 and the Power 11 era ... Announced April 8, 2025 and generally available April 18, 2025, with built-in MFA and Power 11 support that make the current platform story impossible to dismiss as legacy only.
• Technology Refresh and lifecycle planning ... On IBM i, meaningful software progress often arrives between major version jumps, so real release history always includes the TR stream too.

AS400 coding languages and why each one mattered

The language story is one of the biggest reasons AS400 software persisted. IBM i never depended on only one language, but RPG became the signature business language because it mapped so well to transaction-heavy work, reports, screens, and file-driven operations.

IBM documentation still frames the platform around CL, DDS, APIs, ILE languages, SQL, Java, and scripting languages such as Node.js, PHP, and Python. That mix explains why old code and new integration projects can coexist on the same system.

• RPG and ILE RPG ... The flagship IBM i business application language, still heavily used for ERP, order entry, inventory, finance, and custom workflow code.
• COBOL ... still present in long-lived commercial and financial workloads where logic stability mattered more than trendy tooling.
• CL ... the control language used for commands, job control, operational scripting, and system administration.
• DDS ... not a general-purpose language, but a long-important format for database, display, and printer file definitions.
• Db2 for i and SQL services ... Now central for querying, stored procedures, services, reporting, and modernization work.
• C and C++ ... used where lower-level control, APIs, utilities, or interoperability mattered.
• Java ... important for web, middleware, enterprise integration, and packaged application extensions.
• Open-source scripting on IBM i ... PHP, Python, and Node.js now sit beside RPG in many modern IBM i environments instead of replacing it outright.
• API integration and web services ... The bridge that lets mature IBM i applications feed web apps, mobile tools, analytics, EDI, and SaaS integrations.

Who still uses AS400 software today

Yes, AS400 software is still used today. The live question is not whether the platform exists but which companies still trust it enough to keep running orders, finance, manufacturing, and logistics on it.

The answer is usually companies with complex transaction-heavy operations and a long memory of what breaks when core systems change carelessly. IBM's current client stories still point to manufacturers, co-ops, logistics groups, and trucking-related operations ... the same kind of operational markets that have relied on IBM midrange systems for decades.

• Distributors that need dependable order, inventory, and fulfillment flow
• Manufacturers running planning, shop-floor, costing, and supply chain logic
• Warehouse-intensive businesses that depend on barcode, shipping, and replenishment software
• Transportation, dispatch, route, and service organizations with time-sensitive transaction workloads
• Midmarket firms that want one durable system of record instead of a fragile stack of loosely connected applications
• IBM i ISVs, MSPs, resellers, and modernization partners that build their businesses around the installed base

What IBM AS400 software is used for

The workloads are usually practical, not experimental. IBM AS400 software is used for the business functions that companies cannot afford to run loosely ... taking orders, moving inventory, billing customers, producing reports, scheduling operations, and keeping data consistent across departments.

In many organizations, the platform remains central because it still connects the most important transactions cleanly and reliably. That is why the software conversation often sounds more operational than glamorous.

• ERP and financial systems ... Still one of the core IBM i workload families.
• Order management, purchasing, and inventory control ... The operational backbone of many long-running IBM i environments.
• Distribution, warehouse, and shipping operations ... A major area where IBM i software still drives daily execution.
• Manufacturing planning and execution ... Usually tied to ERP and plant-floor process control inside the same business stack.
• EDI and trading partner management ... The integration layer that keeps customer, supplier, and logistics workflows moving.
• Reporting, queries, dashboards, and Db2 for i analysis ... The reporting layer buyers usually shortlist when native reports stop being enough.
• Security, backup, high availability, and disaster recovery ... The protection and resilience layer around the core business workload.
• API integration, modernization, and web enablement ... The path most teams follow when they need IBM i to connect more cleanly to newer systems.

Different types of AS400 software you will actually encounter

When buyers say they need AS400 software, they often mean one slice of a much larger market. Breaking the ecosystem into software types makes the search intent far easier to understand.

This is also why a site like AS400Software.com can exist as a focused category authority. The niche is not one product family. It is an entire software economy wrapped around IBM i workloads.

• System software ... IBM i itself, licensed programs, and the base operational components of the platform.
• Business applications ... ERP, accounting, manufacturing, CRM, dispatch, and service workflows.
• Warehouse and mobility software ... Barcode, picking, labeling, receiving, and shipping tools.
• Document and output tools ... Spool management, forms, archiving, and retrieval software.
• Data and reporting software ... Query, BI, dashboards, and database utility layers.
• Security software ... MFA, auditing, SIEM, authority review, exit-point control, and compliance tooling.
• Recovery software ... Backup, replication, HA, role swap, and disaster recovery products.
• Integration software ... EDI, file transfer, APIs, connectors, and middleware.
• Modernization software ... Web front ends, API layers, RPG tooling, testing, and code-assistance platforms.
• Operations software ... Job scheduling, monitoring, alerting, and help-desk workflow support.

What AS400 software became famous ... and what became infamous

In the AS400 market, software becomes famous when it sits close to money, shipments, or uptime. It becomes infamous when it blocks change, hides risk, or keeps knowledge trapped inside a few people.

That is why the platform's most talked-about software is often not glamorous. It is the software that either keeps operations sane or creates daily friction.

• ERP suites ... They became famous because they turned the platform into the system of record for order, inventory, purchasing, finance, and manufacturing flow.
• Warehouse and barcode software ... It became famous because it touches physical operations directly and delivers fast measurable results when it works well.
• EDI software ... It became famous because one broken map or partner onboarding delay can stop revenue, shipments, or invoicing.
• High availability and backup tools ... They became famous because they change the business conversation from whether data was saved to whether the company can keep running.
• Security and auditing tools ... They became infamous when teams postponed them until an audit finding, ransomware scare, or insurance questionnaire exposed the gap.
• Green-screen-heavy custom applications ... They became infamous when nobody documented them, the original developers retired, and every change felt risky.
• Job scheduling and document workflow tools ... They became quietly famous because they remove repetitive operational drag that people otherwise treat as normal.

How AS400 software works in practice

Most IBM i software is better understood as workflow software than as standalone desktop software. Data usually lives in Db2 for i, business logic runs in RPG, COBOL, Java, SQL routines, or other supported languages, and users interact through 5250 sessions, browser interfaces, reports, APIs, mobile screens, or batch outputs.

The visible application is only one layer. Under it sit jobs, libraries, authorities, queues, printers, integrations, schedules, and recovery assumptions that keep the workload stable day after day.

• 5250 terminals and modern interfaces ... Users sign on through 5250, browser, API, or mobile-connected workflow screens depending on the workload.
• Db2 for i data and business logic ... Business logic reads and writes data under controlled job and authority rules.
• Batch jobs and operational schedules ... Orders, invoices, updates, interfaces, and overnight operational work often move through scheduled processing.
• Reports, forms, spool files, and EDI messages ... The output layer moves information to users and external partners.
• APIs, SQL services, and integration layers ... These are what connect IBM i software to the wider business stack.

AS400 software download, installation, and deployment realities

Searches for AS400 software download usually underestimate how platform-specific the install story is. There is no universal AS400 software ISO that answers every need.

What you download depends on whether you need an IBM access client, a development IDE, a vendor application, a licensed program, a PTF group, an open-source runtime, or a trial. A serious installation plan also includes backups, a test path, authority planning, integration checks, and rollback thinking before production cutover.

• IBM Access Client Solutions for 5250, data access, and administration utilities.
• RPG and development tooling ... This is the internal site destination that best matches Rational Developer for i and similar application-development packages.
• Vendor programs for ERP, EDI, HA, security, and reporting ... The site directory is the right starting point when the install package is part of a broader IBM i software shortlist.
• Open-source integration workloads ... PHP, Python, Node.js, and connector-heavy projects usually sit closer to integration and modernization planning.
• PTF, Technology Refresh, and firmware planning ... Release, support, and hardware compatibility planning matter before production cutover.
• Deployment checklist and recovery thinking ... Serious deployment work still starts with backup, rollback, and recovery discipline.

System requirements for AS400 software

System requirements are never one-size-fits-all because the right answer depends on the IBM i release, the Power model, the vendor application's licensing rules, storage needs, and integration load.

Still, the recurring requirement pattern is stable enough to summarize. Hardware support, IBM i release compatibility, firmware, storage, memory, user licensing, client tooling, and integration dependencies all matter before any software shortlist becomes real.

• Supported IBM Power hardware ... The IBM i release has to match the hardware class you intend to run.
• CPU, memory, and storage sizing ... Capacity planning has to cover both the application and its batch peaks.
• Firmware, PTF groups, and Technology Refresh level ... Compatibility planning matters before any shortlist becomes real.
• Db2 for i, authorities, and environment dependencies ... Database, security, networking, printer, and directory dependencies are part of the real requirement set.
• Client access and API endpoints ... ACS, browser access, ODBC, JDBC, and API access patterns all matter for end users and integrations.
• Current release and hardware support status ... Power 11, Power 10, Power 9, and release support windows keep moving, so the compatibility check cannot be treated as static.

What are the benefits of using AS400 software

The benefits of using AS400 software are easiest to understand when you stop comparing it to consumer software and start comparing it to failure-prone business process chains.

IBM i shops keep paying for this stack because the best AS400 software compresses complexity into a smaller operational surface area. The value is not only old reliability. It is reliable workflow, controlled change, and a realistic modernization path without burning down the business.

• Reliability for core transaction workloads ... The platform is strongest where business continuity matters.
• Tight database and application integration ... Db2 for i remains one of the structural reasons the stack feels cohesive.
• Long application life with high business continuity ... The history timeline shows how unusual the platform's continuity really is.
• Strong fit for ERP, warehouse, distribution, finance, and manufacturing workflows ... These are exactly the workload classes that kept IBM i commercially relevant.
• A path to modernize incrementally ... Most teams do not need to replace everything at once to make progress.
• A software ecosystem built around real operational pain points ... The broader library shows how many specialized problem categories already exist around IBM i.

Is AS400 difficult to learn

It is not easy if you start with every acronym at once, but it is not mysterious either. The platform feels difficult mostly because beginners meet thirty years of accumulated vocabulary on day one.

A role-based learning path works better than a generic crash course. Administrators should learn jobs, users, backups, and security first. Developers should learn RPG, CL, Db2 for i, and existing business flow first. Analysts should learn data, reporting, and process context first.

• Learn the lineage and naming first ... That is the fastest way to make AS/400, IBM i, iSeries, and Power stop feeling like separate worlds.
• Use one real business workflow as the anchor ... A concrete workflow beats abstract theory for most new learners.
• Read the existing operational schedule ... Jobs, menus, reports, and file names connect vocabulary to real activity fast.
• Add SQL, APIs, and open-source tools after the basics ... Integration and modernization topics make more sense once the core platform vocabulary clicks.

Is AS400 still used today

Yes. The more precise statement is that the AS/400 lineage is still used today through IBM i on IBM Power systems. That is not a sentimental claim ... it is visible in IBM's current product pages, release life cycle, support matrix, and client stories.

As of Thursday, July 23, 2026, IBM i 7.4, 7.5, and 7.6 are all part of active real-world planning discussions, IBM i 7.6 is current, and Power 11 support is already part of the active platform story. A dead platform does not get that treatment.

• Current IBM i positioning remains active ... The current platform name is still in live product and buyer language.
• Current release support dates still matter ... Support windows are one of the clearest signals that the platform is still operationally current.
• Current Power 10 and Power 11 planning is active ... Hardware planning did not stop with the old AS/400 brand era.
• Current buyer demand still exists across software categories ... ERP, security, HA, reporting, integration, and modernization demand is still commercially real.

How much does an AS400 cost

The cost question is never just 'how much does an AS400 cost.' The real cost stack includes hardware or hosting, IBM i licensing tier, third-party software, HA or backup design, support contracts, storage, security, consulting, and staffing.

Cheap hardware can still lead to expensive operations if uptime needs, integrations, or staffing gaps are ignored. Mature buyers price the operating model, not just the box.

• Server or cloud capacity ... Hardware or hosting still sets the base of the cost stack.
• IBM i tiers and software subscriptions ... Licensing tiers and third-party software change the economics quickly.
• ERP, EDI, WMS, security, HA, and reporting vendor licensing ... The real price picture usually spans multiple software layers, not one package.
• Implementation and migration work ... Services and change work are often underbudgeted compared with the license itself.
• Training and staffing ... Skills and team readiness shape total cost just as much as the technology choices do.
• Ongoing support, backup, and refresh planning ... Long-term operating cost is where many simplistic cost estimates fall apart.

People also search for around AS400 software

The related searches around AS400 software reveal how mixed the intent really is. People are not searching one neat category. They are jumping between platform identity, business applications, administration, download intent, and niche operational software.

These are the common follow-on searches and what they usually mean.

• AS400 software download ... usually a search for ACS, a vendor trial, sample code, or a licensed program package rather than one generic platform download.
• What is AS400 software used for ... The practical workload answer inside this same article.
• AS400 ERP software ... Still the biggest historical workload class and the center of many IBM i environments.
• AS400 software release date ... Usually either the 1988 AS/400 launch date or the newer IBM i release timeline.
• AS400 dispatch software ... Usually a route, service, fleet, delivery, or field-workflow variation tied back to ERP data.
• AS400 IBM ... A naming query from users trying to connect the older AS/400 term to today's IBM i and Power branding.
• AS400 warehouse management system ... One of the most commercially valuable software niches on the platform.
• AS400 mainframe ... Related in enterprise reputation, but still a different lineage from IBM z Systems.
• AS400 administration ... Usually the operational work of users, jobs, backups, performance, security, printing, and change control.
• IBM i ... The current platform name buyers eventually need once they move beyond nostalgic terminology.

Why this entire site is dedicated to AS400 Software

This entire site is dedicated to AS400 Software because the search phrase still maps to real commercial intent. Buyers, administrators, former programmers, and management teams still ask software-specific questions under the older AS400 label even when the current vendor language says IBM i.

That gap creates a real education problem and a real SEO opportunity. The point of AS400Software.com is to cover the software categories, buyer guides, terminology, and vendor research around that persistent demand with more depth than a single vendor page or a one-paragraph definition can offer.

Sources

• IBM History ... The AS/400
• IBM i Product Page
• IBM Support ... Release life cycle
• IBM Support ... IBM i Platform Support Details
• IBM Support ... Planning to upgrade to IBM i 7.4 hardware
• IBM Support ... IBM i V7R5 versus V7R6 comparison
• IBM Documentation ... Programming on IBM i
• IBM Documentation ... Scripting languages on IBM i
• IBM Documentation ... Application programming language support
• IBM Support ... IBM i Access Client Solutions