Hubbry Logo
General Comprehensive Operating SystemGeneral Comprehensive Operating SystemMain
Open search
General Comprehensive Operating System
Community hub
General Comprehensive Operating System
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
General Comprehensive Operating System
General Comprehensive Operating System
General Comprehensive Operating System
View on Wikipedia
from Wikipedia

General Comprehensive Operating System (GECOS)
DeveloperGeneral Electric, Honeywell, Groupe Bull, Atos
Working stateCurrent
Initial release1962; 63 years ago (1962)
Latest releaseGCOS 8
Supported platformsGE-600 series, Honeywell 6000 series
Licenseproprietary
Official websiteatos.net/en/products/enterprise-servers/bullsequana-m

General Comprehensive Operating System (GCOS, /ˈdʒiːkoʊs/; originally GECOS, General Electric Comprehensive Operating Supervisor)[a] is a family of operating systems oriented toward the 36-bit GE-600 series[1] and Honeywell 6000 series[2] mainframe computers.

The original version of GCOS was developed by General Electric beginning in 1962.[3] The operating system is still used today in its most recent versions (GCOS 7 and GCOS 8) on servers and mainframes produced by Groupe Bull, primarily through emulation, to provide continuity with legacy mainframe environments. GCOS 7 and GCOS 8 are separate branches of the operating system and continue to be developed alongside each other.[4]

History

[edit]

GECOS/Honeywell GCOS 3

[edit]

The GECOS operating system was developed by General Electric for the 36-bit GE-600 series in 1962–1964; GE released GECOS I (with a prototype 635) in April 1965, GECOS II in November 1965 and GECOS III (with time-sharing) in 1967.[5] It bore a close resemblance architecturally to IBSYS on the IBM 7094 and less to DOS/360 on the IBM System/360. However, the GE 600 Series four processor architecture was very different from the System/360 and GECOS was more ambitious than DOS/360. GECOS-III supported both time-sharing (TSS) and batch processing, with dynamic allocation of memory (IBM had fixed partitions, at that time), making it a true second-generation operating system.

After Honeywell acquired GE's computer division, GECOS-III was renamed GCOS 3, and the hardware line was renamed to the Honeywell 6000 series, adding the EIS (enhanced instruction set, character oriented instead of word oriented).[6][7][8]

Other operating systems given the GCOS name

[edit]

The name "GCOS" was extended to the operating systems for all Honeywell-marketed product lines.

GCOS-64, a completely different 32-bit operating system for the Level 64 series, similar to Multics, was designed by Honeywell and Honeywell Bull developers in France and Boston.[9]

GCOS-62,[10][9] the operating system for another 32-bit low-end line of machines, the Level 62 series, was designed in Italy.

GCOS-61 was the operating system for a new version of a small system made in France (Model 58, later Level 61/58).

The operating system for a new 16-bit minicomputer line from Massachusetts (Billerica), the Level 6, got the name GCOS 6.

GCOS 7 and GCOS 8

[edit]

Another renaming of the hardware product lines occurred in 1979, with the Level 6 becoming the DPS 6, the Level 62 becoming the DPS 4, the Level 64 becoming DPS 7, and Level 66 becoming DPS 8. Operating Systems retained the GCOS brand-name, with GCOS 6, GCOS 4, GCOS 7, and GCOS 8 being introduced. GCOS 8 was an extensive rewrite of GCOS 3,[9] with changes made to support true virtual memory management and demand paging (these changes also required new hardware). GCOS 3 was supported in maintenance for several years after this announcement and renaming. Honeywell Bull published "Large Systems: GCOS 8 OS Time Sharing System User's Guide" in 1986.[11]

Legacy

[edit]

DPS 6 and DPS 4 (ex-Level 62) were superseded by Motorola 68000 and later on PowerPC minicomputers running Unix and the product lines were discontinued, though GCOS 6 ran in an emulator on top of AIX.[12] The DPS 7 line, along with GCOS 7, continued to evolve into the DPS 7000 hardware base.

In the late 1980s Honeywell sold its computer business to a joint venture that initially included NEC and Bull, with Honeywell still holding a stake for a time. Over a couple of years, Bull took over the company. NEC supplied several generations of mainframe hardware at the high end, which would run both GCOS 8 and their own ACOS-4 Operating System. Bull used the nomenclature DPS-9000 for its entire GCOS 8-based mainframe line, which included models designed by both Bull and NEC.

By the late 1990s and early 2000s, Bull's desire was to center its development on a single hardware base, running commodity Intel chips but with Bull value-adds. This platform, called Novascale[13] and based on Itanium 2 processors, ran both Windows and Linux natively. However, instruction set simulators for both the DPS 7000 and DPS 9000 allowed GCOS 7 and GCOS 8 to run on this platform. The demise of the Itanium family required a change of hardware, and as of 2022, GCOS 7 and GCOS 8 are simulated on Bull Sequana M7200 and M9600 Xeon-based hardware respectively.[14][15]

Support for GCOS 7 and GCOS 8 from Bull is planned through at least 2025 including regular hardware and software upgrades.

A trace of GCOS influence remains today in modern UNIX systems. Some early Unix systems at Bell Labs used GCOS machines for print spooling and various other services.[16] The field added to "/etc/passwd" to carry GCOS ID information was called the "GECOS field" and survives today as the "pw_gecos" member used for the user's full name and other human-ID information.

Multics today, under the DPS8M simulator,[17] retains the capability of running GCOS jobs, both batch and timesharing, via the "Multics GCOS Environment Simulator."[18]

Applications

[edit]

GCOS 3 (and later GCOS 7 and GCOS 8) featured a CODASYL network database called Integrated Data Store (IDS) that was the model for the more successful IDMS.[9]

Several transaction processing monitors were designed for GCOS 3 and GCOS 8. An early attempt at Transaction processing (TP) for GCOS 3, the Transaction Processing Executive, assumed that a new process should be started to handle each transaction, and enjoyed only very limited success. Another TP system, the Transaction Driven System (TDS), was soon developed for GCOS 3, using a single process (potentially with multiple threads) to service all transactions. TDS was essentially a Honeywell development. It was later replaced by the backward-compatible Transaction Processing 8 (TP8) on GCOS 8, which profited from the overhaul in GCOS system architecture that came with GCOS 8 to make full use of virtual memory concepts. TP8 used multiple static processes in a way similar to UNIX daemons to handle incoming transactions in a multiplexed way. TDS and its TP8 successor were commercially successful, and TDS predated IBM CICS, which had a very similar architecture. A similar product also called TDS was developed for GCOS-7, but the internal architecture was completely different.

System architecture and concepts

[edit]

GCOS is a multithreading, multiprogramming operating system originally oriented towards batch processing, although later versions incorporated enhancements for timesharing and online transaction processing environments. Systems running GCOS today use it mainly for batch and OLTP, or as a backend enterprise server.

