DOCSLIB.ORG

Extensions to DEC TOPS-20 Operating System

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Extensions to DEC TOPS-20 Operating System I Bolt Beranek and Newman Inc. Report No. 4041 LEVEL I ~~ ~ i I— ~ I~X~ ~~ Extensions to DEC TOPS -20 Operating System I Final Report ~ ~~ (I I January 1979 DDC I JE]Ifl . I Def~nse Advanced Research Projects Agency ~~~rB DISTRIBUTION STATEMENT A Approved for public releoso~ I Distribution Unlimited La.. I - I 1• BBN Report No. 4 0 41 ~: :: Extensions to DEC TOPS-20 Operating System Final Report January 1979 1. ~ Sponsored by: I Defense Advanced Research Projects Agency ARPA Order No. 2901, M~endment #5 Monitored by: Office of Naval Research - Under Contract No. N00014-77-C-1490 The views and ~,onc1usions contained in this document are those -. of the authors and should not be interpreted as necessarily representing the official policies, either expressed or implied of the Defense Advanced Research Projects Agency or the United States Government . This research was supported Distribution of this document by the Defense Advanced is unlimited . It may be Research Projects Agency released to the Clearinghouse , under ARPA Order No. 2901. Department of Commerce for Contract No. N00014—77—C-O49O sale to the general public . 11 II Ill _ _ - __________________________________________ . — ________ ~~~~~~~~ I __________________Unclassified InI.r. SECU~~~?Y CLAISIPICATION OP THIS PAGE (1%.. D• REPORT..DOCUMEHTATIOW PAGE BEFORE COMPLETING FORM £ . R- ACCEUIO I NO S CATALOG NUNSE (s’. ~i 1 UflT 4~ $aO ---... OVT ) .7 ~~~ IiM 5 ~ ~ / I ( 7~~-’ Q ~~~~~~~~~~~~~~~~~~~~__.. _.J —vrr . rums• ~ ~~~~ ~~~ s ~~~~~~~~~~~~~~~~~ 62i Extanslons to DEC TOPS—38’Operating System ~ / 3 AUI NO ) — IS ~ ~~~ E I J fr S PS PO NING ORGANIZATION NAME AND ADDRESS ~~~ ~~ ~ AREA A WO RK UNIT NUMSE RS ~ Bolt~~ Beranek and Newman Inc. 50 Moulton Street M* R. 02 ________________________ ’ ~ 41. - -. II. CONTROUJIS G OPPICE NAME AND ADDRESS ~~~~~~~~~~~~~~~~~~~~ _ 1/f) Jan~~~~~~ ~~79/ . * . 31r WWU UW.~~ OP PA~ I * 1 __________________________________________________________ 11 - IS. MONITORING AGENCY NAME S ADORESS(tI OWe.) IS. SECURITY CLASS. (.1 thS. ,sp. j mffiP ,.,I JII III C..M.UM. ~~) Unclass f ed • /> _/ / i i r” ’I . I5a DEC%. ASSIPICATION/DOWNONADING - - / ~ SCHEDULE ~~~~~~ ~I ~ . IS. • SISTRISUTION StAt EMENT (.1 * 1. ~~~~~~ Distribution of this document is unlimited . It may be released to the Clear ngho se 4 i u , Department ,pf Commerce for sale to the general public. fl., II b R .if) IT. DIST RISUTION STATEMENT (.1 I#. .5 fr•e* .,I. , .d S. PS..k SI H ~~ ~~ IS. SUPPLEMENTARY NOTES research w s s or ed by he D fense Adva ce Research Pro - This a upp t t e n d ~ ects Agency under ARPA Order No. 2901 , Amendment #5. -S ,,w . U .. c.. ..p ..d I ffl MicA 5,) IS. KEY ~OROS (Ci. M.s ~ s4* ~~~ ~ ~~ cs TOPS—20 Operating System Network Control Program TENEX Operating System JSY S Traps ARPA Network ,., II c.puucap by MicA ASETRACT (C .icM. a. ~~. i ~~~ ~~~ - This report describes modifications made to the TOPS—20 operating system in order to enable ARPA research programs previously supported by the TENEX operating system to be supported by TOPS—20 . In addition , it -~~ describes modifications to the ARPANET network control programs (Nçt~s) for LI both TENEX and TOPS—20 to enable those hosts to use the ‘ new style extended hos.t/Dff leaders. The changes to TOPS—20 have been delivered to DEC and merged with the standard , DEC version of the system , and will be1.-j~ ~ J ’ D TION OP 1 1S 05b0 1tt DO i n 1473 ~ ~ ~~ 0~~~~~ ~~ Unclassified I ~~~~~ __________________ CI.A$SIPICATIOII OP THIS PASS ( OS.. SECURITY ~~~~~ SECU RITY CLASSIFICATION OP THIS PAS1 US PS.. - ~ ~~~Iurs~~ ..> maintained by DEC along with the rest of the s~stem~~~~ I. • 1~ 0 • Ii L [j ~ _ ..J_ SUURI?Y cI.ASMPICA ,ISN OP YNIS PASSI SI.. ~.S - - -- ~~~~~~~~~~~~~~~~~~~ - - ,- -—--- ~~~~~ [i I Report No. 4041 Bolt Beranek and Newman Inc . I TABLE OF CONTENTS Page i. ~~~~~~~~~~~~~~~~~~ . I 2. TOPS—20 Modifications . 4 1 3. Documentation of TOPS—20 Modification . 7 4. New Style Leaders for TENEX and TOPS-20 S I I I I AC C . ~~~ ~ ~~~ - NTIS e cction • ~ ~ ~~ I I ~ ~~~~~~ 0 I ~ s Y 7 - Di:t ~~~~~~~~~~ u,’or S ’ECIAL :1 __ ‘ i Ti I i Report No. 4041 Bolt Beranek and Newman Inc. 1. Summar y The objective of this project was to augment the TOPS—20 operating system for the DEC System—20 computer system to enable it to support ARPA information processing technology programs. ~ I All of the tasks in the project have been completed , and the i I software has been delivered to DEC and the ARPANET community - along with the supporting documentation . This report describes ~: the various tasks. - For a number of years the DEC KA1O processor operating under ~ the TENEX operating system developed by BBN has been central to ARPA - I many information processing research projects. Recently DEC has developed a new l ine of processors , including the KL1O and — RL2O processors , which are significantly faster than , but functionally compatible with , the older KA1O. The operating system for this new l ine of processors is a descendant of an I early version of TENEX (circa 1972) and is called TOPS—20. The ~ new DEC processor together with the TOPS—20 operating system is I called the DEC System—20. I Because the DEC System—20 offers similar capabilities to the older ~AlO—based TENEX system and is considerably more cost I I effective, many ARPA sponsored installations are upg r ading their equipm ent to these newer systems . This switchover has the I additional benefit of acquiring an operating system that is I suppor ted by a computer manufacturer (DEC) . I -1- I Report No. 4041 Bolt Beranek and Newman Inc. Until this project was completed , however , the benefits of 1. upgrading to the DEC System—20 have been limited due to a number of software - - incompatibilities between TENEX and TOPS—20. The 1. source of the problem was that many of the improvements and increased capabilities that have been added to TENEX since 1972 - - not been integrated had into the TOPS—20 system . As a result , U the computational requirements of many ARPA projects, such as the National Software Works (NSW) and - the Advanced Command Control Architectural Testbed (ACCAT), of other government projects such ~ I as the Military Message systems, and of many users could not be supported by TOPS—20. The purpose of the work described in this report was to correct that situation by making the additions to the TOPS—20 system required to allow these projects to move from j TENEX to In addition to the changes described above , as part of this project we modified the Network Control Programs (NCPs) of the TOPS—20 and TENEX operating systems to make use of the “ new - style” Host/IMP leaders. These modifications make it possible for TOPS—20 and TENEX hosts to address (and therefore communicate with) the full range of ARPANET hosts . The specific tasks in the contract statement of work were: F — “ Implement the modifications to the DEC TOPS—20 operating system that are specified An Section II of the contractor ’s • II proposal (BBN Proposal P77—ISD—47) . — Prov ide documentation to the best commercial standards for the TOPS—20 modifications specified in Section II of the ll contractor ‘ s proposal . -2- I ---• . - -~~~~~~~~~ - - C Report No. 4041 Bolt Beranek and Newman Inc. — Modify the Networ k Control Programs and — for the TOPS—20 ~~ TENEX operating systems to use “ new s tyle” Host/IMP leaders in order to allow TOPS—20 and TENE X hosts to address the full range of ARPANET hosts.” “S The following sections of this report describe each of these tasks. *5 II. 4. - IS .5 ii. I I I —3— I _ _ __ - • - - - p.— •- _•_ ~ - ~~ ~~~~~ • ~~~~ - ~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~ ~ ~ iT Report No. 4041 Bolt Be r anek and Newman Inc. 45 2. TOPS—20 Modifications Considerable care was taken to ensure that the TOPS-20 S mod ifications undertaken were adequate to support the - - requ irements of ARPA ’S users and were acceptable to DEC who would assume respons ibility for maintaining them . At the outset of the project , the ent ire community of ARPA contractors was polled to identify any TENEX features not included in the TOPS—20 system that were required to support the - contractor ’s computational needs. After a set of requirements • had been identified and a set of proposed modifications to * TOPS— 20 specified , we met with DEC to determine how best to - satisfy the requirements. In some cases it was agreed that the • - proposed modifications could be integrated directly into TOPS—20 - - as specified; in others , due to conflicts with other DEC plans for TOPS—20 development , compromises as to how to best support I ~ given requirements were reached . The result of these - - - negotiations with DEC was a new specification for add it ions to 1.. TOPS—20. The resulting spec ification was then circulated to the ARPA community for approval. A number of minor changes to the specification were recommended by the community and agreed to by DEC . The specification was then implemented . The rest of this section lists the modifications made to TOPS—20 and br iefly describes each . The reader interested in I I more detail is referred either to the proposal for th is project (BBN Proposal P77—ISD—47 ) or to DEC documentation for release 3 I of TOPS—20. 1 •-- — - - . “ - - — — •- - “ — • — . - —---- - ---- I— —— ~~~~~~~ . q--.- Zr ‘ - ~ - --~~ ~ r- ~ wn- ~~~~~~~~~~~~~~~~~ ~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - - - - Li Report No. 4041 Bolt Beranek and Newman Inc. LI — Addition of JSYS traps . The JSYS trap mechanism prov ides a means for one process (fork) in a job to intercept (selected) operating system calls I (JSYS ’s) executed by other processes in the job before the i i calls are acted upon by the operating system .
Load more

