DOCSLIB.ORG

TOPS-20 System Manager's Guide | Electronic Distribution | June 1990 This Document Is Intended for the Person Who Is

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
TOPS-20 System Manager's Guide | Electronic Distribution | June 1990 This Document Is Intended for the Person Who Is TOPS-20 System Manager's Guide | Electronic Distribution | June 1990 This document is intended for the person who is responsible for making final decisions for setting up and maintaining the efficient operation of a TOPS-20 installation. Change bars in margins indicate material that has been added or changed since the previous printing of this manual. OPERATING SYSTEM: TOPS-20 (KL Model B) Version 7.0 digital equipment corporation maynard, massachusetts First Printing, September 1985 Revised, June 1988 | Revised, June 1990 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. | Copyright C 1985, 1988, 1990 Digital Equipment Corporation All Rights Reserved. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: CI DECtape LA50 SITGO-10 DDCMP DECUS LN01 TOPS-10 DEC DECwriter LN03 TOPS-20 DECmail DELNI MASSBUS TOPS-20AN DECnet DELUA PDP UNIBUS DECnet-VAX HSC PDP-11/24 UETP DECserver HSC-50 PrintServer VAX DECserver 100 KA10 PrintServer 40 VAX/VMS DECserver 200 KI Q-bus VT50 DECsystem-10 KL10 ReGIS DECSYSTEM-20 KS10 RSX d i g i t a l CONTENTS PREFACE CHAPTER 1 DOCUMENTATION 1.1 DOCUMENTS AVAILABLE FROM DIGITAL . 1-1 1.2 DOCUMENTS PREPARED AT YOUR INSTALLATION . 1-2 1.2.1 System Log . 1-3 1.2.2 Mountable Structure Sign-Up Log . 1-6 1.2.3 System Access Request Form . 1-6 1.2.4 Operator Work Request Form . 1-9 1.2.5 Operator Shift Change Log . 1-9 CHAPTER 2 PREPARING FOR SOFTWARE INSTALLATION 2.1 SECURING THE COMPUTER ROOM . 2-1 2.2 HANDLING USER REQUESTS . 2-1 2.3 ORDERING SUPPLIES . 2-2 2.4 SCHEDULING OPERATOR TASKS . 2-2 2.5 SELECTING SYSTEM FEATURES . 2-4 CHAPTER 3 AFTER SOFTWARE INSTALLATION 3.1 OVERVIEW . 3-1 3.2 SPECIAL SYSTEM DIRECTORIES . 3-1 3.2.1 <ROOT-DIRECTORY> . 3-2 3.2.2 <SYSTEM> . 3-3 3.2.3 Restoring the Directory <SYSTEM> . 3-6 3.2.4 <SUBSYS> . 3-7 3.2.5 Restoring the Directory <SUBSYS> . 3-16 3.2.6 <NEW-SYSTEM> and <NEW-SUBSYS> . 3-17 3.2.7 <ACCOUNTS>, <OPERATOR>, <SPOOL>, and <SYSTEM-ERROR> . 3-18 3.2.8 Other Useful Directories . 3-18 3.3 SYSTEM-LOGICAL NAMES . 3-20 3.3.1 SYSTEM: . 3-21 3.3.2 SYS: . 3-21 3.3.3 NEW: . 3-21 3.3.4 OLD: . 3-22 3.3.5 HLP: . 3-22 3.3.6 SERR: . 3-22 3.3.7 DMP: . 3-23 3.3.8 DEFAULT-EXEC: . 3-23 3.3.9 POBOX: . 3-24 3.3.10 NRT: . 3-24 3.3.11 SPOOL: . 3-25 iii 3.4 CONSOLE FRONT-END FILES . 3-25 3.5 TAILORING THE BATCH SYSTEM . 3-29 3.6 CHECKING THE SOFTWARE (UETP) . 3-29 3.7 REMOTE PRINTERS . 3-30 3.7.1 Remote Printing Requirements . 3-31 3.7.2 Defining DQS and LAT Printers . 3-32 3.7.3 Setting DQS Printing Characteristics . 3-33 3.8 TERMINAL PRINTERS . 3-34 CHAPTER 4 CREATING STRUCTURES 4.1 OVERVIEW . 4-1 4.2 THE SYSTEM STRUCTURE . 4-2 4.2.1 What Is the System Structure? . 4-2 4.2.2 The Contents of the System Structure . 4-3 4.3 ONE-STRUCTURE SYSTEMS . 4-4 4.4 MOUNTABLE STRUCTURES . 4-5 4.4.1 Differences Between Mountable and System Structures . 4-5 4.4.2 Similarities Between Mountable and System Structures . 4-5 4.5 MULTIPLE-STRUCTURE SYSTEMS . 4-7 4.5.1 Choosing Structure Names . 4-9 4.5.2 Mounting Structures Having the Same Name . 4-11 4.5.3 Maximum Size of Structures . 4-11 4.5.4 Increasing the Size of Structures . 4-13 4.5.5 Setting Up Structures for Maximum Availability 4-14 4.5.6 Taking Structures Off-Line . 4-15 4.5.7 Mounting Structures from Another Installation 4-16 4.6 SHARING STRUCTURES (DISK DRIVES) BETWEEN TWO SYSTEMS . 4-17 4.7 DETERMINING SWAPPING SPACE ON THE SYSTEM STRUCTURE . 4-19 4.7.1 What Is Swapping? . 4-19 4.7.2 When to Increase Swapping Space . 4-19 4.8 DETERMINING THE AVAILABLE DISK SPACE . 4-21 4.8.1 Determining Disk Space Before Installation . 4-21 4.8.2 Determining Disk Space After Installation . 4-23 CHAPTER 5 CREATING DIRECTORIES 5.1 HAVING THE OPERATOR CREATE AND MAINTAIN ALL DIRECTORIES (CENTRAL CONTROL) . 5-2 5.2 DELEGATING THE CREATION AND MAINTENANCE OF DIRECTORIES TO PROJECT ADMINISTRATORS (PROJECT CONTROL) . 5-2 5.3 COMBINING CENTRAL AND PROJECT CONTROL . 5-3 5.4 CENTRAL AND PROJECT CONTROL DESCRIPTIONS . 5-3 5.4.1 Central Control . 5-4 5.4.2 Central Control Using Subdirectories . 5-7 iv 5.4.3 Project Control . 5-14 5.4.4 Combined Central and Project Control . 5-22 5.5 ALLOCATING DISK STORAGE QUOTAS . 5-23 5.6 ENFORCING DISK STORAGE QUOTAS . 5-24 5.7 PROTECTING DIRECTORIES AND FILES . 5-26 5.7.1 Directory and File Protection Digits . 5-26 5.7.2 Changing Directory and File Protection . 5-29 5.8 ESTABLISHING GROUPS . 5-29 5.9 GIVING USERS SPECIAL CAPABILITIES . 5-38 5.10 PRINTING DIRECTORY INFORMATION . 5-40 CHAPTER 6 CREATING ACCOUNTS 6.1 SETTING UP THE SYSTEM TO USE ACCOUNTS . 6-2 6.1.1 Enabling or Disabling Account Validation . 6-2 6.1.2 Setting up Account Validation with Existing Files . 6-2 6.1.3 Setting up the System for Accounting Shift Changes . 6-3 6.2 SELECTING AN ACCOUNTING SCHEME . 6-3 6.3 CREATING AN ACCOUNT DATA BASE . 6-7 6.3.1 Entering Accounting Data into Files . 6-8 6.3.2 Sample Data Files . 6-14 6.3.3 Running the ACTGEN Program . 6-17 6.3.4 Data Base Failures/Recovery . 6-19 6.4 VALIDATING ACCOUNTS . 6-19 CHAPTER 7 SYSTEM BACKUP PROCEDURES 7.1 SAVING ALL FILES IN ALL DIRECTORIES . 7-2 7.1.1 Full Dumps . 7-3 7.1.2 Incremental Dumps . 7-3 7.1.3 Security of Backup Tapes . 7-4 7.2 A COMMON BACKUP POLICY . 7-4 7.3 MAGNETIC TAPE REQUIREMENTS . 7-4 7.4 MAKING A SYSTEM CRASH TAPE . 7-6 7.5 MAKING A CRASH TAPE USING BATCH . 7-8 7.6 SAVING THE CONSOLE FRONT-END FILE SYSTEM . 7-10 CHAPTER 8 TAPE STORAGE 8.1 FILE ARCHIVING . 8-2 8.1.1 Setting Up the System to Use File Archiving . 8-3 8.1.2 What Happens When Users Archive Files . 8-3 8.1.3 What Happens When Users Retrieve Files . 8-5 8.1.4 When to Create Archive Tapes . 8-5 8.1.5 Processing Retrieval Requests . 8-7 8.2 FILE MIGRATION . 8-7 8.2.1 Setting Up the System to Use File Migration . 8-8 v 8.2.2 Using the REAPER Program . 8-8 8.2.3 Using the DUMPER Program . 8-10 8.2.4 Processing Retrieval Requests for Migrated Files . 8-11 8.2.5 Recycling Migration (and Archive) Tapes . 8-11 8.3 TAPE DRIVE ALLOCATION . 8-12 8.3.1 When to Use Tape Drive Allocation . 8-12 8.3.2 How to Enable/Disable Tape Drive Allocation . 8-13 8.3.3 Tape Mounting Policy . 8-13 8.4 TAPE LABELING . 8-13 8.4.1 Why Tape Labels? . 8-14 8.4.2 Setting Up the System to Use Tape Labels . 8-16 8.4.3 Initializing Tapes and Drives to Use Labels . 8-17 8.5 SHARING TAPE DRIVES BETWEEN TWO SYSTEMS . 8-18 CHAPTER 9 SYSTEM PROBLEMS/CRASHES 9.1 RESTORING A SINGLE FILE . 9-2 9.2 RESTORING A SINGLE DIRECTORY . 9-2 9.3 RESTORING <ROOT-DIRECTORY> . 9-3 9.3.1 Rebuilding the System Structure <ROOT-DIRECTORY> 9-5 9.4 RESTORING THE ENTIRE FILE SYSTEM . 9-9 9.4.1 Re-creating the File System on the System Structure . 9-9 9.4.2 Re-creating Mountable Structures . 9-10 9.5 POWER FAILURES . 9-11 9.6 REMOTE DIAGNOSTIC LINK (KLINIK) . 9-11 9.7 MAKING THE CI UNAVAILABLE ON NON-CFS SYSTEMS . 9-12 9.8 MAKING THE NI UNAVAILABLE . 9-12 9.9 OFFLINE DISKS . 9-12 9.9.1 Operator Procedures . 9-13 9.10 DUMPING ON NON-FATAL SYSTEM ERRORS . 9-14 9.10.1 Enabling DUMP-ON-BUGCHK . 9-14 9.10.2 Disabling DUMP-ON-BUGCHK . 9-14 9.10.3 "Dumpable Structures" . 9-15 9.10.4 Copying the Dump File . 9-15 9.10.5 Time Considerations . 9-16 9.10.6 Controlling DUMP-ON-BUGCHK . 9-17 CHAPTER 10 SYSTEM PERFORMANCE 10.1 THE CLASS SCHEDULER . 10-2 10.1.1 Overview . 10-2 10.1.2 Who Should Use the Class Scheduler? . 10-4 10.1.3 How to Begin Using the Class Scheduler . 10-6 10.1.4 Procedures to Turn On the Class Scheduler . 10-8 10.1.5 Changing Class Percentages During Timesharing 10-10 10.1.6 Disabling the Class Scheduler During Timesharing .
Load more

