OPERATING SYSTEMS

History Click to edit Master subtitle style Terms Concepts

Definition
4 OS is a program that acts as an intermediary

between a user of a computer and the computer hardware. 4 Its main purpose is to provide an environment in which a user can execute programs. 4 Its primary goal is to make the computer system convenient to use the computer hardware and use it in efficient manner.

Functions
4 Resource allocator - it manages all

resources. 4 Control program - controls execution of user program to prevent errors and improper use of computer. 4 Acts as kernel - it runs at all times.

History
4 Programmer write the program and operate

the program directly from the operators console.

programs are loaded manually that involves switches programmers monitor the program running through the lights on the console use of machine is done by sign-up or reservation scheme.

importance : hands-on interactive nature problem: computer usage is not maximized and often times it is idle (depending on the number of hours the machine is reserved)

4 Assemblers, loaders, and linkers were

designed to ease the programming task.

library of common functions were created and the programmer just copy it if needed implement the use of card readers, line printers, and magnetic tapes subroutines were created for an I/O device called device driver

4 Compilers were created used for FORTRAN and COBOL e.g. process:

FORTRAN/COBOL program COMPILE (compiler) ASSEMBLE (result of compile- assembly language) LINK (link library) BINARY code

problem: it needs significant amount of set-up time (mounting of tapes)

4 Simple monitor to utilize machine usage:

hire professional computer operator

no idle time set-up time was reduced (more experience for operator) problem arises in debugging of programs (a dump of memory and registers were taken and given to the programmer)

jobs with similar needs were BATCHED together and run through the computer as a group

reduced set-up time (e.g. FORTRAN-COBOL-FORTRAN is done FORTRAN-FORTRAN-COBOL to save operator time in mounting compiler tapes)

problem: when a job stops (normal or abnormal termination) the operator takes a dump of memory and registers and restart the computer in which case the CPU is idle. solution: automatic job sequencing - first rudimentary OS were created - done by a resident monitor (always in memory) - automatically transferring control from one job to the next. process: computer on invoke resident monitor transfer control to a program transfer control to monitor (upon termination) next program

How will the resident monitor know which program to execute? operator is provided with program and data control cards were introduced (directives to the resident monitor indicating which program is to be run) example: $FTN - execute FORTRAN COMPILER

$ASM - execute ASSEMBLER $RUN - execute user program $JOB - first card of a job $END - last card of a job

to identify control cards a special character is added at the first column of the control card (e.g. $,//,etc.) CONTROL CARD INTERPRETER - reading and carrying out the instructions on the cards at the point of execution.

4 Off-line operation results from: CPU are often idle because mechanical devices are slow than electronic devices slow I/O devices means waiting time (idle time) for CPU solution: off-line operation process: online: card reader - CPU - line printer off-line: card reader - tape drives - CPU - tape drives - line printer

writing from cards to magnetic tapes and output magnetic tapes to line printer were done off-line using a dedicated small computer - referred to as satellite of the main computer (process is called satellite processing) advantage: the main computer was no longer constrained by the speed of the card readers and line printers, but was limited by only the speed of the much faster magnetic tape units.