Jump to content

OS/2

From Alfawiki
OS/2
Company typeOperating system
IndustryComputer software
Founded1987
FounderIBM and Microsoft
FateMicrosoft withdrew in 1990; IBM continued development until 2006; licensed to third parties thereafter
ProductsOS/2 operating system, including versions OS/2 1.0, 1.1, 1.2, 1.3, 2.0, 2.1, Warp 3, Warp 4
OwnerIBM (original), later licensed to Serenity Systems and Arca Noae LLC

OS/2 is a closed-source operating system designed for x86 and PowerPC personal computers, originally created through a collaboration between IBM and Microsoft under the guidance of IBM software architect Ed Iacobucci. Introduced in 1987 as the successor to DOS, Microsoft withdrew from its development in 1990, leaving IBM to continue independently. The final significant version was OS/2 Warp 4, released in 1996, with maintenance updates extending until 2001.

The title "Operating System/2" stems from its release coinciding with IBM's second-generation "Personal System/2" computer lineup. OS/2 was designed primarily for the Intel 80286 processor, serving as a protected-mode replacement for IBM PC DOS. It maintained compatibility with system calls used by MS-DOS to support "Family Mode" applications that could operate across both platforms. The architecture of OS/2 incorporated concepts from Unix, Xenix, and Windows NT. Its market focus was mainly on networked environments catering to business professionals.

With the launch of OS/2 2.0 in 1992, IBM delivered its first fully independent 32-bit iteration after Microsoft's departure due to strategic disagreements regarding operating system positioning against Windows 3.1. IBM targeted consumer markets with OS/2 Warp 3 in 1994, supported by an extensive marketing campaign; however, it faced challenges competing with Microsoft's entrenched dominance and alleged anti-competitive practices. Following the unsuccessful Workplace OS project, OS/2 Warp 4 became the final major update in 1996, and IBM discontinued official support on December 31, 2006.

After IBM's exit, licensing agreements enabled third parties to continue OS/2's legacy: Serenity Systems distributed it as eComStation from 2001 to 2011, and since 2017, Arca Noae LLC has been developing and marketing it under the name ArcaOS.

1985–1990: Collaborative IBM–Microsoft development

The creation of OS/2 commenced with the IBM–Microsoft "Joint Development Agreement" established in August 1985.[1] Initially codenamed "CP/DOS," the project required two years before delivering its first product.

OS/2 1.0 (1987)

The release of OS/2 1.0 encountered delays partly due to IBM developers adapting to programming in C.[2] Officially announced in April 1987 and launched in December of the same year, the initial version featured only a text-based interface; a graphical user interface was introduced approximately one year later with OS/2 1.1. This version provided an API managing video output and input devices that allowed protected mode applications without direct hardware manipulation. Development tools enabled execution of family mode programs within MS-DOS environments, while the OS/2 Extended Edition v1.0 incorporated a database component named Database Manager (DBM), related to IBM’s DB2.[3] Multitasking of text sessions was facilitated by a task-switcher called Program Selector, accessible via Ctrl-Esc.[4]

In 1988, the Extended Edition of OS/2 1.0 expanded functionality by adding communication and database features such as Systems Network Architecture (SNA), APPC/LU 6.2 protocols, LAN Manager integration, Query Manager, and SQL capabilities.

In a 1987 prediction, Microsoft’s Bill Gates anticipated that over 80% of new office systems would operate on OS/2 within three years.[5] While Ashton-Tate expressed enthusiasm about this forecast, Lotus Development remained doubtful regarding market demand. Gates revealed that Microsoft planned to initially release Windows applications alongside affordable upgrades for OS/2; conversely, Ashton-Tate and Lotus intended to prioritize launching their software on OS/2 first.[6]

OS/2 1.1 (1988)

The graphical interface known as Presentation Manager made its first appearance with OS/2 1.1 in October 1988, bearing a strong resemblance to Windows 2.1, which had been released earlier that year. Subsequent updates in versions 1.2 and 1.3 refined the interface to more closely mirror the look and feel of Windows 3.0.

The Extended Edition of OS/2 1.1, distributed exclusively through IBM’s sales channels, introduced support for distributed databases on IBM systems as well as SNA communications tailored for IBM mainframe environments.

OS/2 1.2 (1989)

With the release of version 1.2, Installable Filesystems were introduced alongside the High Performance File System (HPFS), which enhanced the FAT filesystem by enabling support for long filenames and extended file attributes. Additionally, extended attributes were incorporated into the FAT system.

