Michigan Terminal System

The University of Michigan Multiprogramming Supervisor (UMMPS) was initially developed by the staff of the academic computing center at the University of Michigan for operation of the IBM S/360-67, S/370 and compatible computers. The software may be described as a multiprogramming, multiprocessing, virtual memory, time-sharing supervisor that runs multiple resident, reentrant programs. Among these programs is the Michigan Terminal System (MTS) for command interpretation, execution control, file management, and accounting. End-users interact with the computing resources through MTS using terminal, batch, and server oriented facilities. It ceased operating MTS for end-users on June 30, 1996. By that time, most services had moved to client/server-based computing systems, typically Unix for servers and various Mac, PC, and Unix flavors for clients. The University of Michigan shut down its MTS system for the last time on May 30, 1997. Rensselaer Polytechnic Institute (RPI) is believed to be the last site to use MTS in a production environment. RPI retired MTS in June 1999. Today, MTS still runs using IBM S/370 emulators such as Hercules, Sim390, and FLEX-ES. ==Origins==

In the mid-1960s, the University of Michigan was providing batch processing services on IBM 7090 hardware under the control of the University of Michigan Executive System (UMES), but was interested in offering interactive services using time-sharing. At that time the work that computers could perform was limited by their small real memory capacity. When IBM introduced its System/360 family of computers in the mid-1960s, it did not provide a solution for this limitation and within IBM there were conflicting views about the importance of and need to support time-sharing. A paper titled Program and Addressing Structure in a Time-Sharing Environment by Bruce Arden, Bernard Galler, Frank Westervelt (all associate directors at UM's academic Computing Center), and Tom O'Brian building upon some basic ideas developed at the Massachusetts Institute of Technology (MIT) was published in January 1966. The paper outlined a virtual memory architecture using dynamic address translation (DAT) that could be used to implement time-sharing. After a year of negotiations and design studies, IBM agreed to make a one-of-a-kind version of its S/360-65 mainframe computer with dynamic address translation (DAT) features that would support virtual memory and accommodate UM's desire to support time-sharing. The computer was dubbed the Model S/360-65M. The time-sharing experiment began as a "half-page of code written out on a kitchen table" combined with a small multi-programming system, LLMPS from MIT's Lincoln Laboratory, At this time UM had to decide whether to return the Model 67 and select another mainframe or to develop MTS as an interim system for use until TSS was ready. The decision was to continue development of MTS and the staff moved their initial development work from the Model 50 to the Model 67. TSS development was eventually canceled by IBM, then reinstated, and then canceled again. But by this time UM liked the system they had developed, it was no longer considered interim, and MTS would be used at U of M and other sites for 33 years. ==MTS Consortium==

MTS was developed, maintained, and used by a consortium of eight universities in the US, Canada, and the United Kingdom: • University of Michigan (U of M), 1967 to 1997, US • University of British Columbia (UBC), 1968 to 1998, Canada • NUMAC (University of Newcastle upon Tyne, University of Durham, and Newcastle Polytechnic), 1969 to 1992, United Kingdom • University of Alberta (UQV), 1971 to 1994, Canada • University of Durham (NUMAC), United Kingdom Several sites ran more than one MTS system: NUMAC ran two (first at Newcastle and later at Durham), Michigan ran three in the mid-1980s (UM for Maize, UB for Blue, and HG at Human Genetics), UBC ran three or four at different times (MTS-G, MTS-L, MTS-A, and MTS-I for general, library, administration, and instruction). Each of the MTS sites made contributions to the development of MTS, sometimes by taking the lead in the design and implementation of a new feature and at other times by refining, enhancing, and critiquing work done elsewhere. Many MTS components are the work of multiple people at multiple sites. In the early days collaboration between the MTS sites was accomplished through a combination of face-to-face site visits, phone calls, the exchange of documents and magnetic tapes by snail mail, and informal get-togethers at SHARE or other meetings. Later, e-mail, computer conferencing using CONFER and *Forum, network file transfer, and e-mail attachments supplemented and eventually largely replaced the earlier methods. The members of the MTS Consortium produced a series of 82 MTS Newsletters between 1971 and 1982 to help coordinate MTS development. Starting at UBC in 1974 the MTS Consortium held annual MTS Workshops at one of the member sites. The workshops were informal, but included papers submitted in advance and Proceedings published after-the-fact that included session summaries. In the mid-1980s several Western Workshops were held with participation by a subset of the MTS sites (UBC, SFU, UQV, UM, and possibly RPI). The annual workshops continued even after MTS development work began to taper off. Called simply the "community workshop", they continued until the mid-1990s to share expertise and common experiences in providing computing services, even though MTS was no longer the primary source for computing on their campuses and some had stopped running MTS entirely. MTS sites In addition to the eight MTS Consortium sites that were involved in its development, MTS was run at a number of other sites, including: within the Conselho Nacional de Desenvolvimento Científico e Tecnológico (CNPq), Brazil • Empresa Brasileira de Pesquisa Agropecuária (EMBRAPA), Brazil • Hewlett-Packard (HP), US • Michigan State University (MSU), US • Goddard Space Flight Center, National Aeronautics and Space Administration (NASA), US A copy of MTS was also sent to the University of Sarajevo, Yugoslavia, though whether or not it was ever installed is not known. INRIA, the French national institute for research in computer science and control in Grenoble, France ran MTS on a trial basis, as did the University of Waterloo in Ontario, Canada, Southern Illinois University, the Naval Postgraduate School, Amdahl Corporation, ST Systems for McGill University Hospitals, Stanford University, and University of Illinois in the United States, and a few other sites. ==Hardware==

In theory MTS will run on the IBM S/360-67, any of the IBM S/370 series which include virtual memory, and their successors. MTS has been run on the following computers in production, benchmarking, or trial configurations: the first Amdahl 5860 (serial number 1) in 1982, and the first factory shipped IBM 3090–400 in 1986. NUMAC ran MTS on the first S/360-67 in the UK and very likely the first in Europe. The University of British Columbia (UBC) took the lead in converting MTS to run on the IBM S/370 series (an IBM S/370-168) in 1974. The University of Alberta installed the first Amdahl 470V/6 in Canada (serial number P5) in 1975. By 1978 NUMAC (at University of Newcastle upon Tyne and University of Durham) had moved main MTS activity on to its IBM S/370 series (an IBM S/370-168). MTS was designed to support up to four processors on the IBM S/360-67, although IBM only produced one (simplex and half-duplex) and two (duplex) processor configurations of the Model 67. In 1984 RPI updated MTS to support up to 32 processors in the IBM S/370-XA (Extended Addressing) hardware series, although 6 processors is likely the largest configuration actually used. MTS supports the IBM Vector Facility, available as an option on the IBM 3090 and ES/9000 systems. In early 1967 running on the single processor IBM S/360-67 at UM without virtual memory support, MTS was typically supporting 5 simultaneous terminal sessions and one batch job. By late 1991 MTS at UM was running on an IBM ES/9000-720 supporting over 600 simultaneous terminal sessions and from 3 to 8 batch jobs. MTS can be IPL-ed under VM/370, and some MTS sites did so, but most ran MTS on native hardware without using a virtual machine. ==Features==

Some of the notable features of MTS include: • The use of Virtual memory and Dynamic Address Translation (DAT) on the IBM S/360-67 in 1967. • The use of multiprocessing on an IBM S/360-67 with two CPUs in 1968. • Programs with access to (for the time) very large virtual address spaces. • A straightforward command language that is the same for both terminal and batch jobs. • A strong device independent input/output model that allows the same commands and programs to access terminals, disk files, printers, magnetic and paper tapes, card readers and punches, floppy disks, network hosts, and an audio response unit (ARU). • A file system with support for "line files" where the line numbers and length of individual lines are stored as metadata separate from the data contents of the line, and the ability to read, insert, replace, and delete individual lines anywhere in the file without the need to read or write the entire file. • A file editor ($EDIT) with both command line and "visual" interfaces and pattern matching based on SNOBOL4 patterns. • The ability to share files in controlled ways (read, write-change, write-expand, destroy, permit). • The ability to permit files, not just to other user IDs and projects (aka groups), but to specific commands or programs and combinations of user IDs, projects, commands and programs. • An e-mail system ($MESSAGESYSTEM) that supports local and network mail with the ability to send to groups, to recall messages that haven't already been read, to add recipients to messages after they have been sent, and to display a history of messages in an e-mail chain without the need to include the text from older messages in each new message. • The ability to access tapes remotely, and to handle data sets that extend across multiple tapes efficiently. • The availability of a rich collection of well-documented subroutine libraries. • The ability for multiple users to quickly load and use a collection of common reentrant subroutines, which are available in shared virtual memory. • The availability of compilers, assemblers, and a Symbolic Debugging System (SDS) that allow users to debug programs written in high-level languages such as FORTRAN, Pascal, PL/I, ... as well as in assembly language. • A strong protection model that uses the virtual memory hardware and the S/360 and S/370 hardware's supervisor and problem states and via software divides problem state execution into system (privileged or unprotected) and user (protected or unprivileged) modes. Relatively little code runs in supervisor state. For example, Device Support Routines (DSRs, aka device drivers) are not part of the supervisor and run in system mode in problem state rather than in supervisor state. • A simulated Branch on Program Interrupt (BPI) instruction. Programs developed for MTS The following are some of the notable programs developed for MTS: • Awit, a computer chess program written in Algol W by Tony Marsland. • Chaos, one of the leading computer chess programs from 1973 through 1985. Written in FORTRAN Chaos started at RCA Systems Programming division in Cinnaminson, NJ with Fred Swartz and Victor Berman as first authors, Mike Alexander and others joined the team later and moved development to MTS at the UM Computing Center. • CONFER II, one of the first computer conferencing systems. CONFER was developed by Robert Parnes starting in 1975 while he was a graduate student and with support from the University of Michigan's Center for Research on Learning and Teaching (CRLT) and School of Education. • FakeOS, a simulator that allows object modules containing OS/360 SVCs, control blocks, and references to OS/360 access methods to execute under MTS. • Forum, a computer conferencing system developed by staff of the Computing Centre at the University of British Columbia (UBC). • GOM (Good Old Mad), a compiler for the 7090 MAD language converted to run under MTS by Don Boettner of the UM's Computing Center. • IF (Interactive Fortran), developed by the University of British Columbia Computing Centre. • MICRO Information Management System, one of the earliest relational database management systems implemented in 1970 by the Institute for Labor and Industrial Relations (ILIR) at the University of Michigan. • MIDAS (Michigan Interactive Data Analysis System), an interactive statistical analysis package developed by Dan Fox and others at UM's Statistical Research Laboratory. • Plus, a programming language developed by Alan Ballard and Paul Whaley of the Computing Centre at the University of British Columbia (UBC). It was used for systems programming within MTS itself, particularly DSRs and CLSes. • TAXIR, an information storage and retrieval system designed for taxonomic data at the University of Colorado by David Rogers, Henry Fleming, Robert Brill, and George Estabrook and ported to MTS and enhanced by Brill at the University of Michigan. • Textform, a text-processing program developed at the University of Alberta's Computing Centre to support device independent output to a wide range of devices from line printers, to the Xerox 9700 page printers, to advanced phototypesetting equipment using fixed width and proportional fonts. • VSS, a simulator developed at the University of British Columbia's Computing Centre that makes it possible to run OS/MFT, OS/MVT, VS1, and MVS application programs under MTS. Programs that run under MTS The following are some of the notable programs ported to MTS from other systems: • Fortran, the G, H, and VS compilers from IBM. • GASP, a FORTRAN based discrete simulation package. • Kermit, Columbia University's communications software and protocol • MPS, IBM's Mathematical Programming System/360. • NASTRAN, finite element analysis program originally developed by and for NASA. • OSIRIS (Organized Set of Integrated Routines for Investigations with Statistics), a collection of statistical analysis programs developed at the University of Michigan's Institute for Social Research (ISR). • PascalSB, the Stony Brook Pascal compiler. • Pascal/SLAC, the Pascal compiler from the Stanford Linear Accelerator Center. • Pascal VS, IBM's Pascal VS compiler program product. • PL/I Optimizing Compiler from IBM. • REDUCE2, an algebraic language implemented in LISP. • SAS (Statistical Analysis System). • SHAZAM, a package for estimating, testing, simulating and forecasting econometrics and statistical models • SIMSCRIPT II.5, a free-form, English-like, general-purpose discrete event simulation language. • SPIRES (Stanford Public Information Retrieval System), a database management system. • SPSS (Statistical Package for the Social Sciences) • TELL-A-GRAPH, a proprietary conversational graphics program from ISSCO of San Diego, CA. • TEX, Don Knuth's TeX text-processing program. • TROLL, econometric modeling and statistical analysis Programming languages available under MTS MTS supports a rich set of programming languages, some developed for MTS and others ported from other systems: • ALGOL 68 • APL (IBM's VS APL) • Assembler (360/370: G, H, Assist; DEC PDP-11) • BASIC (BASICUM), WBASIC • BCPL (Basic Combined Programming Language) • C • COBOL (ANSI, VS, WATBOL) • EXPL (Extended XPL) • FORTRAN (G, H, VS, WATFOR, WATFIV) • GASP (A FORTRAN-based discrete simulation language) • GOM (Good Old Mad, the 7090 Michigan Algorithm Decoder ported to the S/370 architecture) (General Purpose Simulation System V) • ICON • IF (Interactive FORTRAN, an incremental compiler and environment for executing and debugging FORTRAN programs, developed at the University of British Columbia) (a new implementation of LISP 1.5 developed at the UM's Mental Health Research Institute, MHRI) • Pascal (VS, JB) • PIL, PIL/2 (Pitt Interpretive Language) • PL/I (F and OPT from IBM, PL/C from Cornell University) • PL/M • PL360 • Plus system language developed at the University of Toronto, c. 1971) • Prolog • Simula • SUE (String Oriented Symbolic Language) • SPITBOL (University of Michigan Interpretive String Translator, based on TRAC) ==System architecture==

