The phrase autonomic computing is new to many IT staff and is used to define the new technology of self-managing systems. However, the practice of designing and implementing self-managing systems has long been a goal and objective of IBM. Numerous examples exist within the IBM portfolio of products in hardware and software, some of which go back over twenty years or more. A few examples: -
The IBM 4300 series of mainframe computers were introduced in 1982. This line was a forerunner of the newer range of mainframes in use today, such as the OS/390 series. A feature was introduced with the 4300 that included internal self-diagnostics. Moreover, it contained a feature to transmit findings, logs, memory dumps, and return codes to remote IBM system engineers, who could then provide customers with quicker solutions. -
More recently, personal computers now have some self-configuration abilities and can receive updates from the Internet, such as critical updates to operating systems. They also have the power to allocate memory. -
The IBM Tivoli suite of software products has many autonomic capabilities. The IBM Tivoli Storage Manager has self-configuration features, such as automatic domain configuration and file identification; self-correction features, such as storage pool, restoration, and correction; self-protection features, such as automated backup to protect data and files when needed; and policy-based systems that optimize disk and tape storage systems. -
RAID (Redundant Array of Independent Disks) systems are another example. These systems connect multiple disk arrays into one logical unit. If errors or problems arise in read/write functions, data is switched automatically to another part of the array. So, the processes of self-managing systems have existed for some time. While these technologies move in the right direction, they are a precursor to fully autonomic computing. Autonomic computing enhances and builds on the base of existing IBM portfolio products and brings better levels of automation through the five level processes. |