The Extended Edition further expanded capabilities by adding support for TCP/IP networking and Ethernet connectivity.

During the late 1980s, promotional materials from Microsoft’s Gordon Letwin and IBM’s Ed Iacobucci positioned OS/2 as the forthcoming operating system poised to drive business computing forward.

OS/2 1.3 (1990)

By 1990, the partnership between Microsoft and IBM had fractured, largely due to the commercial triumph of Windows 3.0, which was bundled with most new PCs, unlike OS/2 that was sold separately and lacked drivers for many non-IBM devices. Microsoft redirected its efforts toward Windows development, attracted by its wider hardware compatibility and stronger market adoption.

Differences in organizational culture and strategic vision contributed to this split: Microsoft championed an open hardware ecosystem, whereas IBM sought to use OS/2 as a lever to increase sales of its own hardware products, even requesting removal of features unsupported by IBM devices. Microsoft developers criticized IBM for bureaucratic inefficiencies and code complexity, while IBM developers considered Microsoft’s code overly concise.

From the outset, OS/2 and Windows employed distinct APIs, complicating software compatibility between platforms. At IBM’s insistence, OS/2 utilized a modified Windows API, which discouraged third-party vendors because it necessitated parallel development efforts for both operating systems.

Targeting the Intel 80286 processor with its 16-bit segmented memory model due to commitments to PS/2 customers, OS/2 1.x was limited in performance compared to Windows/386 2.1’s ability to multitask DOS applications. Even in OS/2 1.3 (1991), DOS applications ran within a single 640 kB "DOS box."

Meanwhile, Microsoft was developing a more advanced operating system under Dave Cutler—formerly architect of VAX/VMS—who led efforts on a new architecture initially named NT OS/2 but later rebranded as Windows NT following the split.

After the separation, IBM assumed responsibility for maintaining and advancing OS/2; Microsoft concentrated on consumer-oriented DOS and Windows systems while preparing Windows NT as a high-end platform compatible with existing applications.

Windows NT retained several elements derived from OS/2 heritage such as HPFS support, text-mode OS/2 applications compatibility, and LAN Manager networking capabilities; early NT versions even contained OS/2 copyright notices along with subsystems supporting Presentation Manager applications.

OS/2 2.0 (1992)

Released in April 1992 with a retail price of $195, OS/2 2.0 introduced a native 32-bit API for applications, although some components like drivers remained partly 16-bit. It unveiled the Workplace Shell, an object-oriented user interface that transformed interaction by allowing users to manage programs, files, and devices via on-screen objects rather than traditional window-based controls.

IBM marketed OS/2 2.0 as "a better DOS than DOS and a better Windows than Windows," incorporating a fully licensed and enhanced version of MS-DOS 5.0. This integration enabled OS/2 to run multiple DOS applications concurrently while supporting a modified Windows 3.0 environment along with its associated software.

Unlike OS/2 1.x—which was constrained by the Intel 80286 processor to running only one DOS program at a time with full control at risk of system crashes—OS/2 2.0 leveraged the Intel 80386’s virtual 8086 mode to execute multiple DOS programs safely within isolated virtual machines configurable for performance needs. This virtualization extended support even to real-mode operating systems such as Xenix, subject to limitations on direct hardware access.

OS/2 supported DOS programs utilizing the DOS Protected Mode Interface (DPMI), but not those relying on the older VCPI interface used by certain Windows applications. While OS/2 permitted DOS programs to mask hardware interrupts—which could cause system deadlocks—it mitigated such risks on specific IBM hardware through watchdog timers. Later releases utilized features from Intel’s 80486 and Pentium processors such as the Virtual Interrupt Flag (VIF) to further address these challenges.

To facilitate multi-boot setups, OS/2 introduced Boot Manager, allowing installations across separate partitions for different versions of DOS, Windows, or OS/2 and providing users with startup-time selection options.

OS/2 2.1 (1993)

Launched in 1993, OS/2 2.1 improved Windows 3.0 and 3.1 compatibility by enabling Windows user-mode components to operate within a virtual DOS machine (VDM). Whereas earlier OS/2 versions contained nearly complete Windows code—Windows 3.0 embedded in OS/2 2.0 and Windows 3.1 in OS/2 2.1—later releases dynamically patched the user's existing Windows installation to avoid extra licensing fees. Windows applications could run either in full-screen mode using dedicated video drivers or "seamlessly," integrating directly into the OS/2 desktop environment. Nevertheless, switching between full-screen WinOS/2 sessions and the Workplace Shell occasionally led to conflicts over hardware access.