UMMPS, the supervisor, has complete control of the hardware and manages a collection of job programs. One of the job programs is MTS, the job program with which most users interact. MTS operates as a collection of command language subsystems (CLSs). One of the CLSs allows for the execution of user programs. MTS provides a collection of system subroutines that are available to CLSs, user programs, and MTS itself. Among other things these system subroutines provide standard access to Device Support Routines (DSRs), the components that perform device dependent input/output. ==Manuals and documentation==

The lists that follow are quite University of Michigan centric. Most other MTS sites used some of this material, but they also produced their own manuals, memos, reports, and newsletters tailored to the needs of their site. End-user documentation The manual series MTS: The Michigan Terminal System, was published from 1967 through 1991, in volumes 1 through 23, which were updated and reissued irregularly. • MTS Volume II: Language processor descriptions: F-level assembler; FORTRAN G; IOH/360; PIL; SNOBOL4; UMIST; WATFOR; and 8ASS (PDP-8 assembler) • MTS Volume 1: The Michigan Terminal System, 1991 • MTS Volume 2: Public File Descriptions, 1990 • MTS Volume 3: Subroutine and Macro Descriptions, 1989 • MTS Volume 4: Terminals and Networks in MTS, 1988 (earlier Terminals and Tapes) • MTS Volume 5: System Services, 1985 • MTS Volume 6: FORTRAN in MTS, 1988 • MTS Volume 7: PL/I in MTS, 1985 • MTS Volume 8: LISP and SLIP in MTS, 1983 • MTS Volume 9: SNOBOL4 in MTS, 1983 • MTS Volume 10: BASIC in MTS, 1980 • MTS Volume 11: Plot Description System, 1985 • MTS Volume 12: PIL/2 in MTS, 1974 • MTS Volume 13: The Symbolic Debugging System, 1985 (earlier ''Data Concentrator User's Guide'') • MTS Volume 14: 360/370 Assemblers in MTS, 1986 • MTS Volume 15: FORMAT and TEXT360, 1988 • MTS Volume 16: ALGOL W in MTS, 1980 • MTS Volume 17: Integrated Graphics System, 1984 • MTS Volume 18: MTS File Editor, 1988 • MTS Volume 19: Tapes and Floppy Disks, 1993 • MTS Volume 20: PASCAL in MTS, 1989 • MTS Volume 21: MTS Command Extensions and Macros, 1991 • MTS Volume 22: Utilisp in MTS, 1988 • MTS Volume 23: Messaging and Conferencing in MTS, 1991 • MTS Reference Summary, a ~60 page, 3" x 7.5", pocket guide to MTS, Computing Center, University of Michigan • The Taxir primer: MTS version, Brill, Robert C., Computing Center, University of Michigan • Fundamental Use of the Michigan Terminal System, Thomas J. Schriber, 5th Edition (revised), Ulrich's Books, Inc., Ann Arbor, MI, 1983, 376 pp. • Digital computing, FORTRAN IV, WATFIV, and MTS (with *FTN and *WATFIV), Brice Carnahan and James O Wilkes, University of Michigan, Ann Arbor, MI, 1968–1979, 1976 538 p. • Documentation for MIDAS, Michigan Interactive Data Analysis System, Statistical Research Laboratory, University of Michigan • OSIRIS III MTS Supplement, Center for Political Studies, University of Michigan Various aspects of MTS at the University of Michigan were documented in a series of Computing Center Memos (CCMemos) which were published irregularly from 1967 through 1987, numbered 2 through 924, though not necessarily in chronological order. Numbers 2 through 599 are general memos about various software and hardware; the 600 series are the Consultant's Notes series—short memos for beginning to intermediate users; the 800 series covers issues relating to the Xerox 9700 printer, text processing, and typesetting; and the 900 series covers microcomputers. There was no 700 series. In 1989 this series continued as Reference Memos with less of a focus on MTS. A long run of newsletters targeted to end-users at the University of Michigan with the titles Computing Center News, Computing Center Newsletter, U-M Computing News, and the Information Technology Digest were published starting in 1971. • MTS Message Manual • MTS Volume n: Systems Edition • MTS Volume 99: Internals Documentation • Supervisor Call Descriptions • Disk Disaster Recovery Procedures • A series of lectures describing the architecture and internal organization of the Michigan Terminal System given by Mike Alexander, Don Boettner, Jim Hamilton, and Doug Smith (4 audio tapes, lecture notes, and transcriptions) ==Distribution==

The University of Michigan released MTS on magnetic tape on an irregular basis. and from the University of Michigan's Deep Blue digital archive. Working with the D6.0 distribution materials, it is possible to create an IPLable version of MTS. A new D6.0A distribution of MTS makes this easier. D6.0A is based on the D6.0 version of MTS from 1988 with various fixes and updates to make operation under Hercules in 2012 smoother. In the future, an IPLable version of MTS will be made available based upon the version of MTS that was in use at the University of Michigan in 1996 shortly before MTS was shut down. ==Licensing==

As of December 22, 2011, the MTS Distribution materials are freely available under the terms of the Creative Commons Attribution 3.0 Unported License (CC BY 3.0). In its earliest days MTS was made available for free without the need for a license to sites that were interested in running MTS and which seemed to have the knowledgeable staff required to support it. In the mid-1980s licensing arrangements were formalized with the University of Michigan acting as agent for and granting licenses on behalf of the MTS Consortium. MTS licenses were available to academic organizations for an annual fee of $5,000, to other non-profit organizations for $10,000, and to commercial organizations for $25,000. The license restricted MTS from being used to provide commercial computing services. The licensees received a copy of the full set of MTS distribution tapes, any incremental distributions prepared during the year, written installation instructions, two copies of the current user documentation, and a very limited amount of assistance. Only a few organizations licensed MTS. Several licensed MTS in order to run a single program such as CONFER. The fees collected were used to offset some of the common expenses of the MTS Consortium. ==See also==