GCOS has a basic architecture similar to that of operating systems for the IBM 360 and earlier IBM 7090 Series, and subsequent operating systems with which it competed. It was also heavily influenced by projects such as MEDINET,[19] Multics, and WWMCCS,[20] and has inherited a strong security structure in consequence. Hardware and software features combine to render the operating system unusually secure for an operating system of its generation and class. Multics influenced the design of the hardware, with gate-oriented secure transfer-of-control instructions and a hardware-enforced system of security levels very similar to that of the famous Multics rings. Operational environments such as WWMCCS drove development of special security features to allow secure hosting of classified information and compartmentalization. For a time separate versions of the GCOS system with special security features turned on were maintained specifically for government customers.

Early versions of GCOS and the hardware it ran on did not support paged virtual memory but did support a single memory segment per process. This made it inferior for time-sharing, especially compared with hardware designed to support Multics and the contemporaneous DEC PDP-10 hardware.

GCOS is a process-oriented OS, in which each process hosts one or more execution threads and executes in its own virtual memory space.[9] Virtual memory is divided into segments of arbitrary size reminiscent of Multics segments, and a second level of address translation converts pure virtual addresses to pageable addresses, which are then converted to real addresses in main memory or backing store. Segments and pages and other constructs include hardware-enforced security parameters. The top-level virtual memory architecture also simplifies sharing of code and data in a secure fashion, again in a way reminiscent of Multics.

Each GCOS version was designed for specific hardware. The most recent machines capable of running the OS do so through emulation of that hardware. The hardware originally had much in common with Multics hardware, so much so that some mainframe equipment could be switched from "GCOS mode" to "Multics mode" with the turn of a dial. Much of the peripheral equipment used with GCOS could also be used with Multics, although front-end network processors were very different between the two systems.

Program languages available for GCOS included GCOS Algol, Algol-68, COBOL, SNOBOL, JOVIAL, APL, GPL,[21] FORTRAN 68, CORAL 66, FORTRAN 77[22] and B.[23]

GCOS8 Storage Units

[edit]

Modern terminology for units of storage applies across various operating systems and computer vendors, and is part of everyday conversation. Terms like megabyte and gigabyte mean much the same to everyone, and terms like mebibyte and gibibyte have been formally standardised.

However, the GCOS8 system pre-dates this mono-culture with some units of its own, as follows:

Unit[24][25] Full Name Meaning Generic Equivalent[b]
WORD Word 36 bits, 6 BCD chars, 4 ASCII chars 4 bytes
LLINK Little Link (sometimes "block") 320 words 1280 bytes or 1.25 kibibytes
LINK Link 12 LLINK's 15,360 bytes or 15 kibibytes
BLINK Big Link 5 LINK's 76,800 bytes or 75 kibibytes

Note that in this system a byte contains 9 bits with values ranging from (000)8 to (777)8 or 0–511, unlike the usual 8-bit-bytes with values ranging from (000)8 to (377)8 or 0-255. This is due to the 36-bit CPU architecture.

Permanent file sizes were specified in Llinks (1280 bytes). Temporary file sizes were specified in Links (15,360 bytes). Since the early 1970s, all GCOS 3 and GCOS 8 disk drives used Logical Block Addressing (LBA).

Installations

[edit]

See also

[edit]

Notes

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

General Comprehensive Operating System

View on Grokipedia
from Grokipedia
The General Comprehensive Operating System (GCOS) is a family of proprietary operating systems designed for mainframe computers, initially developed by in the early 1960s to support and other enterprise workloads on its hardware. Originally known as GECOS (General Electric Comprehensive Operating Supervisor), it was renamed GCOS following Honeywell's acquisition of GE's computer division in 1970, and later maintained by after its purchase of Honeywell's computer business in 1986. GCOS evolved through several to accommodate advancements in hardware and needs, with the mainframes becoming a primary platform in the 1970s and 1980s. Key iterations include early GECOS implementations for 36-bit architecture and later releases like GCOS 7 and GCOS 8, which introduced enhanced support for multiprogramming and multithreading. The system's architecture emphasizes reliability for large-scale , featuring a hierarchical file structure, management, and compatibility with legacy peripherals such as tape drives and high-speed printers. In its modern form, GCOS 8 serves as a multithreading, multiprogramming environment optimized for , , and in mission-critical applications, such as those in and financial sectors. Developed and supported by Bull-Atos Technologies, it has been ported from traditional mainframes to Intel-based servers to extend its lifespan through emulation and , ensuring continued operation of legacy systems without full hardware replacement. As of 2025, GCOS remains approved for use in secure environments like the U.S. Department of , where it complies with federal standards for and .

History

Origins at General Electric

The development of the Comprehensive Operating System, originally known as GECOS, began in 1962 within 's Computer Department, specifically aimed at supporting the newly designed of 36-bit mainframe computers. This initiative marked GE's strategic push into large-scale hardware, building on the company's prior with systems like the ERMA banking computer but focusing on a more versatile software foundation for diverse applications. GECOS was conceived as a comprehensive operating supervisor to manage complex workloads, evolving from GE's internal efforts to create software that could handle the 's advanced architecture, which included features like multiple CPU support and high-speed core memory. The primary motivations for GECOS centered on delivering a robust, batch-oriented operating system tailored for both business data processing and scientific computations on enterprise-level hardware. At the time, GE sought to compete in the growing mainframe market by providing an integrated environment that optimized resource allocation for high-volume operations, emphasizing efficiency in job scheduling and peripheral device management without the limitations of simpler disk operating systems. Although GECOS shared architectural similarities with contemporary systems like IBM's DOS/360—such as support for sequential batch processing—it was designed independently to leverage the GE-600's unique 36-bit word length and transistor-based design, aiming for greater scalability in multiprogramming environments. Initial implementations of GECOS occurred with the first shipments of the , a flagship model in the , starting with a prototype delivered in April 1965 and full installations by August 1965 at key sites including MIT's Project MAC and Bell Telephone Laboratories. Early versions, such as GECOS I and II, introduced foundational capabilities like multiprogramming, which allowed multiple jobs to share system resources dynamically, and basic mechanisms that served as precursors to more advanced virtual addressing concepts. These features enabled efficient handling of batch jobs on the GE-635's up to 1 MB of core memory, supporting applications in research and industry without full paging support at the outset. A significant aspect of GECOS's early evolution involved collaboration with MIT, particularly through Project MAC, where GE engineers contributed to security-oriented innovations that informed the design of starting in 1964. This partnership, involving GE's Cambridge Information Systems Laboratory, focused on enhancing protection rings and access controls in multiprogrammed settings, concepts that extended beyond GECOS to influence secure systems. Following GE's computer division sale to in 1970, GECOS was rebranded as GCOS, paving the way for further adaptations.

Honeywell Acquisition and Early GCOS Versions