OS/2 supports only Windows user-mode components, lacking compatibility with Windows device drivers (VxDs) and software that depends on them.

Several Windows programs can operate cooperatively within a single session without memory protection, mimicking the native behavior of Windows 3.x. For enhanced isolation, OS/2 allows multiple Windows sessions to run in separate VDMs, providing preemptive multitasking and memory protection between sessions (though not within an individual session). This approach enables users to segregate applications across sessions but requires additional system resources.

Intercommunication between OS/2 and Windows applications is facilitated through DDE, while OLE functions are supported among Windows programs.

IBM's OS/2 for Windows (code-named Ferengi), also known as "OS/2, Special Edition," was designed to leverage Microsoft's market share but risked confusing consumers by appearing as a Windows utility rather than a standalone multitasking OS capable of hosting Windows itself. Distributed via CD-ROM or floppy disks, its documentation implied that a prior Windows installation was necessary, although it did support subsequent installations of Windows from HPFS partitions—advantageous for larger drives. Compatibility depended on patching certain memory areas but was disrupted by Windows 3.11, prompting accusations that Microsoft intentionally obstructed IBM’s product.

OS/2 Warp 3 (1994)

Released in 1994, OS/2 version 3.0 was rebranded as OS/2 Warp to highlight performance enhancements and revitalize the product’s image. The name "Warp," originally an internal IBM codename inspired by Star Trek, was adopted for public use. At the launch event, Kate Mulgrew from Star Trek: Voyager took the place of the originally scheduled Master of Ceremonies, Patrick Stewart.

OS/2 Warp expanded hardware compatibility, multimedia features, and Internet networking capabilities while including the basic office suite IBM Works. It was available in two editions: the more affordable "Red Spine," which required an existing Windows installation for running Windows applications, and the premium "Blue Spine," which integrated Windows support directly into its own installation. Given that most PCs came preloaded with Microsoft Windows and due to its lower price point, the "Red Spine" edition became more widely adopted. In mid-1995, OS/2 Warp Connect ("Grape") was introduced, offering full LAN client functionality.

Previous versions such as OS/2 2.0 upgraded core subsystems to 32-bit architecture, with these improvements incorporated into OS/2 2.1. Warp 3 debuted a fully 32-bit windowing system, while Warp 4 progressed further by introducing an object-oriented 32-bit GRADD display driver model.

Workplace OS (1995)

Beginning in 1991, IBM initiated the development of Workplace OS to succeed OS/2. This innovative system employed a microkernel design capable of supporting various IBM operating systems, such as OS/2, as distinct microkernel "personalities." It incorporated significant enhancements including a centralized system registry, the Journaled File System (JFS), compatibility with UNIX graphics libraries, and an updated driver framework.

Aimed at POWER architecture platforms, Workplace OS was part of IBM's strategy to rival Intel’s dominance by introducing a comprehensive lineup of PowerPC-based machines. Early prototypes were presented to enterprise clients who expressed reservations about moving away from Intel-based hardware.

The roadmap envisioned Workplace OS eventually replacing OS/400 and deploying its microkernel technology in sectors like telecommunications and set-top devices. A pre-alpha version was showcased at Comdex and briefly at an OS/2 user group meeting; however, persistent development obstacles hindered progress.

When released in 1995, Workplace OS encountered substantial development expenses—combined with OS/2 costs totaling approximately $990 million annually—and limited market traction, marking the downturn of both the Workplace OS initiative and the OS/2 product series.

OS/2 Warp 4 (1996)

In 1996, OS/2 Warp 4 introduced new functionalities such as integrated Java support and speech recognition technology. IBM also launched server variants of Warp 3 and Warp 4 that incorporated IBM’s LAN Server, alongside bundling a personal edition of Lotus Notes equipped with productivity templates. In the UK, a freely distributed demo CD-ROM contained nearly the entire operating system and was easily bypassed by cracking measures—likely a tactic to broaden the user base and encourage third-party software development. By the year 2000, certain publications offered full Warp 4 copies without activation restrictions. Additionally, specialized editions of OS/2 2.11 and Warp 4 implemented symmetric multiprocessing (SMP) capabilities.