Recommended publications
  • 1.Operating Systems Overview
    OPERATING SYSTEMS OVERVIEW Contents O.S.Functions The Evolution of O.S. Characteristics of O.S. Basic hardware elements 1 Contents O.S.Components System calls O.S.Structure USER 1 USER 2 USER 3 USER n compiler text interpreter database editor system operating system computer hardware 2 Programming system components compilers loader linker comand interpreter (shell) … O.S. purposes to make a computer more convenient and easier to use to allow more efficient operations of the whole computer system 3 To simplify the program development The O.S. masks the details of the hardware from the programmer and provides the programmer with a convenient interface for using system resources (system calls) To simplify the program development Definition of an extended (virtual) machine 4 VIRTUAL MACHINE ES: DISK CONTROLLER commands: read, write, head motion, ecc… parameters: sector address, number of sectors for each track, ecc… state and error conditions 5 Hardware resource allocation Access to system resources must be controlled and conflicts for resource contention resolved Hardware resource allocation Any user should be provided with required resources, by following suitable policies 6 The details for the management of hardware resources must be hidden to users System calls provide the interface between the application programs and the O.S. 7 THE EVOLUTION OF O.S. Serial processing No O.S. Control by console Scheduling Setup time 8 Simple batch systems Monitor Resident in main memory Control of the program execution “batch” solution
    [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]
  • Tops-10 Monitor Calls Manual, Vol. 1
    TOPS-10 Monitor Calls Manual Volume 1 AA-097 4G-TB October 1988 This manual describes the functions that the monitor performs to service monitor calls from assembly language programs. The TOPS-10 Monitor Calls Manual Is divided Into two volumes: Volume 1 covers the facilities and functions of the monitor; Volume 2 describes the- monitor calls, calling sequences, symbols, and GETTAB tables. This manual supe-rsedes the previous manual of the same name, SOC order number AA-0974F-TB. Operating System: . TOPS-10 Version 7.04 Software: GALAXY Version 5.1 digital equipment corporation maynard, massachusetts First Printing, November 1975 Revised, May 1977 Revised, January 1978 Revised, August 1980 Revised, February 1984 Revised, April 1986 Revised, October 1988 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Copyright © 1975, 1984, 1988 Digital Equipment Corporation All Rights Reserved. Printed in U.S.A. The Reader's Comments form on the last page of this document requests the user's critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: CI DECtape LA50 SITGO-10 DDCMP DECUS LN01 TOPS-10 DEC DECwriter LN03 TOPS-20 DECmail DELNI MASSBUS TOPS-20AN DECnet DELUA PDP UNIBUS DECnet-VAX HSC PDP-11/24 UETP DECserver HSC-50 PrintServer VAX DECserver 100 KA10 PrintServer 40 VAXNMS DECserver 200 KI Q-bus VT50 DECsystem-10 KL10 AeGIS DECSYSTEM-20 KS10 RSX ~BmBDmDTM CONTENTS PREFACE CHAPTER 1 INTRODUCTION TO MONITOR CALLS 1.1 MONITOR CALL SYMBOLS .
    [Show full text]
  • The UNIX Time-Sharing System
    1. Introduction ACM Symposium on Operating Systems Principles There have been three versions of UNIX. The earliest Yorktown Heights, N.Y.: October, 1963 version (circa 1969-70) ran on the Digital Equipment Corporation PDP-7 and -9 computers. The second ver. sion ran on the unprotected PDP.~~'20 computer. hi^ paper describes only the PDP-ll 40 and .'45 [I] system System The UNIX Time- since it is more modern and many of the diferences The UNMO Time-Sharing between it and older UNlx systems result from redesign Dennis M. Ritchie and Ken Thompson Sharing System of features found to be deficient or lacking. Since PDP-l l UNIX became operational in February July, 1974 Dennis M. Ritchie and Ken Thompson 1971, about 40 installations have been put into service; Volume 17, Number 7 Bell Laboratories they are generally smaller than the system described here. Most of them are engaged in applications such as pp. 365-375 the preparation and formatting of patent applications and other textual material, the collection and processing of trouble data from vartous switching machines within the Bell System, and recording and checking telephone service orders. Our own installation is used mainly machines, most notably the PDP-I1 family. for research in operating systems, languages, com- UNIPhas become one of the most widely puter networks, and other topics in computer scienc', known and imitated operating systems of all The genius of Ritchie and Thompson is in UNIX is a general-purpose, multi-user, interactive and also for document preparation. time. Ken Thompson, in working on a pro- their selection of a subset of the most pow- operating system for the Digital Equipment Corporation Perhaps the most important achievement of L.NIX PDP-II/~Oand 11/45 computers.
    [Show full text]
  • Openvms I/O User's Reference Manual
    OpenVMS I/O User’s Reference Manual Order Number: AA–PV6SD–TK April 2001 This manual contains the information necessary to interface directly with the I/O device drivers supplied as part of the Compaq OpenVMS operating system. Several examples of programming techniques are included. This document does not contain information on I/O operations using the OpenVMS Record Management Services. Revision/Update Information: This manual supersedes the OpenVMS I/O User’s Reference Manual, OpenVMS Alpha Version 7.2, OpenVMS VAX Version 7.2 Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation Compaq, VAX, VMS, and the Compaq logo Registered in U.S. Patent and Trademark Office. OpenVMS and Tru64 are trademarks of Compaq Information Technologies Group, L.P in the United States and other countries. Microsoft, MS-DOS, Visual C++, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States and other countries. Intel, Intel Inside, and Pentium are trademarks of Intel Corporation in the United States and other countries. Motif, OSF/1, and UNIX are trademarks of The Open Group in the United States and other countries. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein.
    [Show full text]
  • TOPS-10 Version 7.04 Monitor Internals Course
    TOPS-10 Version 7.04 Monitor Internals Course This document is the student guide that accompanies the TOPS-10 Version 7.04 Monitor Internals Course. Revision/Update Information: Version 1.0 Digital Equipment Corporation June 1989 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Copyright ©1986, 1987, 1988, 1989 by Digital Equipment Corporation All Rights Reserved. Printed in U.S.A. The postpaid READER'S COM:MENTS form on the last page of this document requests the user's critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC DIBOL UNIBUS DEC/CMS EduSystem VAX DECIMMS lAS VAXcluster DECnet MASSBUS VMS DECsystem-10 PDP VT DECSYSTEM-20 PDT DECUS RSTS DECwriter RSX This document was prepared using VAX DOCUMENT, Version 1.1 Contents Chapter 1 Introduction to the TOPS-10 Monitor 1.1 User Program Addressing ............................................... 1-1 1.2 Monitor Calls ......................................................... 1-3 1.3 Interrupts ........................................................... 1-3 1.4 The Monitor .......................................................... 1-3 1.5 Structure of the Monitor .................................... "............ 1-4 1.6 The Monitor as an Event Processor ........................................ 1-5 Chapter 2 Monitor Cycle 2.1 The Control Routine ...................................................
    [Show full text]
  • PATHWORKS: PC Integration Software
    PATHWORKS: PC Integration Software Digital Technical] ournal Digital Equipment Corporation Volume 4 Number 1 Winter 1992 Editorial Jane C. Blake, Editor Kathleen M. Stetson, Associate Editor Helen L. Patterson, Associate Editor Circulation Catherine M. Phillips, Administrator Sherry L. Gonzalez Production Mildred R. Rosenzweig, Production Editor Margaret L. Burdine, Typographer Peter R. Woodbury, Illustrator Advisory Board Samuel H. Fuller, Chairman Robert M. Glorioso Richard]. Hollingsworth John W McCredie Alan G. Nemeth Mahendra R. Patel F. Grant Saviers Victor A. Vyssotsky Gayn B. Winters The Digital Technicaljournal is published quarterly by Digital Equipment Corporation, 146 Main Street ML01-3/B68, Maynard, Massachusetts 01754-2571. Subscriptions to thejournal are $40.00 for four issues and must be prepaid in U.S. funds. University and college professors and Ph.D. students in the electrical engineering and computer science fields receive complimentary subscriptions upon request. Orders, inquiries, and address changes should be sent to the Digital Technicaljournal at the published-by address. Inquiries can also be sent electronically to DTJ®CRL.DEC.COM. Single copies and back issues are available for $16.00 each from Digital Press of Digital Equipment Corporation, 1 Burlington Woods Drive, Burlington, MA 01830-4597 Digital employees may send subscription orders on the ENET to ROVAX::JOURNAL or by interoffice mail to mailstop ML01-3/B68. Orders should include badge number, site location code, and address. All employees must advise of changes of address. Comments on the content of any paper are welcomed and may be sent to the editor at the published-by or network address. Copyright© 1992 Digital Equipment Corporation.
    [Show full text]
  • TOPS-10 Operating System Commands Manual AA-0916F-TB
    TOPS-10 Operating System Commands Manual AA-0916F-TB October 1988 This manual contains descriptions of the TOPS-10 monitor commands, their formats and their usage. This manual replaces the TOPS-10 Operating System Commands Manual, . order number AA-0916E-TB. Operating System: TOPS-10 Version 7.04 Software: GALAXY Version 5.1 digital equipment corporation, maynard, massachusetts Firat Printing, July 1975 Revised, August 1977 Revised, March 1978 Revised, August 1980 Updated, July 1982 Updated, February 1984 Revised, April 1986 Revised, October 1988 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Copyright © 1975, 1984, 1988 Digital Equipment Corporation All Rights Reserved. Printed in U.S.A. The Reader's Comments form on the last page of this document requests the user's critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: CI DECtape LA50 SITGO-10 DDCMP DECUS LN01 TOPS-10 DEC DECwriter LN03 TOPS-20 DECmail DELNI MASSBUS TOPS-20AN DEC net DELUA PDP UNIBUS DECnet-VAX HSC PDP-11/24 UETP DECserver HSC-50 PrintServer VAX DECserver 100 KA10 PrintServer 40 VAXNMS DECserver 200 KI Q-bus VT50 DECsystem-10 KL10 ReGIS DECSYSTEM-20 KS10 RSX ~DmDDmDTM CONTENTS PREFACE CHAPTER 1 INTRODUCTION 1.1 JOBS .
    [Show full text]
  • CA IT Client Manager Software Delivery Administration Guide
    CA IT Client Manager Software Delivery Administration Guide 12.8 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
    [Show full text]
  • Introduction
    CHAPTER1 Introduction Chapter 1 introduces the general topic of operating systems and a handful of important concepts (multiprogramming, time sharing, distributed system, and so on). The purpose is to show why operating systems are what they are by showing how they developed. In operating systems, as in much of computer science, we are led to the present by the paths we took in the past, and we can better understand both the present and the future by understanding the past. Additional work that might be considered is learning about the particular systems that the students will have access to at your institution. This is still just a general overview, as specific interfaces are considered in Chapter 3. Exercises 1.13 In a multiprogramming and time-sharing environment, several users share the system simultaneously. This situation can result in various security problems. a. What are two such problems? b. Can we ensure the same degree of security in a time-shared ma- chine as in a dedicated machine? Explain your answer. Answer: a. Stealing or copying one’s programs or data; using system resources (CPU, memory,disk space, peripherals) without proper accounting. b. Probably not, since any protection scheme devised by humans can inevitably be broken by a human, and the more complex the scheme, the more difficult it is to feel confident of its correct imple- mentation. 1.14 The issue of resource utilization shows up in different forms in differ- ent types of operating systems. List what resources must be managed carefully in the following settings: a. Mainframe or minicomputer systems 1 2 Chapter 1 Introduction b.
    [Show full text]
  • Operating Systems and Middleware: Supporting Controlled Interaction
    Operating Systems and Middleware: Supporting Controlled Interaction Max Hailperin Gustavus Adolphus College Revised Edition 1.1.6 January 5, 2014 Copyright c 2011{2013 by Max Hailperin. This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License. To view a copy of this license, visit http:// creativecommons.org/ licenses/ by-sa/ 3.0/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA. To my family iv Contents Preface xi 1 Introduction 1 1.1 Chapter Overview . .1 1.2 What Is an Operating System? . .2 1.3 What is Middleware? . .6 1.4 Objectives for the Book . .8 1.5 Multiple Computations on One Computer . .9 1.6 Controlling the Interactions Between Computations . 11 1.7 Supporting Interaction Across Time . 13 1.8 Supporting Interaction Across Space . 15 1.9 Security . 17 2 Threads 21 2.1 Introduction . 21 2.2 Example of Multithreaded Programs . 23 2.3 Reasons for Using Concurrent Threads . 27 2.4 Switching Between Threads . 30 2.5 Preemptive Multitasking . 37 2.6 Security and Threads . 38 3 Scheduling 45 3.1 Introduction . 45 3.2 Thread States . 46 3.3 Scheduling Goals . 49 3.3.1 Throughput . 51 3.3.2 Response Time . 54 3.3.3 Urgency, Importance, and Resource Allocation . 55 3.4 Fixed-Priority Scheduling . 61 v vi CONTENTS 3.5 Dynamic-Priority Scheduling . 65 3.5.1 Earliest Deadline First Scheduling . 65 3.5.2 Decay Usage Scheduling . 66 3.6 Proportional-Share Scheduling . 71 3.7 Security and Scheduling .
    [Show full text]
  • The Design of TEX and METAFONT: a Retrospective Nelson H
    The Design of TEX and METAFONT: A Retrospective Nelson H. F. Beebe Department of Mathematics University of Utah Salt Lake City, UT 84112-0090 USA Practical TEX 2005 talk... – p.1/36 Prehistory (1452–1970) METAFONT 500-year-long tradition of typesetting expert human typographers with decades of experience hand setting of type in lines and racks letters stored into upper and lower cases (bins) hot-lead process proprietary handmade punch-cut fonts X and typesetting on spread of two facing pages publishersE have editors and proofreaders T typesetting and book binding done by job shops Practical TEX 2005 talk... – p.2/36 Typesetting on computers (1970–) METAFONT expert human typographers, but now hampered by technology typographically substandard quality expensive and proprietary typesetting computer hardware and software optical font scaling proprietary optical fonts Xsee and NHFB’s 25 Years of TEX and METAFONT: Looking Back and Looking Forward: TUG’2003 Keynote AddressE , TUGboat 25(1) 7–30 (2004) T see DEK’s Digital Typography (1999) Practical TEX 2005 talk... – p.3/36 Knuth’s sabbatical year (1977–1978) METAFONT improve typesetting of The Art of Computer Programming books I didn’t know what to do. I had spent 15 years writing those books, but if they were going to look awful I didn’t want to write any more. How could I be proud of such a product? — DEK (1996 Kyoto Prize address) reproduce look of Linotype Modern 8a fonts of earlier editions X and 0.x-MIPS departmental computers (notably, 16-bit PDP-11E and 36-bit PDP-10) T computer use still cost $$$$ for many people Practical TEX 2005 talk..
    [Show full text]