In 1970, Honeywell acquired General Electric's computer division for approximately $375 million in notes and stock (1.5 million shares valued at $264.5 million plus $110 million in notes), a move that integrated GE's established mainframe operations into 's portfolio and positioned the company as the second-largest computer manufacturer behind . This acquisition included GE's Phoenix operations and European subsidiaries, driven by GE's struggles with unprofitable computer ventures amid an economic downturn. Following the deal, Honeywell rebranded GE's hardware as the and renamed the General Electric Comprehensive Operating System (GECOS) to the General Comprehensive Operating System (GCOS), preserving GE's legacy while aligning it under 's branding. The renaming to GCOS also facilitated the incorporation of 's prior expertise in , a secure system co-developed with GE and MIT, enhancing GCOS's capabilities in multi-user environments. Early GCOS versions focused on adapting GE's existing software to Honeywell's evolving hardware lineup, particularly the Series 60 family. GCOS 3 emerged as the direct successor to GECOS III, retaining its batch-processing core while supporting the mainframes, which used integrated circuits for improved performance over GE's originals. In 1971, Honeywell introduced the Enhanced Instruction Set (EIS) extension for these systems, boosting computational efficiency and aiding smoother transitions for GE users. These adaptations emphasized continuity, allowing GE customers to migrate applications with minimal disruption through rebranding and minor software updates rather than full rewrites. A pivotal development occurred in 1973 with Honeywell's announcement of enhancements to GCOS 3, including expanded support for and real-time processing via the Series 66 (Level 66) configuration. This update relaunched the 6000 series hardware—based on the 6080 —for delivery in 1975, enabling multidimensional operations like concurrent batch, remote batch, and interactive user sessions on systems capable of handling up to 1 MIPS performance. These features built on GECOS III's foundational capabilities introduced in 1968, positioning GCOS 3 as a versatile platform for enterprise computing. Honeywell marketed early GCOS versions as a competitive alternative to IBM's OS/360, emphasizing architectural similarities in supervisory control and file management to attract users seeking reliable mainframe solutions without vendor lock-in. From 1971 to 1974, Honeywell developed migration tools and software conversion packages, particularly for smaller systems like the IBM System/3, to facilitate data and application transfers to GCOS environments, while larger 6000 series systems offered peripheral compatibility options for IBM channels. This strategy targeted GE's existing customer base and aimed to erode IBM's dominance by highlighting GCOS's cost-effective scalability and Multics-influenced security.

Bull Integration and Later Developments

In 1987, Honeywell Information Systems merged its operations with and , forming the Honeywell Bull Inc. (with equal 42.5% shares for Honeywell and , and 15% for ). This merger preserved the existing GCOS customer base while minimizing further research and development investments, allowing to leverage GCOS for large-scale enterprise applications across and other European countries. gained majority control (65.1%) in 1989 and full ownership by 1991 when it acquired the remaining stakes from Honeywell and , enhancing GCOS's alignment with European standards and export opportunities. During the 1980s and 1990s, GCOS 7 received enhancements focused on distributed processing, including the Distributed Systems Architecture (DSA) introduced in the late 1970s and expanded for networked environments, enabling better interoperability among Bull's DPS 7 and DPS 90 series hardware. GCOS 8, initially launched in 1979 for the DPS 8 mainframes, saw significant updates in 1985 to support advanced 64-bit addressing capabilities on newer architectures like the DPS 90 series, incorporating and ASCII compatibility to run legacy GCOS 3 programs without modification. These improvements positioned GCOS 8 as a robust option for environments, with performance scaling up to 45 MIPS per processor in the DPS 9000/700 by 1997. In the 2000s, Bull introduced emulation and compatibility support for GCOS on Intel-based platforms through the DPS 9000 series, with a key announcement in extending this to the NovaScale 9000 servers using 2 processors, allowing seamless partitioning for GCOS 8 alongside and Windows without recompilation. Key milestones in the included Bull's Y2K compliance initiatives, where updated versions of GCOS operating systems were rolled out to ensure full year readiness by the end of the decade. In the , Bull piloted open mainframe-class systems like NovaScale GCOS to bridge legacy environments with modern infrastructures, supporting hybrid deployments. Corporate shifts continued with 's acquisition of in 2014 for €620 million, integrating Bull's legacy systems expertise into Atos's portfolio while committing to ongoing maintenance of GCOS. As of 2025, Atos (now operating key Bull assets under Eviden) maintains active support for GCOS 8 on compatible hardware, ensuring continuity for enterprise users.

Legacy and Current Status

The legacy of the General Comprehensive Operating System (GCOS) endures through its contributions to early computing concepts, particularly in and user identification standards that influenced subsequent systems. Originally developed as GECOS by , GCOS established frameworks that emphasized efficient job scheduling and for mainframe environments, setting precedents for structured in later operating systems. Additionally, the system's user accounting mechanisms inspired the in Unix /etc/passwd files, which retains compatibility for inter-system communication with GE/Honeywell mainframes, allowing fields for job numbers, office locations, and user IDs to persist in modern systems. GCOS also incorporated features with multiple protection levels akin to ' ring-based architecture, enabling segmented access controls that were refined for government and military applications, though these were less granular than ' implementation. As of 2025, GCOS remains operational primarily through GCOS 8 on emulated DPS 8/M hardware platforms, with support extended via modern mainframes like BullSequana series that virtualize the original 36-bit . (now part of Eviden) continues to provide hardware and , including end-of-support announcements and for GCOS 7 and 8 environments, ensuring compatibility for legacy workloads. Key users include the U.S. Department of , which relies on GCOS 8 for multithreading and in mission-critical applications, as approved in its 2025 Technical Reference Model. Financial institutions maintain GCOS for COBOL-based applications handling high-volume transactions, leveraging its proven reliability despite modernization pressures. Preservation efforts have sustained GCOS accessibility through open-source emulation projects, such as the DPS8M simulator initiated in the , which accurately replicates the underlying /Bull 6000-series hardware to run GCOS-compatible software without proprietary dependencies. These initiatives, combined with 's long-term support contracts for active sites, facilitate archival and educational use while supporting limited production environments. While new deployments have declined due to migrations toward Linux-based mainframe hybrids—such as porting GCOS 7 applications to open platforms for cost efficiency and —GCOS persists in sectors requiring uninterrupted reliability for irreplaceable legacy codebases. This sustained use underscores GCOS's role in high-stakes operations where system stability outweighs the appeal of contemporary alternatives.

Technical Overview

Core System Architecture

