IBM i
 |
|
| Developer | IBM |
|---|---|
| Working state | Current |
| Source model | Closed source |
| Initial release | 1988 |
| Latest release | 7.3 / April 15, 2016 |
| Marketing target | Minicomputer and enterprise server |
| Available in | English |
| Kernel type | shares many Microkernel (SLIC) and Virtual machine (TIMI) design philosophies |
| License | Proprietary |
| Official website | IBM i |
IBM i is an operating system that runs on IBM Power Systems and on IBM PureSystems. The name was introduced in 2008, and it is the current evolution of the operating system, previously named i5/OS, and originally named OS/400 when it was introduced with the AS/400 computer system in 1988.
It is one of the operating systems supported on IBM Power Systems alongside AIX and Linux as well as on IBM PureSystems alongside AIX, Linux and Windows.
The early IBM System/36 and IBM System/38 series customers were a key target of the AS/400, so OS/400 (and its descendants i5/OS and IBM i), have built-in subsystems that provide backward compatibility with these earlier IBM general business systems. IBM i programs, like System/38 programs before them, contain both processor-independent "virtual" binary code and processor-dependent executable binary code. Compilers for IBM i produce the processor-independent code as their output; the operating system automatically translates the processor-independent code into the processor-dependent code as needed, without the need for source code or attention by IT personnel. Notably, when migrating from a legacy processor, the only effect that most organizations notice is that the program runs somewhat longer when it runs for the first time on the new computer. Migration consists of taking a backup from the old computer, and restoring it on the new.
IBM designed IBM i as a "turnkey" operating system, requiring little or no on-site attention from IT staff during normal operation. For example, IBM i has a built-in DB2 database which does not require separate installation. Disks are multiply redundant, and can be replaced on line without interrupting work. Hardware and software maintenance tasks are integrated. System administration has been wizard-driven for years, even before that term was defined. This automatic self-care policy goes so far as to automatically schedule all common system maintenance, detect many failures and even order spare parts and service automatically. Organizations using i sometimes have when confronting the cost of system maintenance on other systems.
...
Wikipedia