Edinburgh Multiple Access System
|This article needs additional citations for verification. (July 2011) (Learn how and when to remove this template message)|
EMAS was a powerful and efficient general purpose multi-user system which coped with many of the computing needs of Edinburgh University and the University of Kent (the only other site outside Edinburgh to adopt the operating system).
Originally running on the ICL System 4/75 mainframe (based on the design of the IBM 360) it was later reimplemented  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 2MB 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 2MB 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.
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, multi-level storage, an efficient scheduler, a separate user-space kernel ('director'), a user-level shell ('basic command interpreter'), a comprehensive archiving system and a memory-mapped file architecture.
- "The Edinburgh Multi-Access System scheduling and allocation procedures in the resident supervisor". Lecture Notes in Computer Science: 293–310. doi:10.1007/BFb0029366.