Information Management System
In 1966, in the engineering offices of Rockwell’s Space Division, engineers working on the Apollo program juggled thousands of technical drawings, with each modification to a component triggering a cascade of verifications across the entire space capsule. There was no room for error when it came to sending men to the Moon.
Uri Berman, an IBM consultant seconded to Rockwell, observed this organized chaos. Together with Pete Nordyke, they envisioned a bold solution that completely separated data management from application code. Their prototype, which they named DATE (Disk Applications in a Teleprocessing Environment), radically transformed how engineers accessed technical information. Gone were the endless trips to paper archives—a terminal connected to an IBM 7010 now sufficed to check the status of a drawing and its ongoing modifications. This separation between data and processing formed the foundation of Data Language/One (DL/I), an interface that freed programmers from the physical constraints of disk storage. The idea gained ground that an application should not reinvent the wheel of file management. DL/I standardized these operations, improved data integrity, and simplified program maintenance.
The project took on new scope in 1966 with the arrival of IBM System/360 computers. Dr. Robert R. Brown assumed technical leadership, supported by consultant Bob Patrick. The team set itself the goal of creating software that met IBM Type 2 standards without modifying the OS/360 operating system. This seemingly limiting constraint would actually ensure the longevity of their creation.
The collaboration expanded beyond Rockwell. Caterpillar Tractor joined the venture, bringing its specific industrial management needs. About twenty programmers worked on what became IMS/360, integrating DL/I into a more ambitious architecture. On August 14, 1968, the first READY message from IMS appeared on a Rockwell terminal. The Apollo mission could now count on a new computer companion.
The IMS architecture rested on three pillars: the database manager (IMS DB), the transaction manager (IMS TM), and common services. This modularity allowed à la carte usage. Some clients exploited only the database component (DBCTL), while others focused on transaction processing (DCCTL). Everyone found what they needed according to their specific requirements.
An organizational innovation accompanied the technical deployment. Dan Gilbert became Rockwell’s first Database Manager in history, foreshadowing the database administrator profession. This position centralized responsibility for data organization and integrity, breaking with the previous dispersion of these tasks across different departments. IMS’s hierarchical approach contrasted with the relational world that would later dominate. This structure, born from the needs of managing space bills of materials, excelled at predefined access patterns. Relationships between data were established in advance, creating optimized paths. This philosophy differed radically from relational databases, where relationships are constructed dynamically during query execution.
In 1988, twenty years after its inception, IMS equipped 7,000 installations worldwide. In the 2000s, the system processed more than 50 billion transactions daily and managed over 15 million gigabytes of data for more than 200 million users. These volumes testified to its robustness and capacity for evolution.
Technological evolution did not spare IMS, which adapted without renouncing its principles. The introduction of OTMA (Open Transaction Manager Access) opened the system to TCP/IP applications, breaking the isolation of IBM’s proprietary network architectures. Java, XML, and web services gradually found their place, inscribing IMS into the service-oriented architecture era. Integration with Microsoft .NET or SAP further expanded its ecosystem.
IBM’s Parallel Sysplex gave IMS a second youth. Sharing data and messages between multiple instances optimized resource utilization while strengthening availability. These sophisticated disaster recovery mechanisms made it a preferred choice for applications where downtime is not an option.
Today, IMS remains a pillar of transaction processing in the financial, manufacturing, and government sectors. This longevity in a field marked by frantic innovation cycles validates the initial architectural choices. Separation of concerns, data integrity, and processing performance remain central priorities, more than fifty years after the first technical drawings of the Apollo capsule.