Batch Operating System:
In early computer systems, the user did not have interplay immediately with the computer system. The information and programs were first prepared on the input media such as punched cards or punched tape. The information and programs prepared on the punched tape or punched cards were often called jobs. These jobs were submitted to the computer operator. The computer operator would most probably arrange the jobs into proper sequence is termed batches and run the batches through the computer. The batch operating system was used to deal with and control such type of operations.
The simple batch operating system transfers the jobs to the processor one by one. When one job is achieved, then control is transferred to next job. For instance, if first job is set to print a document on printer and 2nd job is to execute a program for creating and editing text document. In this case, when first job is achieved most effective then the 2nd job is started.
The first batch operating system was developed inside of the mid-nineteen fifties by General Motors for IBM 701 computers. This system was revised and then implemented on the IBM 704 computers. By the early nineteen sixties, quite a number vendors had developed batch processing systems for his or her computers notwithstanding the most popular batch operating system was "IBSYS" of IBM. This operating system was developed for the IBM 7090 / 7094 computers.
Timesharing Operating System:
Timesharing system is a multiprogramming, multiprocessing and interactive system. It lets in multiple users to share the computer at an analogous time. This system executes multiple jobs of users by switching between them. Timesharing is used when multiple users are mounted to a single computer in a communication network. Each user accesses the computer with its own terminal.
Timesharing operating system uses the CPU scheduling. Each user is assigned a small time unit is termed time slice. The job of a user executes inside of its time slice. When the allocated time period for a task is used, the next job is allocated to it. This technique continues in a cycle. Thus at an everyday time intervals, some users may well also logout from the system, while new users may well also login into the system.
The processor switches so rapidly from one user to the next and each user feels that the entire computer system is devoted to his use. So the users may well most probably have interplay with their programs, while they are running.
In timesharing system (like multiprogramming system), multiple jobs are in addition simultaneously loaded in leading memory. The leading memory cannot accommodate all these jobs at an analogous time. In this case, the jobs are stored on the disk inside of the job pool. The jobs in job pool await allocation of leading memory. If several jobs are ready to be brought into memory, and if there is not very enormously simply right enough room for all of them, then the system ought to require memory leadership. Similarly, if many jobs are ready to run at an analogous time, the system ought to schedule these jobs. The time-sharing systems ought to in addition provide a file system leadership to deal with the input and output information of the multiple users.
Timesharing system (and multiprogramming system) in addition creates challenges for the operating system. If there are multiple jobs in memory, then they has to be protected from interfering with each other such as modifying each other's information.
One of the first timesharing operating system was the Compatible Time-Sharing System (CTSS). This operating system was first developed for the IBM 709 in 1961 and later transferred to IBM 7094. Nowadays examples of imperative timesharing operating systems are UNIX, Linux, Windows NT Server and Windows 2000 Server.
No comments:
Post a Comment