The General Comprehensive Operating System (GCOS) features a hierarchical divided into privilege levels, with the kernel, often referred to as the monitor or nucleus, handling core functions such as task dispatching, interrupt management, and , while the executive layer manages higher-level services like command interpretation and subsystem coordination. User-level operations are confined to outer privilege levels to prevent unauthorized access to sensitive system components. GCOS adopts a , allowing separable components for key functionalities including (I/O) handling, , and process scheduling, which enhances and in mainframe environments. These modules, such as reentrant drivers and shareable bound units (comprising root segments and overlays), can be loaded dynamically and shared across processes to optimize memory usage. The memory model relies on segmented , where address spaces are divided into variable-sized segments mapped to physical storage via relocation registers or descriptors, supporting efficient allocation and protection. Early implementations on the used 18-bit addressing for up to 256K words of 36-bit memory, later extended to 24-bit addressing in models like the DPS/8 to accommodate larger address spaces. Subsequent versions incorporated management tools for paging and segmentation, enabling non-contiguous allocation without direct hardware addressing limitations. Process management in GCOS supports multiprogramming through task groups organized by priority levels (ranging from 0 to 63), allowing multiple concurrent jobs to execute while the kernel dispatches based on priority and within equal levels. Each task group manages its own memory pools (exclusive or shared, online or batch), facilitating up to dozens of concurrent activities depending on system configuration, such as four to thirty-two jobs in typical setups. The I/O architecture is channel-based, utilizing dedicated channels or multiplexors to connect peripherals, with device independence achieved through logical units and drivers that abstract physical hardware details. This enables parallel I/O operations, buffering for efficiency, and support for various access methods like sequential or direct, while maintaining compatibility across diverse peripherals.

Key Concepts and Features

The model of the General Comprehensive Operating System (GCOS) relies on an Access Rights mechanism that employs lists (ACLs) to manage permissions for projects, files, directories, and volumes, thereby preventing unauthorized escalations by restricting access based on defined such as OWNER, WRITE, and READ. This project-based approach, administered through the SYSADMIN project, ensures that users and jobs operate within granted scopes, with violations logged in activity files like SYS.ACT1 or SYS.ACT2 for auditing and enforcement. integrates user names, passwords (up to 12 characters), and project associations, validated during logon or job submission to maintain integrity without explicit ring structures, though hierarchical priorities for job classes imply layered protections. Compatibility layers in GCOS facilitate integration with other systems, notably through the in Unix /etc/ files, originally designed to hold login information for submitting batch jobs to GCOS mainframes at , enabling legacy user . Additionally, GCOS provides robust support for business-oriented languages via dedicated compilers for and , allowing compilation and execution of applications in these environments while maintaining compatibility with earlier system versions through intermediate code generation. GCOS operates in a hybrid mode that combines and , supporting interactive access for multiple users via the Interactive Operation Facility (IOF) and GCL commands on terminals, alongside management for non-interactive workloads submitted through JCL. This dual capability allows concurrent execution of up to 48 users in sessions while handling batch jobs across six phases—input, scheduling, allocation, execution, termination, and output—optimizing resource use in multi-user environments. Error handling in GCOS emphasizes comprehensive logging and automated recovery, with incidents such as program aborts or I/O failures recorded in files like SYS.ERLOG and SYS.SWLOG, including details on return codes (e.g., JRNAL for before-journal errors) and abnormal events reported to the console or SYSOUT. Recovery leverages checkpoints—synchronization points in batch/IOF steps or TDS commitment units—to enable rollback using before-journals (restoring to the last consistent state) or rollforward with after-journals (advancing to the next stable point), supported by utilities like ROLLFWD and JRU for dynamic or deferred restoration post-crash. These mechanisms ensure data integrity, with automatic file switching and space release after checkpoints to minimize downtime. Networking in GCOS incorporates the Distributed Processing System (DPS) protocol framework, introduced in the for GCOS 7 on DPS 7000 platforms, enabling distributed clusters through OSI and DSA addressing with session control identifiers (SCID) for secure inter-system communication. The XCP2 protocol facilitates program-to-program interactions across up to 5,000 remote systems and 10,000 correspondents, using configurable session pools (default MAXSESS=10, up to 5,000) and buffer management for reliable file transfers and in clustered environments. Configurations via NETGEN support passthroughs and neighbors over ISL/PSI links, allowing incremental updates without interrupting operations in 1980s-era distributed setups.

Versions and Variants

GCOS 3

GCOS 3, originally developed as GECOS III by and renamed following Honeywell's 1970 acquisition of GE's computer division, served as the core operating system for the mainframes. It was specifically tailored for the Series 60 Level 66 systems, which were introduced in April 1974 to extend the 6000 series with improved compatibility and performance for commercial and scientific environments. These systems emphasized reliable batch-oriented for large-scale data handling in business applications. The operating system featured robust enhancements, enabling efficient job queuing, , and execution in multi-programming environments to support high-volume . Basic was available through optional extensions like the Time-Sharing System package, allowing multiple users to interact with the system via terminals for interactive debugging and data entry, though it remained primarily batch-focused compared to contemporaries like . was constrained by the era's hardware, typically supporting configurations up to several megabytes across models, with the Level 66 lineup offering scalable core storage from 65K to over 1 million 36-bit words depending on the variant. At its core, GCOS 3 utilized a organized into catalogs and files, facilitating structured and access in a tree-like directory model that improved organization for complex applications. This system supported both fixed-length and variable-length records, enabling flexible handling of diverse data formats such as sequential files for batch jobs and indexed files for database-like operations, with built-in utilities for file creation, maintenance, and protection. GCOS 3 entered a phase-out period in the late as Honeywell shifted focus to successor systems, though legacy installations persisted into the 1990s through hardware upgrades and software patches. Emulation efforts have since preserved its functionality in modern environments for archival and specialized legacy applications. Migration tools and compatibility layers were developed during the and to transition applications to advanced versions like GCOS 8, preserving file systems and job control structures to minimize disruption for users moving to newer hardware platforms.

GCOS 7

GCOS 7, introduced in 1981 for the DPS 7 series of medium-scale mainframes, represented a significant evolution in the GCOS family, building on -inspired designs to support more demanding commercial environments. Announced on October 14, 1981, with initial deliveries starting in early 1982 for models like the DPS 7/45, 7/55, and 7/65, it targeted transaction-oriented applications in industries such as banking and . The system ran on hardware compatible with concepts, including segmented addressing and protection rings, enabling efficient resource sharing in multi-user settings. Key advancements in GCOS 7 included enhanced real-time processing capabilities through the Transaction Driven System (TDS/64), which allowed concurrent handling of batch, transactional, and workloads with up to 64 jobs. It featured 32-bit addressing with segment-relative mechanisms, enabling larger address spaces compared to earlier versions and supporting dynamic relocation of program segments. was improved via a distributed that integrated CPU and peripheral processors, using firmware-implemented semaphores for and handling, which facilitated scalable configurations up to multiple processors. For database support, GCOS 7 integrated the DPS/VS virtual storage environment with tools like DM-IV and the Integrated Data Store II (I-D-S/II), a CODASYL-compliant network database optimized for high-volume across up to 15 communication lines with 32 terminals each. In terms of lifecycle, GCOS 7 received year 2000 (Y2K) compliance updates in 1999, incorporating four-digit year support (ranging from 1961 to 2060) in its General Control Language (GCL) and dedicated testing functions like Y2KTEST for validating applications without disrupting production. These enhancements, including a "61 rule" for interpreting two-digit years (YY < 61 as 20YY, otherwise 19YY), ensured continued reliability into the new . Support for GCOS 7 persisted through the under (later ), with maintenance releases documented as late as 2003 and security updates available into the 2020s; as of November 2025, it remains supported on platforms like BullSequana MH servers. Unlike GCOS 3, which was oriented toward with limited addressing, GCOS 7 introduced interrupt-driven I/O managed through semaphores rather than direct hardware interrupts, along with expanded 32-bit address spaces and to accommodate growing multi-user and real-time demands. This shift positioned GCOS 7 as a transitional system toward more advanced 64-bit architectures, emphasizing efficiency in commercial transaction environments.