Recommended publications
  • Getting Started Computing at the Al Lab by Christopher C. Stacy Abstract
    MASSACHUSETTS INSTITUTE OF TECHNOLOGY ARTIFICIAL INTELLI..IGENCE LABORATORY WORKING PAPER 235 7 September 1982 Getting Started Computing at the Al Lab by Christopher C. Stacy Abstract This document describes the computing facilities at the M.I.T. Artificial Intelligence Laboratory, and explains how to get started using them. It is intended as an orientation document for newcomers to the lab, and will be updated by the author from time to time. A.I. Laboratory Working Papers are produced for internal circulation. and may contain information that is, for example, too preliminary or too detailed for formal publication. It is not intended that they should be considered papers to which reference can be made in the literature. a MASACHUSETS INSTITUTE OF TECHNOLOGY 1982 Getting Started Table of Contents Page i Table of Contents 1. Introduction 1 1.1. Lisp Machines 2 1.2. Timesharing 3 1.3. Other Computers 3 1.3.1. Field Engineering 3 1.3.2. Vision and Robotics 3 1.3.3. Music 4 1,3.4. Altos 4 1.4. Output Peripherals 4 1.5. Other Machines 5 1.6. Terminals 5 2. Networks 7 2.1. The ARPAnet 7 2.2. The Chaosnet 7 2.3. Services 8 2.3.1. TELNET/SUPDUP 8 2.3.2. FTP 8 2.4. Mail 9 2.4.1. Processing Mail 9 2.4.2. Ettiquette 9 2.5. Mailing Lists 10 2.5.1. BBoards 11 2.6. Finger/Inquire 11 2.7. TIPs and TACs 12 2.7.1. ARPAnet TAC 12 2.7.2. Chaosnet TIP 13 3.
    [Show full text]
  • Storage Organization and Management in TENEX I. Introduction
    Storage Organization and Management in TENEX http://www.linique.com/dlm/tenex/fjcc72/ Storage Organization and Management in TENEX by Daniel L. Murphy Presented at the Fall Joint Computer Conference, 1972. Originally published in AFIPS Conference Proceedings Volume 41. I. Introduction In early 1969, BBN began an effort aimed at developing a new time-shared operating system. It was felt at the time that none of the commercially available systems could meet the needs of the research planned and in progress at BBN. The foremost requirement of the desired operating system was that it support a directly addressed process memory in which large list-processing computations could be performed. The cost of core storage prohibited the acquisition of sufficient memory for even one such process, and the problems of swapping such very large processes in a time-sharing environment made that solution technically infeasible as well. Paging was therefore the logical alternative, and our study and experience with list processing systems(1,2) led us to believe that using a demand-paged virtual memory system for such computations was a feasible approach. With demand paged process virtual memory added to our requirements, we found no existing system which could adequately meet our needs. Our approach was to take an existing system which was otherwise appropriate and add the necesary hardware to support paging. The system chosen was the DEC PDP-10 (3), which, although not paged, was available with a time-shared operating system and substantial support software. Consideration was given to modifying the existing PDP-10 operating system to support demand paging, but that approach was rejected because of the substantial amount of work which would be required, because of the inherent constraints imbedded in the architecture of any large system, and because development of a new operating system would allow the inclusion of a great many other features and facilities which were judged desirable.
    [Show full text]
  • NWG/RFC# 752 MRC 2-Jan-79 01:22 Nnnnn a Universal Host Table
    NWG/RFC# 752 MRC 2-Jan-79 01:22 nnnnn A Universal Host Table Network Working Group Mark Crispin Request for Comments 752 SU-AI NIC nnnnn 2 January 1979 A Universal Host Table ABSTRACT: The network host table in use at MIT and Stanford is described. This host table is superior to the NIC and Tenex host tables in several ways. A binary file, compiled from this host table, is also described. This file is used by subsystems on MIT's ITS and Stanford's WAITS timesharing systems for efficiency in host and network lookups. HISTORY: As with many other sites on the Arpanet, we found the NIC's host table unsuited to our needs. Part of the problem was because the NIC host table was often inaccurate and all too often failed to include several nicknames in common usage in our communities. In addition, the NIC host table's format was awkward for user programs to use, especially those which wanted to have the host table mapped into memory in some sort of structured binary form for efficient lookups. Finally, the NIC host table neglects to include some essential information. The ITS host table was originally designed to be compiled along with a network handling program (MIDAS, the PDP-10 assembler used, has a pseudo-op to insert a file into an assembly). In order to make the host table palatable to the assembler, every comment line began with a semicolon, and every actual data line began with the word HOST. Each program which used the host table defined HOST as an assembly macro before inserting the host table into the assembly.
    [Show full text]
  • Engineering Strategy Overview Preliminary
    March 1982 Engineering Preliminary Strategy Company Overview Confidential If.-t8···· L..4L ~ \:')' j.~.! / .;.' ' 1985 1990 1995 2000 - P,O S SIB L E DEC PRO Due T S - $lJOO cellular radio net discontinouous.100 word ~ lim! ted context HANDHELD speaker independent speaker independent $1.0K speech recogn. • sketchpad , interpretation Glata structures , ' & relat~onsh~ps object filing natural languaqe (invisible, protected structures) $40K I CAB I NET I ,4 (dedicated fixture) ~~~n limited context [:~~~~e~ ~~~:~~i:ti~n ~ ak rind pendent • voice ~tuate~ retrieval spe ~ e _ .. • te1econferenc1ng center cont1nued speechlrecogn~tion " ;., encryption associa tiveJparallel a;;;'e'los (, ..j." .---~ provide CAtt= ASSISTANT -------...--- .. • LIBRARlj\N ~ ?ertified "best match" retrieval ~ (secure) os (holographic? ) $650K BD 1/15/81 PRELIMINARY ENGINEERING STRATEGY OVERVIEW MARCH lYtil SECONIJ IJRAFT PRELIMINARY ENGINEERING STRATEGY OVERVIEW TABLE OF CONTENTS ,Preface Chapter I fhe Product Strategy and Transitioning to the Fifth Generation - Product Strategy Overview - The Transitions - Personal Computer Clusters, PCC, Are An Alternative to Timeshared Computers - The Product Strategy - Fifth and Sixth Computer Technology Generations - Uistributed Processing and Limits to Its Growth Chapter II Essays on the Criteria for Allocation of Engineering Resources - Overview, - Heuristics for Building Great Products, - Proposed Resource Allocation Criteria - UEC's Position in the VAN - Buyout Philosophy/Process/Criteria - Example of a "Make vs Buy" Analysis - Engineering Investment Sieve Chapter III Essays on Strategic Threats and Opportunities - Uverview, - Strategic Threats - Getting Organized in Engineering and Manufacturing to Face Our Future Competitors p - View of Competitors ---~,.~".~.-~ l f;t-1) IPrT Co?"! v. 7U/L, / IJ ...J - Te-Iecommunications Environment ) ;2f e-c.. - Competitive TeChnology Exercise, ltv • Chapter IV TeChnology Managers Committee Report ,MC- .
    [Show full text]
  • Lisp: Program Is Data
    LISP: PROGRAM IS DATA A HISTORICAL PERSPECTIVE ON MACLISP Jon L White Laboratory for Computer Science, M.I.T.* ABSTRACT For over 10 years, MACLISP has supported a variety of projects at M.I.T.'s Artificial Intelligence Laboratory, and the Laboratory for Computer Science (formerly Project MAC). During this time, there has been a continuing development of the MACLISP system, spurred in great measure by the needs of MACSYMAdevelopment. Herein are reported, in amosiac, historical style, the major features of the system. For each feature discussed, an attempt will be made to mention the year of initial development, andthe names of persons or projectsprimarily responsible for requiring, needing, or suggestingsuch features. INTRODUCTION In 1964,Greenblatt and others participated in thecheck-out phase of DigitalEquipment Corporation's new computer, the PDP-6. This machine had a number of innovative features that were thought to be ideal for the development of a list processing system, and thus it was very appropriate that thefirst working program actually run on thePDP-6 was anancestor of thecurrent MACLISP. This earlyLISP was patterned after the existing PDP-1 LISP (see reference l), and was produced by using the text editor and a mini-assembler on the PDP-1. That first PDP-6 finally found its way into M.I.T.'s ProjectMAC for use by theArtificial lntelligence group (the A.1. grouplater became the M.I.T. Artificial Intelligence Laboratory, and Project MAC became the Laboratory for Computer Science). By 1968, the PDP-6 wasrunning the Incompatible Time-sharing system, and was soon supplanted by the PDP-IO.Today, the KL-I 0, anadvanced version of thePDP-10, supports a variety of time sharing systems, most of which are capable of running a MACLISP.
    [Show full text]
  • Non Unix Family Tree and Timeline Version 0.3.2
    Non Unix family tree and Timeline Version 0.3.2 1958 FMS SOS 1958 Late 1950's Late 1950's 1960 1960 IBM 1410/1710 OS Early 1960's CTSS 1961-1962 1962 IBSYS PDP-1 OS 1962 Early 1960's 1962 SABRE 1962-64 EXEC I 1964 Tops-10 1.4 1964 1964 Early 1960's OS/360 Multics TOS (BOS, TOS,DOS) 1965 1965 EXEC II Early 1960's DOS CP-40 1966 (CP-67) Tops-10 1.9 MS/8 1966 1966 1966 1966 CAL BPS/360 CP/CMS Tops-10 2.18 Late 1960's ITS WAITS EXEC 3 Late 1960's 1967 1967 1967 1967 Late 1960's DOS/VSE 1968 PARS Tops-10 3.27 1968 1968 SCOPE TDOS 1968 Late 1960's EXEC 4 Late 1960's Late 1960's VMOS ACP v4 EXEC 8 OS/MFT Tops-10 4.50 ACP TENEX Unix Late 1960's 1969 1969 1969 1969 MSS 4.0 1969 Late 1960's Tops-10 4.72 10/1969 1969 MSS 5.0 1970 12/1969 1970 Tops-10 5.01 DOS/Batch 11 MSS 6.0 1970 1970 3/1970 MSS 7.0 3/1970 MSS 8.0 6/1970 1971 RSTS-11 1971 1971 Tops-10 5.02 Tape Scope 2 KRONOS 1971 OS/8 Early 1970's Early 1970's VS/9 Chios 1971 VM/CMS Earl 1970's Early 1970's 1972 OS/VS1 Tops-10 5.03 BKY 1972 1972 1972 Early 1970's Tops-10 5.04 5/1972? KI-TELNEX Tops-10 5.05 mid 1972 7/1972? Tops-10 5.06 1973 11/1972 1973 VSE RSX-11D 5/1973 RT-11 OS/12 Alto 7/1973 1973 OS/VS2 r1 1974 1974 MSS 22.0 1974 RSX-11M 1/1974 1974 Tops-10 5.07 Tops-10 6.01 MR 1.0 CP/M 1.0 5/1974 5/1974 6/1974 1974 OS/VS2 r2 7/1974 1975 1975 OS/VS2 MVS r3 3/1975 Tops-10 5.07A Tops-10 6.01A 5/1975 5/1975 CP/M 1.3 1976 Tops-10 6.02 1975 RSX-11M Plus 1976 Tops-20 1 MSS 28.0 1976 2/1976 2/1976 Tops-20 1A 4/1976 Tops-20 1B 10/1976 Tops-20 101B 12/1976 1977 1977 Tops-10 6.03 p-System I.0 3/1977
    [Show full text]
  • The UNIX Time- Sharing System
    1. Introduction There have been three versions of UNIX. The earliest version (circa 1969–70) ran on the Digital Equipment Cor- poration PDP-7 and -9 computers. The second version ran on the unprotected PDP-11/20 computer. This paper describes only the PDP-11/40 and /45 [l] system since it is The UNIX Time- more modern and many of the differences between it and older UNIX systems result from redesign of features found Sharing System to be deficient or lacking. Since PDP-11 UNIX became operational in February Dennis M. Ritchie and Ken Thompson 1971, about 40 installations have been put into service; they Bell Laboratories are generally smaller than the system described here. Most of them are engaged in applications such as the preparation and formatting of patent applications and other textual material, the collection and processing of trouble data from various switching machines within the Bell System, and recording and checking telephone service orders. Our own installation is used mainly for research in operating sys- tems, languages, computer networks, and other topics in computer science, and also for document preparation. UNIX is a general-purpose, multi-user, interactive Perhaps the most important achievement of UNIX is to operating system for the Digital Equipment Corpora- demonstrate that a powerful operating system for interac- tion PDP-11/40 and 11/45 computers. It offers a number tive use need not be expensive either in equipment or in of features seldom found even in larger operating sys- human effort: UNIX can run on hardware costing as little as tems, including: (1) a hierarchical file system incorpo- $40,000, and less than two man years were spent on the rating demountable volumes; (2) compatible file, device, main system software.
    [Show full text]
  • David Walden and Raymond Nickerson
    Chapter 18 Distributed Computing at BBN Network Computing Software Infrastructure and Distributed Applications from 1970-1995 Richard Schantz In this article we review highlights of the history of BBN and distributed computing from a number of different perspectives: early investigations, distributed systems infrastructure (later to be more commonly known as Middleware), and network-centric applications which utilized the emerging distributed systems capabilities in new and innovative ways, with lasting impact. 18.1 Introduction The innovations being pursued in the area of packet switching and inter-computer communications (see Chapter 17 on networking) spawned a simultaneous interest and investigation into how to utilize this emerging new data oriented communication capability. To complement its activities in pioneering network communications, from the earliest conception of the ARPANET and continuing to this day, BBN initiated and participated in a number of the leading edge, innovative activities aimed at delivering value from the increasing interconnectivity through network centric applications and by providing the network centric infrastructure needed to more easily build these types of applications (see also Chapter 19 on email and 20 relating to distributed simulation). We use the term “Distributed Computing” to loosely tie together these activities covering both advanced, higher levels of multi-host1 infrastructure and the innovative distributed applications themselves, and to distinguish it from the lower level capabilities (e.g.,
    [Show full text]
  • MTS Volume 1, for Example, Introduces the User to MTS and Describes in General the MTS Operating System, While MTS Volume 10 Deals Exclusively with BASIC
    M T S The Michigan Terminal System The Michigan Terminal System Volume 1 Reference R1001 November 1991 University of Michigan Information Technology Division Consulting and Support Services DISCLAIMER The MTS manuals are intended to represent the current state of the Michigan Terminal System (MTS), but because the system is constantly being developed, extended, and refined, sections of this volume will become obsolete. The user should refer to the Information Technology Digest and other ITD documentation for the latest information about changes to MTS. Copyright 1991 by the Regents of the University of Michigan. Copying is permitted for nonprofit, educational use provided that (1) each reproduction is done without alteration and (2) the volume reference and date of publication are included. 2 CONTENTS Preface ........................................................................................................................................................ 9 Preface to Volume 1 .................................................................................................................................. 11 A Brief Overview of MTS .......................................................................................................................... 13 History .................................................................................................................................................. 13 Access to the System ...........................................................................................................................
    [Show full text]
  • Multinet for Openvms Administrator's Reference
    MultiNet for OpenVMS Administrator’s Reference March 2016 This guide provides information to configure and manage MultiNet for the experienced system manager. Before using this guide, install and start MultiNet as described in the MultiNet Installation and Introduction. Revision/Update: This guide supersedes the MultiNet Administrator's Reference, V5.4. Operating System/Version: VAX/VMS V5.5-2 or later, OpenVMS VAX V6.2 or later, or OpenVMS Alpha V6.2 or later, OpenVMS IA64 V8.2 or later Software Version: MultiNet 5.5 Process Software Framingham, Massachusetts USA The material in this document is for informational purposes only and is subject to change without notice. It should not be construed as a commitment by Process Software. Process Software assumes no responsibility for any errors that may appear in this document. Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. The following third-party software may be included with your product and will be subject to the software license agreement. Network Time Protocol (NTP). Copyright © 1992-2004 by David L. Mills. The University of Delaware makes no representations about the suitability of this software for any purpose. Point-to-Point Protocol. Copyright © 1989 by Carnegie-Mellon University. All rights reserved. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by Carnegie Mellon University.
    [Show full text]
  • Influential Operating Systems
    Influential CHAPTER Operating 20 Systems Now that you understand the fundamental concepts of operating systems (CPU scheduling, memory management, processes, and so on), we are in a position to examine how these concepts have been applied in several older and highly in¯uential operating systems. Some of them (such as the XDS-940 and the THE system) were one-of-a-kind systems; others (such as OS/360) are widely used. The order of presentation highlights the similarities and differences of the systems; it is not strictly chronological or ordered by importance. The serious student of operating systems should be familiar with all these systems. As we describe early systems, we include references to further reading. The papers, written by the designers of the systems, are important both for their technical content and for their style and ¯avor. Bibliographical Notes Description of looms and calculators are described in[Frah (2001)] and shown graphically in[Frauenfelder (2005)]. The Manchester Mark 1 is described by[Rojas and Hashagen (2000)] and its offspring, the Ferranti Mark 1, is described by[Ceruzzi (1998)]. The Atlas operating system is described by[Kilburn et al. (1961)] and [Howarth et al. (1961)]) The XDS-940 operating system is described by[Lichtenberger and Pirtle (1965)]. The THE operating system is described by[Dijkstra (1968)] and by[McKeag and Wilson (1976)]. The Venus system is described by[Liskov (1972)]. The RC 4000 system is described by[Brinch-Hansen (1970)] and[Brinch- Hansen (1973)]. The Compatible Time-Sharing System (CTSS) is described by[Corbato et al. (1962)]. The MULTICS operating system is described by[Corbato and Vyssotsky (1965)] and[Organick (1972)] TSS/360 is described by[Lett and Konigsford (1968)].
    [Show full text]
  • Compatible Time-Sharing System (1961-1973) Fiftieth Anniversary
    Compatible Time-Sharing System (1961-1973) Fiftieth Anniversary Commemorative Overview The Compatible Time Sharing System (1961–1973) Fiftieth Anniversary Commemorative Overview The design of the cover, half-title page (reverse side of this page), and main title page mimics the design of the 1963 book The Compatible Time-Sharing System: A Programmer’s Guide from the MIT Press. The Compatible Time Sharing System (1961–1973) Fiftieth Anniversary Commemorative Overview Edited by David Walden and Tom Van Vleck With contributions by Fernando Corbató Marjorie Daggett Robert Daley Peter Denning David Alan Grier Richard Mills Roger Roach Allan Scherr Copyright © 2011 David Walden and Tom Van Vleck All rights reserved. Single copies may be printed for personal use. Write to us at [email protected] for a PDF suitable for two-sided printing of multiple copies for non-profit academic or scholarly use. IEEE Computer Society 2001 L Street N.W., Suite 700 Washington, DC 20036-4928 USA First print edition June 2011 (web revision 03) The web edition at http://www.computer.org/portal/web/volunteercenter/history is being updated from the print edition to correct mistakes and add new information. The change history is on page 50. To Fernando Corbató and his MIT collaborators in creating CTSS Contents Preface . ix Acknowledgments . ix MIT nomenclature and abbreviations . x 1 Early history of CTSS . 1 2 The IBM 7094 and CTSS at MIT . 5 3 Uses . 17 4 Memories and views of CTSS . 21 Fernando Corbató . 21 Marjorie Daggett . 22 Robert Daley . 24 Richard Mills . 26 Tom Van Vleck . 31 Roger Roach .
    [Show full text]