Although OS/2 sales were primarily focused on networked corporate environments, Microsoft Windows NT overtook it during the early 1990s. Despite possessing technical advantages over Windows 95, OS/2 struggled to gain traction in consumer and standalone PC markets; reports highlighted installation difficulties even on IBM’s own Aptiva home computer line. Microsoft proposed licensing Windows 95 to IBM under terms comparable to those extended to Compaq if IBM ceased further OS/2 development; IBM rejected this offer, adhering instead to an "IBM First" philosophy that emphasized promoting OS/2 Warp to stimulate hardware and software sales. Negotiations deteriorated further following IBM’s acquisition of Lotus SmartSuite, which directly competed with Microsoft Office. IBM ultimately signed the Windows 95 license agreement shortly before its release, limiting momentum for PC sales. In conclusion, IBM conceded that OS/2 was not sustainable for maintaining its PC business.

1996–2001: Downsizing

An internal evaluation within IBM examined the competitive pressure posed by Microsoft Windows 95, uncovering significant code quality deficiencies in OS/2 that necessitated over twenty service pack updates, along with operational inefficiencies in the Boca Raton and Austin development teams. This confidential analysis revealed critical vulnerabilities throughout IBM’s Personal Systems Division, prompting severe cutbacks: more than a 95% reduction in budget allocations for the product line; termination of ongoing development projects including Workplace OS; closure of the Boca Raton facility; discontinuation of sales and marketing activities; and layoffs exceeding 1,300 employees. In the final full year prior to these reductions, IBM had spent $990 million on development efforts. Warp 4 remained the last broadly distributed version of OS/2.

2001–2006: Phase-out and End of Official Support

Although OS/2 maintained a dedicated user base, it never achieved widespread adoption beyond select industries where IBM held significant sway. It notably operated numerous banking ATMs, ticketing machines for the French SNCF, Nortel’s voicemail infrastructure, and NPR’s Satellite Operations Support System until 2007.

IBM discontinued sales of OS/2 on December 23, 2005, and terminated formal support by December 31, 2006. The last official IBM release was OS/2 Warp 4.52, issued in December 2001 for both desktop and server environments. Following the end of support, IBM continued to provide paid defect assistance while advising customers to migrate complex applications toward platform-independent e-business solutions such as Java. Ultimately, IBM recommended transitioning to alternative operating systems like Linux to modernize IT infrastructures.

2001–present: Continuation by Third Parties

After IBM halted active development of OS/2, various third-party entities endeavored to sustain the platform’s lifecycle. Stardock expressed interest in assuming stewardship in 1999; however, IBM chose not to proceed with this proposal. Serenity Systems later secured licensing rights from IBM and began marketing OS/2 as eComStation starting in 2001. Currently distributed by XEU.com, eComStation’s most recent release (version 2.1) arrived in 2011. In 2015, Arca Noae, LLC acquired reseller rights from IBM and introduced ArcaOS in 2017. ArcaOS has undergone several updates and remains actively developed as of 2023.

Attempts to Open Source

In 2005 and again in 2007, campaigns sought to persuade IBM to release OS/2 under an open source license; however, IBM declined due to legal complexities and technical limitations. The presence of proprietary components licensed from Microsoft and Amiga technology hindered full open-sourcing efforts. Nonetheless, IBM contributed Object REXX to the Open Object REXX initiative hosted on SourceForge.

A petition initiated by OS2World aimed to liberate portions of OS/2’s codebase. Linux indirectly benefited from OS/2 through IBM’s release of the JFS file system, which was initially ported from Linux back into eComStation and incorporated into eComStation version 2.0 as well as later ArcaOS 5.0 releases—enabling boot capabilities from JFS-formatted partitions.

Release Overview

The dates listed correspond to US English versions unless otherwise indicated.

Date Version
December 1987 OS/2 1.0
November 1988 OS/2 1.1
October 1989 OS/2 1.2
December 1990 OS/2 1.3
October 1991 OS/2 2.0 LA (Limited Availability)
April 1992 OS/2 2.0
October 1992 OS/2 2.00.1
May 1993 OS/2 2.1
November 1993 OS/2 for Windows
February 1994 OS/2 2.11
July 1994 OS/2 2.11 SMP
October 1994 OS/2 Warp 3
May 1995 OS/2 Warp Connect
December 1995 OS/2 Warp, PowerPC Edition
February 1996 OS/2 Warp Server 4
September 1996 OS/2 Warp 4
September 1996 OS/2 Warp Server Advanced SMP
November 1997 WorkSpace On-Demand 1.0
October 1998 WorkSpace On-Demand 2.0
April 1999 OS/2 Warp Server for e-Business (4.50)
November 2000 OS/2 Convenience Pack 1 (4.51)
November 2001 OS/2 Convenience Pack 2 (4.52)

