History of IBM i : Part 5 – SLIC (System Licensed Internal Code) in IBM Power Systems

The System Licensed Internal Code (SLIC), also known as Licensed Internal Code (LIC) in broader IBM contexts, is a critical, proprietary layer in the IBM i operating system architecture running on IBM Power Systems. It serves as the hardware-dependent kernel-like component that bridges the abstract, hardware-independent layers of IBM i with the underlying POWER processor hardware.

IBM i Architecture: (medium)

SLIC is essentially the “secret sauce” that enables IBM i’s legendary hardware independence, extreme backward compatibility, and integrated features like the built-in Db2 database.

Table of Contents

Architectural Position and Layers

IBM i’s architecture is layered, with SLIC occupying the lowest software layer above the hardware:

This structure isolates applications from hardware changes. SLIC implements the TIMI on the specific POWER architecture, translating TIMI bytecode into native POWER instructions.

POWER architecture (seasoft)

In virtualized environments with Logical Partitions (LPARs), there is one SLIC instance per physical Power server, shared across all IBM i LPARs. SLIC handles translation and resource management for all partitions, enforcing isolation while allocating CPU, memory, and I/O.

Key Functions of SLIC

SLIC performs a wide range of low-level and integrated functions:

  1. TIMI Translation: Converts TIMI intermediate code (bytecode) from compiled programs into optimized native POWER machine code. This ahead-of-time translation occurs on program load or hardware change, with results cached for performance.
  2. Kernel-Like Operations: Manages memory (including single-level store), process scheduling, I/O, interrupts, and exception handling.
  3. Single-Level Store Implementation: Treats all storage (RAM and disk) as a unified 64-bit (or larger) virtual address space, automatically handling paging and persistence.
  4. Object-Based Model: Enforces IBM i’s object-oriented design, where everything (files, programs, libraries) is an encapsulated object with strict access controls.
  5. Integrated Database (Db2 for i): Much of the relational database engine is embedded directly in SLIC, providing seamless, high-performance data access without separate server processes.
  6. Security and Isolation: Prevents direct hardware access by applications, reducing vulnerabilities (e.g., no buffer overflows reaching hardware).
  7. Virtualization Support: Works with PowerVM hypervisor for LPAR management, resource allocation, and shared hardware access.
IBM i: Power9 Systems Processor (midlandinfosys)

SLIC is closed-source and licensed (not owned outright by customers), allowing IBM to evolve it freely for new hardware without breaking compatibility.

Historical Evolution

Chief architect Frank Soltis designed much of this structure to ensure “technology independence.”

Benefits and Implications

SLIC updates (part of IBM i PTFs or resaves) are applied via IPLs or slip installs.

Final Thoughts

SLIC is the foundational, hardware-adapting layer that makes IBM i on Power Systems uniquely resilient and future-proof. By handling translation, core OS functions, and integrated capabilities below the TIMI boundary, it allows IBM to innovate hardware aggressively while preserving decades of software investments.

Software layers between the system hardware and operating systems (IBM Redbooks)

As of late 2025, SLIC continues to support the latest POWER processors, ensuring IBM i’s relevance in enterprise computing.

  1. https://en.wikipedia.org/wiki/IBM_i Comprehensive overview of IBM i architecture, detailing SLIC as the hardware-dependent layer below TIMI, its role in translating TIMI bytecode, implementing single-level store and the integrated Db2 database, and its evolution during the 1995 CISC-to-RISC transition (replacing HLIC/VLIC with over 2 million lines of C++ code).
  2. https://en.wikipedia.org/wiki/IBM_AS/400 Explanation of SLIC’s creation during the PowerPC transition, its function in hardware abstraction, and integration with TIMI for backward compatibility.
  3. https://medium.com/@dhemanthc/ibm-i-architecture-how-timi-and-slic-enable-hardware-independence-82aea3f2dae3 (November 2025) Detailed article on IBM i layered architecture, including SLIC’s single instance per physical server managing multiple LPARs, TIMI translation, resource allocation, and isolation.
  4. https://www.ibm.com/docs/en/i/7.5?topic=system-recovering-licensed-internal-code (and similar for other versions) Official IBM documentation describing Licensed Internal Code (SLIC) as the layer just above hardware, with recovery procedures. Inside the AS/400 and Fortress Rochester: The Inside Story of the IBM iSeries by Frank G. Soltis Books by IBM i chief architect Frank Soltis providing foundational insights into SLIC’s design, its role in technology independence, single-level store, and processor migrations.
  5. https://handwiki.org/wiki/Software:IBM_i In-depth technical summary of SLIC’s implementation in C++, its replacement of earlier microcode layers, and functions like query optimizers and database integration.
  6. https://www.ibm.com/support/pages/steps-slip-install-licensed-internal-code IBM support page on installing/updating SLIC (Licensed Internal Code), highlighting its proprietary nature and integration with IBM i.