GCOS 8

GCOS 8, developed by following the integration of Honeywell's systems, represents the evolution of the General Comprehensive Operating System lineage into a robust, -based operating system tailored for mid-to-large-scale mainframe environments. Initially released in June 1987 alongside the DPS 8000 series hardware, with Software Release 3000 becoming available in December of that year, GCOS 8 introduced advanced capabilities and hardware-transparent virtual memory management to support demanding commercial workloads. This version marked a significant upgrade from prior iterations, emphasizing compatibility with existing GCOS 8 software without requiring recompilation, thereby facilitating seamless migrations for users transitioning from earlier releases like SR 2500. At its core, GCOS 8 employs a segmented virtual addressing scheme, where each segment can span up to 4 billion bytes, organized into up to 512 workspaces comprising 4 million 4096-byte pages each, enabling efficient across multiprogrammed environments. The system supports with configurations ranging from single-processor setups (e.g., Model 81) to dual-processor models (e.g., Model 82T), paired with main memory capacities from 16 MB to 256 MB in its initial implementations, leveraging VLSI for enhanced performance through multipipeline instruction execution and memory interleaving. Key features include support for , , and via integrated monitors like CTP and TDS, with the Rapid Access Data System (RADS) optimizing throughput for high-volume data operations. In modern deployments on Bull's NovaScale series, GCOS 8 extends to 64-bit architectures, such as Intel Itanium-based systems, allowing up to four dedicated processors and 4 GB of memory allocation per instance for improved scalability in mixed-OS environments. As the flagship variant of the GCOS family, GCOS 8 continues to receive active development and support from (formerly ) as of November 2025, powering mission-critical applications on dedicated mainframe servers like the BullSequana M series, which integrate GCOS 8 alongside Windows and for hybrid workloads. These platforms enable terabyte-scale storage configurations and multi-node setups for enterprise-scale , maintaining with legacy GCOS 8 binaries to preserve decades of invested software assets. Emulation efforts, such as the open-source DPS8/M simulator, provide a pathway for running historical GCOS 8 environments on x86 platforms, though full production support remains tied to hardware; ongoing community interest hints at potential extensions to architectures for archival and testing purposes. Unlike GCOS 7, which operates on distinct 32-bit branches, GCOS 8's architecture prioritizes 36-bit and later 64-bit virtual addressing for real-time and high-availability scenarios in industrial and deployments.

Other Systems Named GCOS