User interface

The graphical environment incorporates Presentation Manager, which handles windows, fonts, and icons, functioning similarly to a standalone version of X11 or the Windows GDI. Layered on top is the Workplace Shell (WPS), introduced with OS/2 2.0, an object-oriented shell that allows users to manage files, printers, execute legacy software, and carry out sophisticated operations using both native and third-party application objects—providing a level of integration rarely seen in other popular operating systems. WPS adheres to IBM's Common User Access guidelines.

Within WPS, disks, folders, files, program entities, and printers are represented through the System Object Model (SOM), which promotes code reuse among applications written in various programming languages. A distributed extension named DSOM enabled interaction between objects located on separate machines by leveraging CORBA. SOM's object-oriented framework supported inheritance capabilities absent from Microsoft's Component Object Model. Development efforts for SOM and DSOM have since been discontinued.

Multimedia features are accessible via commands from the Media Control Interface. The final update bundled with IBM's edition of Netscape Navigator plugins introduced support for MPEG media files. Compatibility with newer formats such as PNG, progressive JPEG, DivX, Ogg, and MP3 is provided by third-party developers, either integrated within the multimedia framework or as independent applications.

Commands

The following list details the commands available through cmd.exe on OS/2:

Networking

The TCP/IP implementation in OS/2 derives from the open-source BSD stack, as indicated by the use of SCCS-compatible utilities. IBM included networking tools such as ftp and telnet, along with corresponding server software. Additionally, the company offered networking enhancements like NFS integration and an X11 server to improve connectivity and system interoperability.

Drivers

Hardware manufacturers showed limited enthusiasm for developing device drivers tailored to alternative operating systems like OS/2, restricting available hardware support to a small group of vendors. To overcome this limitation for graphics adapters, IBM acquired a streamlined variant of the Scitech display drivers, allowing users access to a wide selection of supported video cards through Scitech’s flexible modular driver framework.

Virtualization

Running OS/2 within virtualized environments has traditionally been difficult due to its dependence on the complete x86 CPU feature set, notably its utilization of ring 2, which hindered compatibility with early versions of VMware. More recent VMware editions provide official support for OS/2, particularly the eComStation distribution.

Microsoft’s VirtualPC (initially developed by Connectix) has long enabled OS/2 operation without requiring hardware virtualization, offering "additions" software that enhances integration between host and guest systems. Although current VirtualPC versions no longer include these additions, older iterations remain functional. OS/2 operated as both host and guest on certain VirtualPC versions but is confined to guest mode on x86-based virtualization platforms.

VirtualBox, maintained by Oracle Corporation, supports OS/2 releases from 1.x through Warp 3 to 4.5 and eComStation; however, usage can be challenging due to stringent VT-x/AMD-V hardware virtualization prerequisites. Among these, only ACP2/MCP2 reportedly achieves stable performance.

ArcaOS supports guest operation within VirtualBox, VMware ESXi, and VMWare Workstation, incorporating VirtualBox Guest Additions alongside driver enhancements to optimize guest system performance.

The difficulty in virtualizing OS/2 created a commercial niche: a prominent Moscow bank required OS/2 functionality on modern unsupported hardware and sought a hypervisor solution. Unable to utilize VMware products, it commissioned Russian developers to create a host-based hypervisor compatible with OS/2, which led to the establishment of Parallels, Inc. and their Parallels Workstation software.

Security niche

OS/2 has historically experienced minimal exposure to native computer virus threats; although not inherently immune, its relatively small user base has deterred virus authors. Antivirus solutions for OS/2 primarily focus on detecting DOS and Windows viruses that could potentially impact OS/2 servers.

Problems

Common challenges compared with other operating systems included:

  • Synchronous input queue (SIQ): When a graphical application ceased processing window messages, it could cause the entire GUI to freeze, necessitating a system reboot. This issue was alleviated in later Warp 3 fixpacks and Warp 4 by implementing mechanisms that regain control after detecting unresponsiveness.
  • Absence of unified object handles (OS/2 v2.11 and earlier): Without support for a single thread to wait on multiple asynchronous events simultaneously, console applications frequently resorted to inefficient polling of input devices, resulting in excessive CPU consumption and uneven responsiveness. This limitation was addressed with new system calls introduced in OS/2 3.0.

