Edinburgh Multiple Access System Explained

The Edinburgh Multi-Access System (EMAS) was a mainframe computer operating system at the University of Edinburgh. The system went online in 1971.^[1]

EMAS was a powerful and efficient general purpose multi-user system which coped with many of the computing needs of the University of Edinburgh and the University of Kent (the only other site outside Edinburgh to adopt the operating system).

History

Originally running on the ICL System 4/75 mainframe (based on the design of the IBM 360) it was later reimplemented ^{[2] [3] [4]} on the ICL 2900 series of mainframes (as EMAS 2900 or EMAS-2) where it ran in service until the mid-1980s. Near the end of its life, the refactored version was back-ported (as EMAS-3) to the Amdahl 470 mainframe clone, and thence to the IBM System/370-XA architecture (the latter with help from the University of Kent, although they never actually ran EMAS-3). The National Advanced System (NAS) VL80 IBM mainframe clone followed later. The final EMAS system (the Edinburgh VL80) was decommissioned in July 1992.

The University of Kent system went live in December 1979, and ran on the least powerful machine in the ICL 2900 range - an ICL 2960, with 2 MB of memory, executing about 290k instructions per second. Despite this, it reliably supported around 30 users. This number increased in 1983 with the addition of an additional 2 MB of memory and a second Order Code Processor (OCP) (what is normally known as a CPU) running with symmetric multiprocessing. This system was decommissioned in August 1986.

Features

EMAS was written entirely in the Edinburgh IMP programming language, with only a small number of critical functions using embedded assembler within IMP sources. It had several features that were advanced for the time, including dynamic linking,^[5] multi-level storage, an efficient scheduler,^[6] a separate user-space kernel ('director'),^[7] a user-level shell ('basic command interpreter'),^[8] a comprehensive archiving system^[9] and a memory-mapped file architecture.

Such features led EMAS supporters to claim that their system was superior to Unix for the first 20 years of the latter's existence.

Legacy

The Edinburgh Computer History Project is attempting to salvage some of the lessons learned^[10] from the EMAS project and has the complete source code of EMAS online for public browsing.^[11]

See also

• Atlas Autocode

Notes and References

1. EMAS—The Edinburgh Multi-Access System. H.. Whitfield. A. S.. Wight. 1 January 1973. The Computer Journal. 16. 4. 331–346. 10.1093/comjnl/16.4.331. free.
2. Web site: Archived copy . 2004-10-09 . dead . https://web.archive.org/web/20041216160948/http://www.gtoal.com/athome/edinburgh/docs/Experiment/again.html . 16 December 2004 . dmy-all .
3. 10.1002/spe.4380101206 . 10 . 12 . The evolution of the operating system EMAS 2900 . Software: Practice and Experience . 993–1008 . Stephens . P. D.. 1980 . 31830708 .
4. 10.1002/spe.4380120707 . 12 . 7 . The kernel of the EMAS 2900 operating system . Software: Practice and Experience . 655–667 . Rees . D. J.. 1982 . 22177787 .
5. Web site: Index of /archive/os/emas/emas2/subsystem/doc/loader. history.dcs.ed.ac.uk.
6. Book: 10.1007/BFb0029366 . The Edinburgh Multi-Access System scheduling and allocation procedures in the resident supervisor . 16. 293–310 . Shelness . N. H.. Lecture Notes in Computer Science . Operating Systems . 1974. 978-3-540-06849-5.
7. The EMAS Director. D. J.. Rees. 1 January 1975. The Computer Journal. 18. 2. 122–130. 10.1093/comjnl/18.2.122. free.
8. The standard EMAS subsystem. G. E.. Millard. D. J.. Rees. H.. Whitfield. 1 January 1975. The Computer Journal. 18. 3. 213–219. 10.1093/comjnl/18.3.213. free.
9. The EMAS Archiving Program. A. S.. Wight. 1 January 1975. The Computer Journal. 18. 2. 131–134. 10.1093/comjnl/18.2.131. free.
10. Web site: More Taste: Less Greed?. Forsyth. C. H.. 2011. history.dcs.ed.ac.uk. Department of Computer Science University of York.
11. Web site: Index of /archive/os/emas. history.dcs.ed.ac.uk.