In the late 1960s, General Electric developed the Mark III time-sharing system as part of its Information Systems Division offerings, which provided remote access to computing resources via dial-up terminals for business and scientific applications. This system, launched around 1968, operated independently as a service-oriented platform based on the Dartmouth Time-Sharing System and ported to GE-600 hardware, without direct lineage to the core GECOS/GCOS supervisor for the GE-600 series mainframes. Unlike the mainline GCOS, which focused on batch processing and later incorporated elements of time-sharing from GECOS III, Mark III emphasized commercial time-sharing services and did not evolve into subsequent Honeywell-supported versions. During the 1970s, Corporation in licensed technology from (successor to GE's computer division) to adapt GCOS for its domestic market, resulting in the ACOS series operating systems. Specifically, 's ACOS-4, introduced with the ACOS/S-400 hardware in 1975, was built on GCOS 64 as its foundational layer, enabling compatibility with 's while incorporating Japanese-specific enhancements for in manufacturing and finance sectors. Later iterations, such as ACOS-6, drew from licensed GCOS-3 code, featuring custom file management systems optimized for 's hardware architecture, including hierarchical file structures tailored to character handling and high-volume transaction logging not present in the original GCOS. These adaptations maintained binary compatibility for select GCOS applications but diverged in networking protocols to align with 's emerging standards for inter-system communication. As of November 2025, continues to support and develop ACOS-4 for modern mainframes. In the 1980s, unofficial implementations of GCOS appeared in educational and hobbyist contexts, primarily through third-party emulators and simulators developed for training purposes. Honeywell released the GCOS Environment Simulator in , a software tool that emulated core GCOS behaviors on smaller host systems to facilitate and system familiarization without requiring full mainframe access. Independent clones emerged in academic settings, such as university labs adapting GCOS-like interfaces for minicomputers to teach operating system principles, though these lacked official support and often simplified for pedagogical use. These non-official systems differed markedly from /Bull's core GCOS lineage in security architecture and historical influences. While official GCOS incorporated segmented inspired by early collaborations during the GE era, variants like Mark III and NEC's ACOS omitted the advanced ring-based security model—' hierarchical privilege rings (0-7) for controlled access to sensitive operations—which GCOS partially adopted in its supervisor mode but not to the same granular extent. Consequently, these peripheral namings prioritized compatibility and localization over the robust, ties to that defined official GCOS's evolution toward enterprise reliability.

Hardware and Peripherals

Supported Hardware Platforms

The General Comprehensive Operating System (GCOS) originated on the mainframes developed by in the mid-1960s. These 36-bit systems, including models like the GE-635 and GE-625, featured core memory capacities ranging from 32,768 words (approximately 144 KB) to 262,144 words (approximately 1.18 MB) and were designed for and multiprogramming environments. GCOS, initially known as GECOS, provided comprehensive support for these machines, enabling efficient handling of scientific and commercial workloads through its modular architecture. Although the GE-400 series (24-bit minicomputers introduced in 1965) utilized an early variant of GECOS for smaller-scale operations, full GCOS compatibility was primarily aligned with the larger GE-600 line. Following Honeywell's acquisition of GE's computer division in 1970, GCOS was adapted for the , which maintained the 36-bit architecture while introducing enhancements such as faster cycle times and expanded I/O capabilities. Models like the Honeywell 6180 supported up to 2 MB of core memory and integrated peripherals for real-time processing. Concurrently, the Honeywell Series 60 Level 6 systems in the 1970s represented a shift toward 16/32-bit hybrid architectures, with GCOS 6 providing upward compatibility from earlier Level 6 minicomputers; these platforms offered modular expansions up to 1 MB of , targeting business applications. In the and , under (which acquired Honeywell's computer operations), GCOS evolved to support the DPS 7 and DPS 8 families. The DPS 7 series, running GCOS 7, comprised midrange 36-bit systems with capabilities and memory up to 64 MB, suitable for in industrial settings. The DPS 8 line, under GCOS 8, extended to larger configurations with up to 256 MB of memory and multiple CPUs. By the late , the Bull DPS 9000 series introduced vector processing based on licensed technology, maintaining binary compatibility with prior 36-bit GCOS 8 systems while supporting up to 512 MB of memory and high-speed vector operations for compute-intensive tasks. As of 2025, GCOS continues on modern hardware through dedicated servers like the NovaScale 70xx series (Intel x86-based) for GCOS 7 and NovaScale 9000 equivalents for GCOS 8, ensuring legacy application portability without performance degradation in emulated modes. As of 2025, the BullSequana M9600 series uses Scalable processors in modular configurations supporting up to multiple terabytes of and petabyte-scale storage via SSD emulation for GCOS 8. Open-source emulation via the DPS8/M simulator enables GCOS execution on contemporary x86 platforms, replicating the 36-bit architecture of / systems with sufficient fidelity for testing and archival purposes; this tool supports models such as the Honeywell 6180 and DPS 8, running full GCOS instances at speeds approaching original hardware under optimized conditions. 's Escala PowerPC servers provide interoperability layers for GCOS front-ends, facilitating hybrid environments with AIX-based systems.

Storage Units and Data Management

GCOS 8 employs a hierarchical storage that integrates , cache, devices such as disks and magnetic tapes, and shared subsystems for enhanced data accessibility and performance. Primary storage units include disk drives like the MSU0400 series, which utilize removable Type 4451 disk packs offering capacities of 78 million 9-bit bytes per pack, and higher-capacity fixed units such as the MSU0501 with up to 1.1 billion 9-bit bytes across dual spindles. Magnetic tapes, primarily 9-track configurations, support densities of 800 or 1600 bits per inch (bpi) via devices like the MTU0600, enabling transfer rates up to 320,000 bytes per second for archival and backup operations. The in GCOS 8 is managed by the Unified File Access System (UFAS), which provides device-independent access to sequential, relative, indexed, and integrated file organizations, incorporating buffer management and error recovery mechanisms. A key component is the Indexed Sequential Access Method (ISAM), implemented through the Indexed Sequential Processor (ISP), allowing efficient random and via key-based indexing for database and applications. File Management Supervisor (FMS) oversees cataloging, space allocation, and multi-level access controls, ensuring compatibility across batch, , and remote processing environments. Data management features emphasize reliability through Shared Mass Storage (SMS), which enables up to four DPS 8 systems to access common disk volumes in clustered configurations, providing via dynamic load balancing and access queuing. is further supported by error-correcting Hamming codes in and instruction retry capabilities for transient I/O faults, though explicit implementations are not standard; instead, dual checkpoints on files facilitate program recovery. Volume sets allow concatenation of multiple physical units into logical entities for large datasets, managed transparently by FMS to maintain during transfers or failures. In GCOS 8 implementations, high-speed I/O is facilitated by Multiplexers (IOMs) and Peripheral Subsystem Interfaces (PSI), supporting data rates up to 2 million bytes per second across up to 32 disk drives and 16 tape units per channel, with to petabyte-level storage through compatible enterprise arrays. Later enhancements on platforms, such as the DPS 9000 series, integrate ESCON and FICON channels for fiber-optic connectivity to modern storage subsystems, enabling sustained throughput for large-scale data operations. By the , solid-state caching was introduced in Bull's NovaScale and servers running GCOS 8, improving access latencies, while 2025 configurations on BullSequana M9600 leverage SSD-based emulations for legacy peripherals, maintaining compatibility with original and tape formats at terabyte-to-petabyte scales. The evolution of GCOS storage traces back to the 1960s GE-600 series, which relied on magnetic drums for secondary storage alongside early disk and 7-track tape units under initial GECOS variants. By the Honeywell 6000 era, core memory supplemented by drum-backed paging gave way to dedicated disk subsystems in GCOS, culminating in the virtual memory optimizations of GCOS 8 on DPS 8 hardware from 1979 onward.

Applications and Deployments

Commercial and Industrial Applications

GCOS systems have been widely adopted in commercial environments for COBOL-based () applications, particularly in sectors from the 1970s through the 2000s. These implementations focused on core business functions such as inventory management, processing, and production scheduling, leveraging GCOS's robust support for to handle large-scale batch operations on mainframes like the DPS series. For instance, provided pre-packaged tailored for workflows, enabling automotive and industrial firms to integrate across supply lines and financial modules for improved operational efficiency. In the realm of , GCOS excelled in banking applications during the 1980s, with subsystems like the Transaction Driven Subsystem (TDS) facilitating (OLTP) for high-volume financial operations. Running on GCOS 8 platforms such as the DPS 8000 series, these systems supported tasks including account management and payment processing in European and U.S. institutions. Bull's GCOS installations served thousands of large customers in , with early adopters benefiting from its multi-threading capabilities to manage peak loads without downtime. GCOS 7 and GCOS 8 variants found significant use in industrial control applications, particularly for real-time monitoring in utilities during the late . The TDS environment on GCOS 7 enabled transaction-based real-time processing, allowing utilities to track distribution, monitor equipment status, and respond to operational anomalies in near real-time. This capability supported multitasking and data communications in online configurations, ensuring reliable performance for like power grids and water management. As of 2025, GCOS remains in legacy support for compliance-intensive commercial applications, including in and . Modernized variants on BullSequana servers continue to underpin batch and OLTP workloads, ensuring regulatory adherence for data-intensive processes like and auditing in global supply networks.

Government and Legacy Installations

The U.S. Department of Veterans Affairs (VA) has utilized GCOS 8 since the 1980s, with the system remaining authorized under the VA's Technical Reference Model (TRM) as of 2025. This deployment supports , , and transaction-oriented environments critical to VA operations, ensuring reliable data handling for veteran services. Military applications of GCOS date to the early 1970s, when secured contracts with the U.S. Department of Defense to deploy the system within the World Wide Military Command and Control System (WWMCCS) for and command functions. These implementations provided robust batch and real-time processing support for defense , with modifications to GCOS enabling secure, distributed operations across military sites. As of 2025, GCOS installations persist globally, predominantly in emulated environments on modern hardware such as Bull's NovaScale series, including deployments in utilities for legacy . Emulation allows continued operation without full hardware replacement, preserving specialized applications in sectors resistant to modernization. Migration from GCOS presents significant challenges, with cost-benefit analyses for legacy mainframe systems indicating a for retention over full replacement due to high upfront refactoring costs and ongoing maintenance efficiencies. These evaluations highlight the economic rationale for phased emulation strategies in government and legacy contexts, balancing stability against modernization pressures.

Documentation

Official Manuals and Guides

The official documentation for GCOS, produced by and later , encompasses a range of manuals designed for system administrators, programmers, and operators. Core manuals include the GCOS 8 OS System Startup manual from 1987, which details procedures for initializing and restarting systems, including aspects of kernel configuration and tuning relevant to performance optimization. These documents, often exceeding 500 pages in length, provide in-depth guidance on low-level system operations, such as and process scheduling, tailored to the DPS 8 hardware architecture. User guides focus on practical operations, particularly the Job Control Language (JCL), a command-based system analogous to IBM's JCL for and job submission. The JCL Reference Manual for GCOS 7, updated in October 2010, outlines syntax and parameters for job execution, data handling, and error recovery, serving as a primary resource for programmers managing workflows. Complementing this is the JCL User's Guide from August 2011, which includes examples for integrating JCL with GCOS utilities like file allocation and program linking, emphasizing efficient resource utilization in multi-user environments. Installation documentation addresses hardware integration, particularly for the DPS 8 series. The DPS 8 System Manual from August 1982 describes the physical composition of the , including the central processor unit, main unit, and input/output , with guidelines for cabling and initial sequences to ensure compatibility with GCOS 8. These guides incorporate diagrams for peripheral connections, such as tape drives and disk units, and step-by-step verification processes to prevent configuration errors during deployment. Access to these materials remains controlled through Bull's On-line Support Portal, which as of 2025 provides PDF downloads exclusively to licensed customers and maintenance contract holders for active GCOS installations. Historical versions are available via public archives, including scans of 1980s-era manuals hosted on sites like bitsavers.org, allowing preservation and limited non-commercial reference without vendor restrictions. The evolution of GCOS documentation transitioned from printed paper volumes in the 1960s and 1970s—such as early series manuals distributed in bound formats—to digital PDFs by the , coinciding with the adoption of electronic distribution for updates and revisions. This shift facilitated easier revisions and global access for Bull's international clientele, with modern formats incorporating searchable text and hyperlinks for enhanced usability.

Historical and Modern Resources

The Bitsavers project maintains an extensive archive of GECOS and GCOS materials from the , including scanned manuals, system documentation, and software distributions that serve as key artifacts for researchers studying the operating system's early evolution. Similarly, the IT History Society provides online resources on GCOS development, drawing from historical records of its origins at . The Computer History Museum's digital archives include correspondence and technical documents related to GCOS design and implementation during the Honeywell era. These non-official collections complement vendor documentation by offering preserved primary sources for academic and hobbyist analysis. Emulation tools for exploring GCOS are limited but include open-source projects targeting the underlying 36-bit hardware architecture, such as the DPS8/M simulator, which has been available since the mid-2000s and supports running legacy environments on modern hardware; its Release 3.1.0 from May 2025 includes performance improvements and bug fixes. Tutorials for setting up the DPS8/M emulator, including configuration for related 6000-series systems, are hosted on the heritage site, enabling users to experiment with compatible software and understand GCOS-compatible peripherals. Proprietary emulation from / also allows GCOS applications to run on contemporary servers, though community-driven open-source efforts like DPS8/M provide accessible entry points for non-commercial study. Online forums and communities focused on GCOS include Bull user groups accessible via the Atos support portal, where legacy system administrators share experiences and troubleshooting tips. Discussions on legacy operating systems like GCOS also occur in broader online venues, fostering knowledge exchange among enthusiasts. The FEB Patrimoine archive offers additional community-curated historical overviews of GCOS evolution. Modern resources for GCOS include whitepapers from Atos on mainframe modernization and cloud migrations. Books providing context on GCOS include "A Personal History in Mainframe Computers" by Russell C. McGee (2013), which features detailed appendices and discussions on GCOS variants alongside , drawing from the author's experiences with systems. Earlier works like the seminal paper collection in ": The First Seven Years" (reprinted in various editions through the 1980s) reference GCOS integrations and shared hardware influences.

References

  1. https://www.ithistory.org/resource/general-comprehensive-operating-system
  2. https://www.pcmag.com/encyclopedia/term/gcos
  3. https://www.oit.va.gov/Services/TRM/ToolPage.aspx?tid=10112
  4. https://www.smecc.org/ge_information_systems.htm
  5. https://www.computinghistory.org.uk/sec/15518/General-Electric/
  6. https://www.computer-dictionary-online.org/definitions-g/gcos
  7. https://multicians.org/ge635.html
  8. https://gunkies.org/wiki/GE_635
  9. https://www.nytimes.com/1970/08/20/archives/us-allows-ges-sale-of-computer-business-to-unit-of-honeywell-ge-can.html
  10. https://www.nytimes.com/1970/05/21/archives/computer-field-to-get-new-giant-ge-and-honeywell-to-form.html
  11. https://time.com/archive/6816756/computers-challenging-the-jolly-gray-giant/
  12. https://www.histo.cat/sabir/GE-Honeywell-Bull-from-GECOS-to-GCOS8
  13. https://gunkies.org/wiki/Honeywell
  14. https://www.computerhistory.org/brochures/g-i/honeywell-information-systems-inc/
  15. http://web.mit.edu/srz/www/multics-glossary.html
  16. https://gunkies.org/wiki/Honeywell_6000_series
  17. http://bitsavers.org/pdf/honeywell/Competitive_Timesharing_Offerings_May79.pdf
  18. http://ftpmirror.your.org/pub/misc/bitsavers/pdf/datapro/datapro_reports_70s-90s/Honeywell_Bull/70C-480-12_7708_Honeywell_Series_60_Level_62_64.pdf
  19. https://multicians.org/history.html
  20. https://www.afr.com/companies/honeywell-cuts-ties-with-computer-industry-19910419-k4c36
  21. https://www.upi.com/Archives/1988/12/30/Groupe-Bull-takes-majority-of-Honeywell-Bull/2089599461200/
  22. https://www.nytimes.com/1991/04/17/business/company-news-honeywell-to-sell-bull-its-stake-in-venture.html
  23. https://bitsavers.computerhistory.org/pdf/datapro/datapro_reports_70s-90s/Honeywell_Bull/70C-458MM-80_8610_Honeywell_DPS_90.pdf
  24. https://www.hpcwire.com/2004/06/18/bull-extends-novascale-range-w-novascale-6000-9000-servers/
  25. https://techmonitor.ai/technology/bull_with_necs_help_opens_up_speeds_up_gcos_mainframes_1
  26. https://www.bloomberg.com/news/articles/2014-05-26/atos-offers-844-million-to-acquire-bull-in-cybersecurity-push
  27. https://www.tuhs.org/pipermail/tuhs/2017-December/014070.html
  28. https://csrc.nist.gov/files/pubs/conference/1998/10/08/proceedings-of-the-21st-nissc-1998/final/docs/early-cs-papers/karg74.pdf
  29. https://dps8m.gitlab.io/
  30. https://support.bull.com/ols/product/platforms/dps7000/ns7xxx/doc/doc-list/folder_contents
  31. https://www.infosol.com/solutions/cobol-migration/
  32. https://dps8m.gitlab.io/blog/
  33. https://eviden.com/solutions/enterprise-servers/mainframe-servers/
  34. https://www.bonede.com/fr/success-stories/from-bull-gcos-7-to-linux--dehner-gartencenter-group-61-22-0.html
  35. https://bitsavers.trailing-edge.com/pdf/honeywell/small_systems/series60level6/gcos6/CB20_GCOS_6_MOD_400_System_Concepts_Jan1978.pdf
  36. https://support.bull.com/ols/product/system/gcos7/gcos7-com/g7-dps7000/doc-com/docf/g/47X257TN23-mar2005/doc/34ula10.pdf
  37. http://www.bitsavers.org/pdf/honeywell/large_systems/GCOS/DD19-01_GCOS_Manual_198008.pdf
  38. https://support.bull.com/ols/product/system/gcos7/gcos7-com/g7-dps7000/doc-com/docf/g/47X257TN26-jun2007/40A461CF01.pdf
  39. https://bitsavers.trailing-edge.com/pdf/honeywell/medium_systems/Level_64_GCOS/AQ11-01_Level_64_Job_Control_Language_197809.pdf
  40. https://support.bull.com/ols/product/system/gcos7/gcos7-com/g7-dps7000/doc-com/docf/g/47X257TN27-oct2009/47A253US08.pdf
  41. https://support.bull.com/ols/product/system/gcos7/gcos7-com/g7-dps7000/doc-com/docf/g/47X257TN30-aug2011/47A254US02.pdf
  42. https://docs.oracle.com/cd/E19683-01/817-6958/userconcept-97366/index.html
  43. http://bitsavers.trailing-edge.com/pdf/honeywell/large_systems/GCOS_8/GCOS_8_Operator_Training_Student_Handbook_198712.pdf
  44. https://support.bull.com/ols/product/system/gcos7/gcos7-com/g7-dps7000/doc-com/docf/g/47X257TN23-mar2005/doc/37ufa05.pdf
  45. https://support.bull.com/ols/product/system/gcos7/gcos7-com/g7-dps7000/doc-com/docf/g/47X257TN29-oct2010/47A293UC04.pdf
  46. http://bitsavers.org/pdf/honeywell/large_systems/GCOS/BS01_GCOS_Time-Sharing_System_General_Information_197201.pdf
  47. http://bitsavers.org/pdf/datapro/datapro_reports_70s-90s/Honeywell_Bull/70C-480-13_7910_Honeywell_Series_60_Level_66_68.pdf
  48. https://apps.dtic.mil/sti/tr/pdf/ADA044939.pdf
  49. http://bitsavers.org/pdf/honeywell/large_systems/dps-8/Honeywell_Large_Systems_Product_Guide_198411.pdf
  50. https://bitsavers.trailing-edge.com/pdf/datapro/datapro_reports_70s-90s/Honeywell_Bull/70C-480-09_8303_Honeywell_DPS_7.pdf
  51. http://www.mindpride.net/root/Extras/History/OS/history_of_multics.htm
  52. https://bitsavers.trailing-edge.com/pdf/honeywell/medium_systems/dps7000/47A253US07_GCOS7_System_Operators_Guide_200305.pdf
  53. https://support.bull.com/ols/product/system/gcos7
  54. http://bitsavers.org/pdf/datapro/datapro_reports_70s-90s/Honeywell_Bull/70C-115KM-60_8711_Bull_DPS_8000.pdf
  55. https://multicians.org/dps8m-emulator-presentation-text.pdf
  56. http://www.bitsavers.org/components/signetics/2650/Application_Memo_SP54_-_Support_Software_For_Use_With_GE_Mark_III_Timesharing_System.pdf
  57. http://bitsavers.informatik.uni-stuttgart.de/pdf//datapro/datapro_reports_70s-90s/Honeywell_Bull/70C-115KM-50_8708_Bull_DPS_7000.pdf
  58. http://www.1000bit.it/ad/bro/honeywell/HoneywellBullNecRelationship.pdf
  59. http://www.bitsavers.org/pdf/honeywell/large_systems/multics/AN05-02A_gcosSim_Dec85.pdf
  60. https://www.acsac.org/2002/papers/classic-multics-orig.pdf
  61. https://ftpmirror.your.org/pub/misc/bitsavers/pdf/datapro/datapro_reports_70s-90s/Honeywell_Bull/70C-480-11_8012_Honeywell_DPS_8.pdf
  62. https://bitsavers.org/pdf/honeywell/large_systems/GCOS/DD19-01_GCOS_Manual_198008.pdf
  63. https://support.bull.com/ols/product/system/gcos7/gcos7-com/g7-dps7000/doc-com/docf/g/47X257TN29-oct2010/77A762UP00.pdf
  64. https://bitsavers.org/pdf/honeywell/large_systems/GCOS/BS01_GCOS_Time-Sharing_System_General_Information_197201.pdf
  65. ftp://ftpmirror.your.org/pub/misc/bitsavers/pdf/datapro/datapro_reports_70s-90s/Honeywell_Bull/70C-115JE-40_8909_Bull_DPS_8000.pdf
  66. http://bitsavers.org/pdf/honeywell/HoneywellBull_Product_Family_1988.pdf
  67. https://slksoftware.com/blog/how-to-modernize-mainframe-in-banking-without-disrupting-businesses/
  68. https://support.bull.com/ols/product/system/gcos7/gcos7-com/g7-dps7000/doc-com/docf/g/47X257TN30-aug2011/47A226UT00.pdf
  69. https://www.gao.gov/assets/lcd-80-22.pdf
  70. https://www.longpelaexpertise.com.au/ezine/OtherMainframes.php
  71. https://www.epam.com/insights/blogs/mainframe-modernization-roi-a-cost-focused-guide-for-businesses
  72. https://www.quinnox.com/blogs/legacy-mainframe-modernization/
  73. https://bitsavers.trailing-edge.com/pdf/honeywell/large_systems/GCOS_8/DH18-03_GCOS_8_OS_System_Startup_198708.pdf
  74. https://support.bull.com/ols/product/system/gcos7/gcos7-com/g7-dps7000/doc-com/docf/g/47X257TN29-oct2010/47A211UJ04.pdf
  75. https://support.bull.com/ols/product/system/gcos7/gcos7-com/g7-dps7000/doc-com/docf/g/47X257TN30-aug2011/47A212UJ03.pdf
  76. https://bitsavers.org/pdf/honeywell/large_systems/dps-8/58009906-040_DPS8_System_Manual_198208.pdf
  77. http://bitsavers.org
  78. https://archive.computerhistory.org/resources/access/text/2019/02/102785372-05-03-acc.pdf
  79. https://gitlab.com/dps8m/dps8m/-/wikis/DPS8M-R3.1.0-Release-Notes
  80. https://multicians.org/simulator.html
  81. http://www.feb-patrimoine.com/english/bull_computer_index.htm
  82. https://www.ed-thelen.org/McGee_Book-4.2.2.pdf
  83. http://web.mit.edu/saltzer/www/publications/f7y/f7y.html
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.