Global Fixed Priority Scheduling with Deferred Pre-Emption

Total Page:16

File Type:pdf, Size:1020Kb

Global Fixed Priority Scheduling with Deferred Pre-Emption Global Fixed Priority Scheduling with Deferred Pre-emption R.I. Davis, A. Burns J. Marinho, V. Nelis, S.M. Petters M. Bertogna University of York, UK. CISTER/INESC-TEC, ISEP, Porto, Portugal. University of Modena, Italy. {rob.davis, alan.burns}@york.ac.uk {jmsm, nelis, smp}@isep.ipp.pt [email protected] Abstract— This paper introduces schedulability analysis for emption (gFPDS). gFPDS can be viewed as a superset of global fixed priority scheduling with deferred pre-emption both global fixed priority pre-emptive scheduling (gFPPS) (gFPDS) for homogeneous multiprocessor systems. gFPDS is a and global fixed priority non-pre-emptive scheduling superset of global fixed priority pre-emptive scheduling (gFPPS) (gFPNS) and strictly dominates both. With gFPDS, there are and global fixed priority non-pre-emptive scheduling (gFPNS). two key parameters that affect schedulability: the priority We show how schedulability can be improved via appropriate choice of priority assignment and final non-pre-emptive region assigned to each task, and the length of each task’s final non- lengths, and we provide algorithms which optimize schedulability pre-emptive region (FNR). The FNR length affects both the in this way. An experimental evaluation shows that gFPDS schedulability of the task itself, and the schedulability of significantly outperforms both gFPPS and gFPNS. tasks with higher priorities. This is a trade-off as increasing the FNR length can improve schedulability for the task itself I. INTRODUCTION by reducing the number of times it can be pre-empted, but A common misconception with regard to fixed priority potentially increases the blocking effect on higher priority scheduling of sporadic tasks is that fully pre-emptive tasks which may reduce their schedulability. scheduling is more effective in terms of schedulability than In 2012, Davis and Bertogna [27] introduced an optimal non-pre-emptive scheduling. The two are however algorithm for fixed priority scheduling with deferred pre- incomparable; there are tasksets that are schedulable under emption on a single processor. This algorithm finds a fixed priority non-pre-emptive scheduling that are not schedulable priority assignment and set of FNR lengths schedulable under fixed priority pre-emptive scheduling and whenever such a schedulable combination exists. In this vice-versa. This is the case for uniprocessor scheduling [27] paper we also build upon this work, extending it to the and also the case for global multiprocessor scheduling [30], multiprocessor case. For a given priority ordering, we show which is the focus of this paper. how to find an assignment of FNR lengths that result in a While the blocking effect, due to long non-pre-emptive system that is deemed schedulable under gFPDS according regions of low priority tasks degrades schedulability for to our sufficient schedulability tests, whenever such an single processor systems that have a wide range of task assignment exists of FNR lengths exists. We also show that execution times and periods (as illustrated by Figure 7 in the Final Non-pre-emptive Region and Priority Assignment [27]), Guan et al. [30] showed that the same is not (FNR-PA) algorithm from [27] is not optimal in the necessarily true for multiprocessor systems. With m multiprocessor case, but nevertheless can be used as a processors rather than one, long non-pre-emptive regions can heuristic for determining both priority ordering and final be accommodated without necessarily compromising the non-pre-emptive region lengths. schedulability of higher priority tasks. However, this advantage only extends so far; with m processors then m II. BACKGROUND RESEARCH long non-pre-emptive regions are enough to significantly A. Deferred pre-emption compromise schedulability. In this context, limited non-pre- Two different models of fixed priority scheduling with emptive execution has the advantage of reducing the number deferred pre-emption have been developed in the literature. of pre-emptions, and potentially improving the worst-case In the fixed model, introduced by Burns in 1994 [19], the response time of tasks, while also keeping blocking effects location of each non-pre-emptive region is statically on higher priority tasks within tolerable limits. determined prior to execution. Pre-emption is only permitted In the literature, the term fixed priority scheduling with at pre-defined locations in the code of each task, referred to deferred pre-emption has been used to refer to a variety of as pre-emption points. This method is also referred to as co- different techniques by which pre-emptions may be deferred operative scheduling, as tasks co-operate, providing re- for some interval of time after a higher priority task becomes scheduling / pre-emption points to improve schedulability. ready. These are described in a survey by Buttazzo et al. [21] In the floating model [7], [32], an upper bound is given and briefly discussed in Section II. In this paper, we assume on the length of the longest non-pre-emptive region of each a simple form of fixed priority scheduling with deferred pre- task. However, the location of each non-pre-emptive region emption where each task has a single non-pre-emptive region is not known a priori and may vary at run-time, for example at the end of its execution. If this region is of the minimum under the control of the operating system. possible length for all tasks, then we have fully pre-emptive For uniprocessor systems: Exact schedulability analysis scheduling, whereas if it constitutes all of the task’s for the fixed model was derived by Bril et al. in 2009 [18]. execution time then we have non-pre-emptive scheduling. Subsequently, Bertogna et al. integrated pre-emption costs In this paper, we introduce sufficient schedulability tests and cache related pre-emption delays (CRPD) into analysis for global fixed priority scheduling with deferred pre- of the fixed model, considering both fixed [14] and variable [15] pre-emption costs. In 2011, Bertogna et al. [16] derived Tasks are assumed to comply with the sporadic task a method for computing the optimal FNR length of each task model. In this model, each task gives rise to a potentially in order to maximize schedulability assuming a given unbounded sequence of jobs. Each job may arrive at any priority assignment. In 2012, Davis and Bertogna [27] time once a minimum inter-arrival time has elapsed since the introduced an optimal algorithm that is able to find a arrival of the previous job of the same task. τ schedulable combination of priority assignment and FNR Each task i is characterised by its relative deadline Di , ≤ lengths whenever such a schedulable combination exists. worst-case execution time Ci ( Ci Di ), and minimum B. Global fixed priority scheduling inter-arrival time or period Ti . It is assumed that all tasks have constrained deadlines ( D ≤ T ). The utilisation U of In 2003, Baker [5] developed a strategy that underpins an i i i each task is given by Ci /Ti . Under gFPDS, each task is extensive thread of subsequent research into schedulability assumed to have a final non-pre-emptive region of length F tests for gFPPS [9], [11], [12], [13], [29], [31], and gFPNS i in the range [1,Ci ] (Here, the minimum value is 1 rather [30]. (For a comprehensive survey of multiprocessor real- than 0 as a task can only be pre-empted at discrete times time scheduling, the reader is referred to [26]). Baker’s work corresponding to processor clock cycles). Finding an was subsequently built upon by Bertogna et al. [11] [13]. appropriate FNR length for each task is assumed to be part of They developed sufficient schedulability tests for gFPPS the scheduling problem. based on bounding the maximum workload in a given The worst-case response time Ri of a task is the longest interval. In 2007, Bertogna and Cirinei [12] adapted this possible time from the release of the task until it completes approach to iteratively compute an upper bound on the τ ≤ execution. Thus task i is schedulable if and only if Ri Di response time of each task, using the upper bound response ∀ ≤ and a taskset is schedulable if and only if i Ri Di . We times of other tasks to limit the amount of interference UB use Ri to indicate an upper bound on the worst-case considered. In 2009, Guan et al. [31] extended this approach τ response time of task i . using ideas from [8] to limit the amount of carry-in Under gFPDS, at any given time, the m ready tasks with interference. the highest priorities are selected for execution. Final non- In 2009 and 2010, Davis and Burns [22], [23] showed pre-emptive regions are assumed to be implemented by that priority assignment is fundamental to the effectiveness manipulating task priorities, thus a task executing its FNR of gFPPS. They proved that Audsley’s optimal priority has the highest priority and will not be pre-empted. assignment algorithm [3], [4] is applicable to some of the The tasks are assumed to be independent and so cannot sufficient tests developed for gFPPS, including the deadline- be blocked from executing by another task, other than due to based test of Bertogna et al. [13], but not to others such as contention for the processors. Further, it is assumed that once the later response time tests [12], [31]. a job starts to execute it will not voluntarily suspend itself. In 2011, Guan et al. [30] provided schedulability analysis Job parallelism is not permitted; hence, at any given time, for gFPNS based on the approach of Baker [5], and the each job may execute on at most one processor. As a result techniques introduced by Bertogna et al. in [11]. of pre-emption and subsequent resumption, a job may gFPDS is broadly similar to the dynamic algorithm FPZL migrate from one processor to another.
Recommended publications
  • Task Scheduling Balancing User Experience and Resource Utilization on Cloud
    Rochester Institute of Technology RIT Scholar Works Theses 7-2019 Task Scheduling Balancing User Experience and Resource Utilization on Cloud Sultan Mira [email protected] Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Mira, Sultan, "Task Scheduling Balancing User Experience and Resource Utilization on Cloud" (2019). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. Task Scheduling Balancing User Experience and Resource Utilization on Cloud by Sultan Mira A Thesis Submitted in Partial Fulfillment of the Requirements for the Degree of Master of Science in Software Engineering Supervised by Dr. Yi Wang Department of Software Engineering B. Thomas Golisano College of Computing and Information Sciences Rochester Institute of Technology Rochester, New York July 2019 ii The thesis “Task Scheduling Balancing User Experience and Resource Utilization on Cloud” by Sultan Mira has been examined and approved by the following Examination Committee: Dr. Yi Wang Assistant Professor Thesis Committee Chair Dr. Pradeep Murukannaiah Assistant Professor Dr. Christian Newman Assistant Professor iii Dedication I dedicate this work to my family, loved ones, and everyone who has helped me get to where I am. iv Abstract Task Scheduling Balancing User Experience and Resource Utilization on Cloud Sultan Mira Supervising Professor: Dr. Yi Wang Cloud computing has been gaining undeniable popularity over the last few years. Among many techniques enabling cloud computing, task scheduling plays a critical role in both efficient resource utilization for cloud service providers and providing an excellent user ex- perience to the clients.
    [Show full text]
  • Resource Access Control Facility (RACF) General User's Guide
    ----- --- SC28-1341-3 - -. Resource Access Control Facility -------_.----- - - --- (RACF) General User's Guide I Production of this Book This book was prepared and formatted using the BookMaster® document markup language. Fourth Edition (December, 1988) This is a major revision of, and obsoletes, SC28-1341- 3and Technical Newsletter SN28-l2l8. See the Summary of Changes following the Edition Notice for a summary of the changes made to this manual. Technical changes or additions to the text and illustrations are indicated by a vertical line to the left of the change. This edition applies to Version 1 Releases 8.1 and 8.2 of the program product RACF (Resource Access Control Facility) Program Number 5740-XXH, and to all subsequent versions until otherwise indicated in new editions or Technical Newsletters. Changes are made periodically to the information herein; before using this publication in connection with the operation of IBM systems, consult the latest IBM Systemj370 Bibliography, GC20-0001, for the editions that are applicable and current. References in this publication to IBM products or services do not imply that IBM· intends to make these available in all countries in which IBM operates. Any reference to an IBM product in this publication is not intended to state or imply that only IBM's product may be used. Any functionally equivalent product may be used instead. This statement does not expressly or implicitly waive any intellectual property right IBM may hold in any product mentioned herein. Publications are not stocked at the address given below. Requests for IBM publications should be made to your IBM representative or to the IBM branch office serving your locality.
    [Show full text]
  • 3.A Fixed-Priority Scheduling
    2017/18 UniPD - T. Vardanega 10/03/2018 Standard notation : Worst-case blocking time for the task (if applicable) 3.a Fixed-Priority Scheduling : Worst-case computation time (WCET) of the task () : Relative deadline of the task : The interference time of the task : Release jitter of the task : Number of tasks in the system Credits to A. Burns and A. Wellings : Priority assigned to the task (if applicable) : Worst-case response time of the task : Minimum time between task releases, or task period () : The utilization of each task ( ⁄) a-Z: The name of a task 2017/18 UniPD – T. Vardanega Real-Time Systems 168 of 515 The simplest workload model Fixed-priority scheduling (FPS) The application is assumed to consist of tasks, for fixed At present, the most widely used approach in industry All tasks are periodic with known periods Each task has a fixed (static) priority determined off-line This defines the periodic workload model In real-time systems, the “priority” of a task is solely derived The tasks are completely independent of each other from its temporal requirements No contention for logical resources; no precedence constraints The task’s relative importance to the correct functioning of All tasks have a deadline equal to their period the system or its integrity is not a driving factor at this level A recent strand of research addresses mixed-criticality systems, with Each task must complete before it is next released scheduling solutions that contemplate criticality attributes All tasks have a single fixed WCET, which can be trusted as The ready tasks (jobs) are dispatched to execution in a safe and tight upper-bound the order determined by their (static) priority Operation modes are not considered Hence, in FPS, scheduling at run time is fully defined by the All system overheads (context-switch times, interrupt handling and so on) are assumed absorbed in the WCETs priority assignment algorithm 2017/18 UniPD – T.
    [Show full text]
  • The CICS/MQ Interface
    1 2 Each application program which will execute using MQ call statements require a few basic inclusions of generated code. The COPY shown are the one required by all applications using MQ functions. We have suppressed the list of the CMQV structure since it is over 20 pages of COBOL variable constants. The WS‐VARIABLES are the minimum necessary to support bot getting and putting messages from and to queues. The MQ‐CONN would normally be the handle acquired by an MQCONN function, but that call along with the MQDISC call are ignored by CICS / MQ interface. It is CICS itself that has performed the MQCONN to the queue manager. The MQ‐HOBJ‐I and MQ‐HOBJ‐O represent the handles, acquired on MQOPEN for a queue, used to specify which queue the other calls relate to. The MQ‐COMPCODE and MQ‐REASON are the variables which the application must test after every MQ call to determine its success. 3 This slide contains the message input and output areas used on the MQGET and MQPUT calls. Our messages are rather simple and limited in size. SO we have put the data areas in the WORKING‐STORAGE SECTION. Many times you will have these as copy books rather than native COBOL variables. Since the WORKING‐STORAGE area is being copied for each task using the program, we recommend that larger messages areas be put into the LINKAGE SECTION. Here we use a size of 200‐300 K as a suggestion. However, that size will vary depending upon your CICS environment. When the application is using message areas in the LINKAGE SECTION, it will be responsible to perform a CICS GETMAIN command to acquire the storage for the message area.
    [Show full text]
  • Introduction to Xgrid: Cluster Computing for Everyone
    Introduction to Xgrid: Cluster Computing for Everyone Barbara J. Breen1, John F. Lindner2 1Department of Physics, University of Portland, Portland, Oregon 97203 2Department of Physics, The College of Wooster, Wooster, Ohio 44691 (First posted 4 January 2007; last revised 24 July 2007) Xgrid is the first distributed computing architecture built into a desktop operating system. It allows you to run a single job across multiple computers at once. All you need is at least one Macintosh computer running Mac OS X v10.4 or later. (Mac OS X Server is not required.) We provide explicit instructions and example code to get you started, including examples of how to distribute your computing jobs, even if your initial cluster consists of just two old laptops in your basement. 1. INTRODUCTION Apple’s Xgrid technology enables you to readily convert any ad hoc collection of Macintosh computers into a low-cost supercomputing cluster. Xgrid functionality is integrated into every copy of Mac OS X v10.4. For more information, visit http://www.apple.com/macosx/features/xgrid/. In this article, we show how to unlock this functionality. In Section 2, we guide you through setting up the cluster. In Section 3, we illustrate two simple ways to distribute jobs across the cluster: shell scripts and batch files. We don’t assume you know what shell scripts, batch files, or C/C++ programs are (although you will need to learn). Instead, we supply explicit, practical examples. 2. SETTING UP THE CLUSTER In a typical cluster of three or more computers (or processors), a client computer requests a job from the controller computer, which assigns an agent computer to perform it.
    [Show full text]
  • GEMTC: GPU Enabled Many-Task Computing
    GEMTC: GPU Enabled Many-Task Computing Scott Krieder, Ioan Raicu Department of Computer Science Illinois Institute of Technology Chicago, IL USA [email protected], [email protected] Abstract— Current software and hardware limitations prevent acceleration on HPC resources. However, a programmability gap still Many-Task Computing (MTC) workloads from leveraging exists between applications and accelerators. Researchers and hardware accelerators (NVIDIA GPUs, Intel Xeon Phi) boasting developers are forced to work within the constraints of closed Many-Core Computing architectures. Some broad application environments such as the CUDA GPU Programming Framework[3] classes that fit the MTC paradigm are workflows, MapReduce, (for NVIDIA GPUs). The goal of this work is to improve the high-throughput computing, and a subset of high-performance performance of MTC workloads running on GPUs through the use of computing. MTC emphasizes using many computing resources the GEMTC framework. The CUDA framework can only support over short periods of time to accomplish many computational 16 kernels running concurrently, one kernel per streaming tasks (i.e. including both dependent and independent tasks), multiprocessor (SM). One problem with this approach is that where the primary metrics are measured in seconds. MTC has all kernels must start and end at the same time, causing extreme already proven successful in Grid Computing and inefficiencies in heterogeneous workloads. By working at the Supercomputing on MIMD architectures, but the SIMD architectures of today’s accelerators pose many challenges in the warp level, (which sits between cores and SMs) I can trade efficient support of MTC workloads on accelerators. This work local memory for concurrency, and I am able to run up to 200 aims to address the programmability gap between MTC and concurrent kernels.
    [Show full text]
  • Real-Time Operating Systems with Example PICOS18
    Real-Time Operating Systems With Example PICOS18 Sebastian Fischmeister 1 What is an Operating System? . A program that acts as an intermediary between a user of a computer and the computer hardware . Operating system goals: o Execute user programs and make solving user problems easier. o Make the computer system convenient to use . Use the computer hardware in an efficient manner CSE480/CIS700 S. Fischmeister 2 1 Computer System Components 1. Hardware – provides basic computing resources (CPU, memory, I/O devices) 2. Operating system – controls and coordinates the use of the hardware among the various application programs for the various users 3. Applications programs – define the ways in which the system resources are used to solve the computing problems of the users (compilers, database systems, video games, business programs) 4. Users (people, machines, other computers) CSE480/CIS700 S. Fischmeister 3 Abstract View of System Components CSE480/CIS700 S. Fischmeister 4 2 What is an RTOS? . Often used as a control device in a dedicated application such as controlling scientific experiments, medical imaging systems, industrial control systems, and some display systems . Well-defined fixed-time constraints CSE480/CIS700 S. Fischmeister 5 More Precisely? . The system allows access to sensitive resources with defined response times. o Maximum response times are good for hard real-time o Average response times are ok for soft real-time . Any system that provides the above can be classified as a real-time system o 10us for a context switch, ok? o 10s for a context switch, ok? CSE480/CIS700 S. Fischmeister 6 3 Taxonomy of RTOSs .
    [Show full text]
  • Z/OS, Language Environment, and UNIX How They Work Together
    The Trainer’s Friend, Inc. 256-B S. Monaco Parkway Telephone: (800) 993-8716 Denver, Colorado 80224 (303) 393-8716 U.S.A. Fax: (303) 393-8718 E-mail: [email protected] Internet: www.trainersfriend.com z/OS, Language Environment, and UNIX How They Work Together The following terms that may appear in these materials are trademarks or registered trademarks: Trademarks of the International Business Machines Corporation: AD/Cycle, AIX, AIX/ESA, Application System/400, AS/400, BookManager, CICS, CICS/ESA, COBOL/370, COBOL for MVS and VM, COBOL for OS/390 & VM, Common User Access, CORBA, CUA, DATABASE 2, DB2, DB2 Universal Database, DFSMS, DFSMSds, DFSORT, DOS/VSE, Enterprise System/3090, ES/3090, 3090, ESA/370, ESA/390, Hiperbatch, Hiperspace, IBM, IBMLink, IMS, IMS/ESA, Language Environment, MQSeries, MVS, MVS/ESA, MVS/XA, MVS/DFP, NetView, NetView/PC, Object Management Group, Operating System/400, OS/400, PR/SM, OpenEdition MVS, Operating System/2, OS/2, OS/390, OS/390 UNIX, OS/400, QMF, RACF, RS/6000, SOMobjects, SOMobjects Application Class Library, System/370, System/390, Systems Application Architecture, SAA, System Object Model, TSO, VisualAge, VisualLift, VTAM, VM/XA, VM/XA SP, WebSphere, z/OS, z/VM, z/Architecture, zSeries Trademarks of Microsoft Corp.: Microsoft, Windows, Windows NT, Windows ’95, Windows ’98, Windows 2000, Windows SE, Windows XP Trademark of Chicago-Soft, Ltd: MVS/QuickRef Trademark of Phoenix Software International: (E)JES Registered Trademarks of Institute of Electrical and Electronic Engineers: IEEE, POSIX Registered Trademark of The Open Group: UNIX Trademark of Sun Microsystems, Inc.: Java Registered Trademark of Linus Torvalds: LINUX Registered Trademark of Unicode, Inc.: Unicode Preface This document came about as a result of writing my first course for UNIX on the IBM mainframe.
    [Show full text]
  • MTS on Wikipedia Snapshot Taken 9 January 2011
    MTS on Wikipedia Snapshot taken 9 January 2011 PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sun, 09 Jan 2011 13:08:01 UTC Contents Articles Michigan Terminal System 1 MTS system architecture 17 IBM System/360 Model 67 40 MAD programming language 46 UBC PLUS 55 Micro DBMS 57 Bruce Arden 58 Bernard Galler 59 TSS/360 60 References Article Sources and Contributors 64 Image Sources, Licenses and Contributors 65 Article Licenses License 66 Michigan Terminal System 1 Michigan Terminal System The MTS welcome screen as seen through a 3270 terminal emulator. Company / developer University of Michigan and 7 other universities in the U.S., Canada, and the UK Programmed in various languages, mostly 360/370 Assembler Working state Historic Initial release 1967 Latest stable release 6.0 / 1988 (final) Available language(s) English Available programming Assembler, FORTRAN, PL/I, PLUS, ALGOL W, Pascal, C, LISP, SNOBOL4, COBOL, PL360, languages(s) MAD/I, GOM (Good Old Mad), APL, and many more Supported platforms IBM S/360-67, IBM S/370 and successors History of IBM mainframe operating systems On early mainframe computers: • GM OS & GM-NAA I/O 1955 • BESYS 1957 • UMES 1958 • SOS 1959 • IBSYS 1960 • CTSS 1961 On S/360 and successors: • BOS/360 1965 • TOS/360 1965 • TSS/360 1967 • MTS 1967 • ORVYL 1967 • MUSIC 1972 • MUSIC/SP 1985 • DOS/360 and successors 1966 • DOS/VS 1972 • DOS/VSE 1980s • VSE/SP late 1980s • VSE/ESA 1991 • z/VSE 2005 Michigan Terminal System 2 • OS/360 and successors
    [Show full text]
  • CICS and Threadsafe Exploiting the Open Transaction Environment
    CICS and Threadsafe Exploiting the Open Transaction Environment Russ Evans [email protected] Objectives • History of Multithreading • The Open Transaction Environment • Making programs Threadsafe • Exploiting the OTE • OTE Performance Considerations • Diagnosing Threadsafe Problems • Recommendations Copyright (c) 2013, The Evans Group, Inc. 2 History of Multithreading • CICS as a Single TCB – Most efficient on a uni-processor – “Quasi-Reentrancy” – Issues: • Runaway tasks • OS Waits = Region Wait • Many restricted OS and COBOL Commands • Limited by speed of one processor Copyright (c) 2013, The Evans Group, Inc. 3 History of Multithreading • CICS Exploiting Multiple Processors – Multiple TCBs – Primary TCB is “QR”, Quasi-Reentrant – Additional TCBs for: • VSAM • DB2 • Program Loader • etc. Copyright (c) 2013, The Evans Group, Inc. 4 History of Multithreading • CICS and DB2 – Separate TCB („thread‟) for each DB2 Request – Task is switched to DB2 TCB for DB2 work, DB2 system code runs on DB2 TCB – Significant workload shifted to DB2 TCBs, but measurable overhead from TCB switching Copyright (c) 2013, The Evans Group, Inc. 5 Open Transaction Environment • Transaction runs under own TCB • Introduced in TS 1.3 for Java • DB2 Support added for TS 2.2 • Supports full OS function • Allows true Multitasking in CICS • Pseudo-reentrancy no longer allowed Copyright (c) 2013, The Evans Group, Inc. 6 OTE and DB2 Without Threadsafe QR TCB Open TCB Task Starts EXEC CICS EXEC SQL DB2 Code executes Application Code DB2 Code completes EXEC SQL DB2 Code executes DB2 Code completes Copyright (c) 2013, The Evans Group, Inc. 7 OTE and DB2 With Threadsafe QR TCB Open TCB Task Starts EXEC CICS EXEC SQL DB2 Code executes Application Code DB2 Code executes Task Termination Task completes Copyright (c) 2013, The Evans Group, Inc.
    [Show full text]
  • Operating Systems 1
    GENERAL I ARTICLE Operating Systems 1. Objectives and Evolution M Suresh Babu In this article we examine the objectives and fun.ctions of operating systems, and then we trace the evolution of oper­ ating systems from the first manual system to the current multiprogrammed and time-shared systems. Introduction M Suresh Babu is currently a fourth year An operating system (OS) is a program that controls the execu­ undergraduate student in tion of an application program and acts as an interface between the Department of the user of a computer and computer hardware. The purpose of Computer Science and an OS is to provide an environment in which a user can execute Engineering, Narayana Engineering College, programs in a convenient and efficient manner. Nellore, Andhra Pradesh. He would like to work in The operating system must provide certain services to programs operating systems, and to the users of those programs in order to make the program­ computer networks and ming task easier. The specific services provided will, of course, also in Internet security concepts. differ from one OS to another, but there are some common classes of services that we identify and explore in this article. After reading this article you can understand the reasons behind development of OS and appreciate the tasks an OS does and how it does them. What is an Operating System? An operating system is an important part of almost every com­ puter system. An OS is similar to a government; a resource allocator and a control program. As a government the OS performs no useful function by itself, it simply provides a good environment.
    [Show full text]
  • IBM OS/360: an Overview of the First General Purpose Mainframe
    IBM OS/360: An Overview of the First General Purpose Mainframe CS 550-2: Operating Systems Fall 2003 E. Casey Lunny 1 Table of Contents Introduction............................................................................................................3 “A Second Generation OS”...................................................................................3 Secondary Design Goals...................................................................................4 Processor Modes...................................................................................................5 Jobs and Tasks.....................................................................................................5 Degrees of Multiprocessing...............................................................................6 Data Sharing.....................................................................................................7 Job and Task Management...............................................................................7 Allowable Process States..................................................................................8 Memory Management............................................................................................8 Overview of Memory Management Techniques (Fig. 1)...............................9 Memory Structure and Implementation.............................................................9 Deadlock.............................................................................................................10 Mutual exclusion
    [Show full text]