Historical applications

OS/2 has been widely adopted across global banking and infrastructure industries:

- Prior to transitioning to Windows-based virtual machines by 2011, Iran Export Bank operated a network exceeding 35,000 OS/2 workstations encompassing teller terminals, ATMs, and servers.

- During the 1990s, Brazilian financial institutions such as Banco do Brasil deployed up to 10,000 OS/2 Warp devices. OS/2 continued to power ATMs until their migration to Linux in 2006.

- Australia's Suncorp bank sustained an ATM system running on OS/2 until at least 2002. Similarly, Perisher Blue ski resort utilized OS/2 for its ATMs until approximately 2010.

- In the mid-1990s, accounting and auditing organizations preferred OS/2 for its native 32-bit applications tailored to corporate environments.

- The baggage handling system at Denver International Airport operated on OS/2 but was ultimately abandoned due to software-related delays.

- Radio host Howard Stern publicly endorsed OS/2 and employed it on his IBM ThinkPad laptop.

- From 1994 through its decommissioning in 2007, NPR relied on OS/2 within its Satellite Operations Support System (SOSS).

- Vancouver’s SkyTrain automated rail infrastructure ran OS/2 until it was replaced by Windows XP in the late 2000s.

- The London Jubilee Line Extension Signals Control System utilized OS/2 from 1999 until 2011, managing manual train oversight across multiple locations.

- The Co-operative Bank in the UK implemented OS/2 for its domestic call center using custom account access software that proved difficult to migrate away from.

- As recently as March 2010, Stop & Shop supermarkets continued deploying OS/2 systems.

- Ticket vending machines for London’s Tramlink and New York City’s subway MetroCard system were powered by OS/2, primarily linking simple computing terminals with mainframe backends; the NYC Metropolitan Transportation Authority plans to phase out OS/2 following adoption of contactless payment methods.

- Safeway supermarkets also incorporated OS/2 into their point-of-sale checkout systems.

- Trenitalia utilized OS/2 on desktop systems and Automatic Ticket Counters until 2011; these counters reportedly outperformed newer Windows-based alternatives.

- Abbey National General Insurance employed OS/2 from 1996 to 2001 for motor and home insurance direct call center applications running on the PMSC Series III platform with DB2.2 database support.

Awards

In 1989, BYTE honored OS/2 with an "Excellence" award, likening its role as a development platform to that of the Macintosh in 1984. The magazine anticipated that once fully matured and broadly adopted on 80386 processors, OS/2 would eclipse DOS as a dominant operating system, labeling it a milestone achievement.

In March 1995, OS/2 garnered seven accolades including:

  • InfoWorld Product of the Year.
  • Five CeBIT honors:
    • PC Professional Magazine's Innovation of the Year.
    • CHIP Magazine's Operating System of the Year.
    • DOS International's Operating System of the Year.
    • 1+1 Magazine's Software Marketing Quality award.
    • Industrie Forum's Design Excellence award.
  • SPA Best Business Software Award.

IBM products incorporating OS/2

IBM deployed OS/2 as an embedded operating system across a range of hardware solutions:

Product Product category Role of OS/2
IBM 2074 Console support controller Facilitated connections for 3270 sessions to hosts via ESCON channels. Released in 2000 as a successor to non-SNA 3174 Control Units; discontinued in 2006 and succeeded by the Open System Adapter Integrated Console Controller (OSA ICC).
IBM 3494 Tape library Powered the Library Manager software responsible for controlling the tape accessor robot.
IBM 3745 Communications controller Served as the operating system for both the Service Processor and, when present, the Network Node Processor.
IBM 3890 Document processor Originally operated on OS/2 1.1 Extended Edition running on a PS/2 Model 80 to emulate stacker control software previously hosted on System/360; later upgraded to OS/2 Warp.
IBM 473x ATM Incorporated into various IBM-manufactured ATM models, including subsequent versions co-developed with Diebold.
IBM 9672 IBM mainframe Utilized as the operating system for the Hardware Management Console (HMC) and Support Element (SE); also implemented in later mainframe models such as the IBM 2064.

See also

Further reading

External links

  1. ↑ ...
  2. ↑ ...
  3. ↑ ...
  4. ↑ ...
  5. ↑ ...
  6. ↑ ...