General Comprehensive Operating System

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

General Comprehensive Operating System (GECOS)
DeveloperGeneral Electric, Honeywell, Groupe Bull, Atos
Working stateCurrent
Initial release1962 (1962)
Latest releaseGCOS 8
Licenseproprietary
Official websiteatos.net/en/products/enterprise-servers/bullsequana-m

The original version of GCOS was developed by General Electric from 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

GECOS

The GECOS operating system was developed by General Electric for the 36-bit GE-635 in 1962-1964 and renamed GECOS II[5] in November 1965. It bore a close resemblance architecturally to IBSYS on the IBM 7094 and less to DOS/360 on the System/360. However, the GE-635 architecture was very different from the IBM System/360 and GECOS was more ambitious than DOS/360. GECOS-II 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.

Honeywell GCOS 3

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

One notable use of GCOS was for the United States Worldwide Military Command and Control System (WWMCCS) in the 1960s.[8][9][10][11][12][13][14][15][16][17][18][19][20][21][22][23][24][25]

GCOS 64

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 a parallel development called Multics, was designed by Honeywell and Honeywell Bull developers in France and Boston.

GCOS 61/62

GCOS-62, 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), and 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

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, 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.

Legacy

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. 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 and based on Itanium 2 processors, runs 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. GCOS 7 has also been ported to a lower-end Xeon-based platform, while Bull has publicly stated that GCOS 8 will continue to be developed for Itanium systems. Bull continues to invest development money in support of both GCOS 7 and GCOS 8, and still has customers in countries around the world. 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. 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.

Applications

GCOS 3 (and later GCOS 7 and GCOS 8) featured a good Codasyl "relational" database called Integrated Data Store (IDS) that was the model for the more successful IDMS.

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, as in Unix, 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

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.

Although GCOS has a basic architecture similar to that of the IBM 360 and earlier IBM 7090 Series, which was abandoned by IBM for the 360, and subsequent operating systems with which it competed, it was also heavily influenced by projects such as MEDINET, Multics, and WWMCCS, 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.

GCOS is a process-oriented OS, in which each process hosts one or more execution threads and executes in its own virtual memory space. 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.

GCOS requires specific hardware designed for the operating system, although the most recent machines capable of running the OS do so through emulation. 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 shared a great deal 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, FORTRAN 68, CORAL 66, FORTRAN 77,[26] and B.[27]

GCOS8 Storage Units

We have become accustomed to an almost universal terminology for units of storage. Modern terminology 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 colourful units of its own, as follows:

Unit[28][29] Full Name Meaning Generic Equivalent[30]
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 (00)16 to (FF)16 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).

Notes
  1. The title of the manual[1] was GE-635 Comprehensive Operating Supervisor but the text referred to it as General Comprehensive Operating Supervisor.
gollark: I mean, yes, you can just use the FPGA to run a CPU but worserer, but no.
gollark: No idea!
gollark: As well as TLS, TCP/IP, and all the other things.
gollark: Oh, very!
gollark: No, that would be uncool, directly implement HTTP parsing in transistors.

See also

References
  1. "GE-635 Comprehensive Operating Supervisor" (PDF), The Compatibles/600, General Electric, July 1964, CPB-1002
  2. JNC @ Gunkies.org (2017). "Honeywell 6000 series". Most 6000 series machines ran GCOS (General Comprehensive Operating System), an evolution of the earlier GECOS (General Electric Comprehensive Operating Supervisor) - early Honeywell documentation continued to call it GECOS.
  3. "GCOS". An operating system developed by General Electric from 1962; originally called GECOS (the General Electric Comprehensive Operating System).
  4. "Bull launches its new mainframe family gcos 7 systems leveraging Extreme Computing technologies". September 29, 2011. This makes novascale 7010 servers the most open on the market, along with Bull's novascale 9010 family running gcos 8.
  5. Ed Thelen, General Electric Computer Department from the bottom up 1961 through 1965
  6. Enterprise, I. D. G. (23 May 1983). "Computerworld". IDG Enterprise – via Google Books.
  7. Nutt, Gary J. (3 March 1979). "A Survey of Remote Monitoring". U.S. Department of Commerce, National Bureau of Standards – via Google Books.
  8. Technology, Institute for Computer Sciences and (3 March 1977). "A survey of eleven government-developed data element dictionary/directory systems". U.S. Dept. of Commerce, National Bureau of Standards – via Google Books.
  9. Hosaka, M.T. "ARMY WWMCCS INFORMATION SYSTEM (AWIS): A STRATEGIC COMMAND AND CONTROL SYSTEM" (PDF). Defense Technical Information Center. Retrieved June 19, 2020.
  10. M. Wallack, Barry; H. Gero, George (1 September 1978). "Worldwide Military Command and Control System (WWMCCS). H-6000 Tuning Guide. Volume III. TSS Response Time Analysis Procedures": 110 – via ResearchGate. Cite journal requires |journal= (help)
  11. https://www.cia.gov/library/readingroom/docs/CIA-RDP96B01172R000600070004-6.pdf
  12. "WWMCCS - OS-Tan Collections Wiki". www.ostan-collections.net.
  13. "Groupe BULL chronology". www.feb-patrimoine.com.
  14. "The 'Bun Reunion - Celebrating the 1970's Roots of the Digital Age - Randall Howard". randalljhoward.com.
  15. Defense Technical Information Center (1 February 1977). "DTIC ADA039111: WWMCCS H6000 Multiprocessor Performance Evaluation. Volume I." – via Internet Archive.
  16. http://tech.uh.edu/conklin/docs/B2-Security-Evaluation.pdf
  17. ftp://ftp.stratus.com/vos/multics/tvv/security-eval.html
  18. https://fas.org/nuke/guide/usa/c3i/jopes/jfm_10.htm
  19. https://www.gpo.gov/fdsys/pkg/GOVPUB-C13-3b9965342f49a3936fa087a4e0cb6d58/pdf/GOVPUB-C13-3b9965342f49a3936fa087a4e0cb6d58.pdf
  20. http://www.ideals.illinois.edu/bitstream/handle/2142/32408/researchinnetwor160alsb.pdf?sequence=2
  21. http://archive.computerhistory.org/resources/access/text/2016/07/102738959-05-01-acc.pdf
  22. https://core.ac.uk/download/pdf/36713073.pdf
  23. http://web.mit.edu/Saltzer/www/publications/OngoingR.pdf
  24. Stillman, R.; Defiore, C. (1 September 1980). "Computer Security and Networking Protocols: Technical Issues in Military Data Communications Networks". IEEE Transactions on Communications. 28 (9): 1472–1477. doi:10.1109/TCOM.1980.1094838.
  25. "The 'Security Digest' Archives (TM) : TCP-IP Distribution List for May 1988". securitydigest.org.
  26. "Multics Execution Environment". www.multicians.org.
  27. "Thinkage UW Tools Package". Thinkage, Ltd. Retrieved 26 March 2014.
  28. From section "Terms For Units Of Information Storage" in System Output
  29. From section "$FILE" in AN INTRODUCTION TO GCOS BATCH PROCESSING
  30. Assumes 36-bit words containing four 8-bit bytes with one high-order zero bit for padding
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.