History of AS400 and IBM Power Systems
A short history of the AS/400 platform lineage and how it evolved into the IBM i environments that run on IBM Power today.
A short history of the AS/400 platform lineage and how it evolved into the IBM i environments that run on IBM Power today.
Master DB2 for i stored procedures in 2026: create SQL procedures with CREATE PROCEDURE, define IN, OUT, and INOUT parameters, use local variables and cursors for row-by-row processing, return result sets to callers, handle errors with DECLARE HANDLER and SQLSTATE, call procedures from RPG and CL with RUNSQL, and build reusable database logic encapsulated in DB2 procedures on IBM i.
Call external REST APIs from IBM i in 2026: use QSYS2.HTTP_GET and QSYS2.HTTP_POST SQL table functions to make HTTP requests, parse JSON responses with JSON_VALUE and JSON_QUERY, consume REST APIs from RPG embedded SQL, handle OAuth token authentication, configure the IBM i SSL certificate trust store for HTTPS connections, and integrate external web services with DB2 for i data.
AS400 is the common historical name, while IBM i is the current operating system. This article explains what each term means and why they are not interchangeable.
Master ILE RPG service programs in 2026: compile RPG modules with CRTRPGMOD, create service programs with CRTSRVPGM, export and import procedures with NOMAIN source, build and use binding directories with CRTBNDDIR and ADDBNDDIRE, manage activation groups, use the BNDDIR keyword in RPG source, and build reusable shared procedure libraries on IBM i.
Master IBM i save and restore in 2026: save and restore individual objects with SAVOBJ and RSTOBJ, save entire libraries with SAVLIB and RSTLIB, perform full system saves with SAVSYS, run incremental saves with SAVCHGOBJ, create and use save files with CRTSAVF, save the IFS with SAVSAVFDTA, and design a robust IBM i backup strategy using GO SAVE and BRMS.
AS400 usually means IBM i running on IBM Power hardware. This beginner’s guide explains AS/400, IBM i, and IBM Power in plain language, how the platform evolved, and why organizations still use it.
Master DB2 for i triggers in 2026: create BEFORE and AFTER triggers with CREATE TRIGGER, use FOR EACH ROW and FOR EACH STATEMENT granularity, access transition variables OLD and NEW for changed data, build audit logging triggers for change tracking, cascade business rules across tables, create INSTEAD OF triggers on views, and apply trigger best practices on IBM i.
Master IBM i commitment control in 2026: start and end commitment definitions with STRCMTCTL and ENDCMTCTL, control DB2 transaction scope with COMMIT and ROLLBACK in CL and RPG, use savepoints with SAVEPOINT and ROLLBACK TO SAVEPOINT in embedded SQL, handle commitment control errors, and design reliable multi-file update patterns on IBM i.
Master IBM i job scheduling in 2026: add recurring batch jobs with ADDJOBSCDE, manage schedules with WRKJOBSCDE and CHGJOBSCDE, create schedule calendars and exception calendars for bank holidays, retrieve schedule entries with RTVJOBSCDE, hold and release schedules with HLDJOBSCDE and RLSJOBSCDE, and monitor scheduled job execution from CL.