Batch operating system - Revision history

Jnc: fmt

2022-09-10T06:41:07Z

fmt

← Older revision		Revision as of 06:41, 10 September 2022
Line 1:		Line 1:
	'''Batch''' [[operating system]]~~s were the first OS'~~s, and were common up to the 1980s or so; some are still running today. The essence of a batch OS is its lack of interaction with [[user]]s; a [[job]] - a [[program]], along with all its input data - is handed in to the system; when there is an opportunity, it is run; and any resultant output is provided back to the person who ~~sumitted~~ the job.		'''Batch operating systems''' were the first [[operating system]]s, and were common up to the 1980s or so; some are still running today. The essence of a batch OS is its lack of interaction with [[user]]s; a [[job]] - a [[program]], along with all its input data - is handed in to the system; when there is an opportunity, it is run; and any resultant output is provided back to the person who submitted the job.

	==Origins==		==Origins==
Line 7:		Line 7:
	An operational efficiency technique was adopted at an early stage: the programs and data of groups of jobs were collected onto [[magnetic tape]]; once a tape was full, it was mounted on a [[drive]], and all the jobs on it were run, with the output being [[spooling\|spooled]] to on another drive, to be printed on an off-line [[line printer]] later.		An operational efficiency technique was adopted at an early stage: the programs and data of groups of jobs were collected onto [[magnetic tape]]; once a tape was full, it was mounted on a [[drive]], and all the jobs on it were run, with the output being [[spooling\|spooled]] to on another drive, to be printed on an off-line [[line printer]] later.

	The time from when the job is submitted, to when the results are ready for the user, it called the 'turn-around'. That operational ~~approachs~~ unfortunately increased average turn-around times: it increased the efficiency of the computer (since tapes could be read a lot faster than [[punched card]] decks), but also increased the turn-around time considerably.		The time from when the job is submitted, to when the results are ready for the user, it called the 'turn-around'. That operational approach unfortunately increased average turn-around times: it increased the efficiency of the computer (since tapes could be read a lot faster than [[punched card]] decks), but also increased the turn-around time considerably.

	==Development==		==Development==

Jnc: Jnc moved page Batch to Batch operating system over a redirect without leaving a redirect

2022-09-09T12:49:07Z

Jnc moved page Batch to Batch operating system over a redirect without leaving a redirect

← Older revision		Revision as of 12:49, 9 September 2022
(No difference)

Jnc: +cat

2018-12-16T21:15:30Z

+cat

← Older revision		Revision as of 21:15, 16 December 2018
Line 19:		Line 19:
	With the advent of [[time-sharing]] and [[virtual memory]], all modern OS's tend to have the capability to run jobs in batch mode, and so specialized batch OS's have now faded out.		With the advent of [[time-sharing]] and [[virtual memory]], all modern OS's tend to have the capability to run jobs in batch mode, and so specialized batch OS's have now faded out.

	~~{{semi-stub}}~~		[[Category: OS Basics]]

Jnc: /* Origins */ bit more detail

2018-10-23T19:48:31Z

Origins: bit more detail

← Older revision		Revision as of 19:48, 23 October 2018
Line 5:		Line 5:
	They were a development of the earliest stages of computer use, when [[magnetic tape drive]]s were the principal [[secondary storage]] devices. Initially, users signed up for blocks of time on the computer; set-up, etc, meant that a lot of time on these rare and expensive machines was wasted.		They were a development of the earliest stages of computer use, when [[magnetic tape drive]]s were the principal [[secondary storage]] devices. Initially, users signed up for blocks of time on the computer; set-up, etc, meant that a lot of time on these rare and expensive machines was wasted.

	An operational efficiency technique was adopted at an early stage: the programs and data of groups of jobs were collected onto [[magnetic tape]]; once a tape was full, it was mounted on a [[drive]], and all the jobs on it were run.		An operational efficiency technique was adopted at an early stage: the programs and data of groups of jobs were collected onto [[magnetic tape]]; once a tape was full, it was mounted on a [[drive]], and all the jobs on it were run, with the output being [[spooling\|spooled]] to on another drive, to be printed on an off-line [[line printer]] later.

	The time from when the job is submitted, to when the results are ready for the user, it called the 'turn-around'. That operational ~~efficiency technique~~ unfortunately increased average turn-around times: it increased the efficiency of the computer (since tapes could be read a lot faster than [[punched card]] decks), but also increased the turn-around time considerably.		The time from when the job is submitted, to when the results are ready for the user, it called the 'turn-around'. That operational approachs unfortunately increased average turn-around times: it increased the efficiency of the computer (since tapes could be read a lot faster than [[punched card]] decks), but also increased the turn-around time considerably.

	==Development==		==Development==

Jnc: Copyedit for better flow

2018-10-23T15:12:57Z

Copyedit for better flow

← Older revision		Revision as of 15:12, 23 October 2018
Line 1:		Line 1:
	'''Batch''' [[operating system]]s were the first OS's, and were common up to the 1980s or so; some are still running today.		'''Batch''' [[operating system]]s were the first OS's, and were common up to the 1980s or so; some are still running today. The essence of a batch OS is its lack of interaction with [[user]]s; a [[job]] - a [[program]], along with all its input data - is handed in to the system; when there is an opportunity, it is run; and any resultant output is provided back to the person who sumitted the job.

	The essence of a batch OS is its lack of interaction with [[user]]s; a [[job]] - a [[program]], along with all its input data - is handed in to the system; when there is an opportunity, it is run; and any resultant output is provided back to the person who sumitted the job.		==Origins==

	~~The time from when~~ the ~~job is submitted~~, to when the results are ready for the user, it called the 'turn-around'. An operational efficiency technique adopted at an early stage unfortunately increased average turn-around times: groups of jobs were collected onto [[magnetic tape]]~~; once a tape was full, it was mounted on a~~ [[~~drive~~]], ~~and all the jobs~~ on ~~it were run. This increased the efficiency of~~ the computer ~~(since tapes could be read~~ a lot ~~faster than [[punched card]] decks), but also increased the turn-around~~ time ~~considerably~~		They were a development of the earliest stages of computer use, when [[magnetic tape drive]]s were the principal [[secondary storage]] devices. Initially, users signed up for blocks of time on the computer; set-up, etc, meant that a lot of time on these rare and expensive machines was wasted.

	~~The earliest batch OS's~~ were ~~not~~ [[~~multi-tasking~~]]; ~~each job ran to completion~~, ~~before the next job started. However, this did not make efficient use of~~ a ~~system; while a job is waiting for~~ [[~~input/output\|I/O~~]] ~~to complete~~, the ~~rest of the system was idle. This was especially a problem for the very expensive computers which~~ were ~~the norm at that stage~~.		An operational efficiency technique was adopted at an early stage: the programs and data of groups of jobs were collected onto [[magnetic tape]]; once a tape was full, it was mounted on a [[drive]], and all the jobs on it were run.

	~~Before [[interrupt]]s were added~~, ~~early computers did not have much of a choice; they~~ ''~~had'' to spend~~ a lot ~~of time watching~~ [[~~peripheral~~]]s, ~~waiting for them to complete an operation~~ - ~~generally [[magnetic tape drive]]s, since those were the principal [[secondary storage]] devices at that point in~~ time.		The time from when the job is submitted, to when the results are ready for the user, it called the 'turn-around'. That operational efficiency technique unfortunately increased average turn-around times: it increased the efficiency of the computer (since tapes could be read a lot faster than [[punched card]] decks), but also increased the turn-around time considerably.

	Once interrupts were available, multi-tasking was added, because having a mix of jobs running at any time is the best way to maximize the use of the system. However, this brought in other issues: e.g. in the earliest stages of this change, all jobs which were running at any time had to be resident in [[main memory]] together. This then required the addition of security, so that a job which encountered a programing mistake could not damage other job(s).		==Development==

	With the advent of [[time-sharing]] and [[virtual memory]], all modern OS's tend to have the capability to run jobs in batch mode, and so specialized batch OS's ~~are~~ now ~~fading~~ out.		The earliest batch OS's were not [[multi-tasking]]; each job ran to completion, before the next job started. However, this did not make efficient use of a system; while a job was waiting for [[input/output\|I/O]] to complete, the rest of the system was idle.

			Before [[interrupt]]s were added, early computers did not have much of a choice; they ''had'' to spend a lot of time watching [[peripheral]]s, waiting for them to complete an operation.

			Once interrupts were available, multi-tasking was added, because having a mix of jobs running at any time is the best way to maximize the use of the system. However, this brought in other issues: e.g. in the earliest stages of this change, all jobs which were running at any time had to be resident in [[main memory]] together, which might not be possible. This also required the addition of security, so that a job which encountered a programing mistake could not damage other job(s).

			With the advent of [[time-sharing]] and [[virtual memory]], all modern OS's tend to have the capability to run jobs in batch mode, and so specialized batch OS's have now faded out.

	{{semi-stub}}		{{semi-stub}}

Jnc: punch decks

2018-10-23T00:06:46Z

punch decks

← Older revision		Revision as of 00:06, 23 October 2018
Line 3:		Line 3:
	The essence of a batch OS is its lack of interaction with [[user]]s; a [[job]] - a [[program]], along with all its input data - is handed in to the system; when there is an opportunity, it is run; and any resultant output is provided back to the person who sumitted the job.		The essence of a batch OS is its lack of interaction with [[user]]s; a [[job]] - a [[program]], along with all its input data - is handed in to the system; when there is an opportunity, it is run; and any resultant output is provided back to the person who sumitted the job.

	The time from when the job is submitted, to when the results are ready for the user, it called the 'turn-around'. An operational efficiency technique adopted at an early stage unfortunately increased average turn-around times: groups of jobs were collected onto [[magnetic tape]]; once a tape was full, it was mounted on a [[drive]], and all the jobs on it were run. This increased the efficiency of the computer, but also increased the turn-around time considerably		The time from when the job is submitted, to when the results are ready for the user, it called the 'turn-around'. An operational efficiency technique adopted at an early stage unfortunately increased average turn-around times: groups of jobs were collected onto [[magnetic tape]]; once a tape was full, it was mounted on a [[drive]], and all the jobs on it were run. This increased the efficiency of the computer (since tapes could be read a lot faster than [[punched card]] decks), but also increased the turn-around time considerably

	The earliest batch OS's were not [[multi-tasking]]; each job ran to completion, before the next job started. However, this did not make efficient use of a system; while a job is waiting for [[input/output\|I/O]] to complete, the rest of the system was idle. This was especially a problem for the very expensive computers which were the norm at that stage.		The earliest batch OS's were not [[multi-tasking]]; each job ran to completion, before the next job started. However, this did not make efficient use of a system; while a job is waiting for [[input/output\|I/O]] to complete, the rest of the system was idle. This was especially a problem for the very expensive computers which were the norm at that stage.

Jnc: Mention collecting jobs increased turn-around

2018-10-22T23:01:07Z

Mention collecting jobs increased turn-around

← Older revision		Revision as of 23:01, 22 October 2018
Line 1:		Line 1:
	'''Batch''' [[operating system]]s were the first OS's, and were common up to the 1980s or so; some are still running today.		'''Batch''' [[operating system]]s were the first OS's, and were common up to the 1980s or so; some are still running today.

	The essence of a batch OS is its lack of interaction with [[user]]s; a [[job]] - a [[program]], along with all its input data - is handed in to the system; when there is an opportunity, it is run; and any resultant output is provided back to the person who sumitted the job~~. The time from when the job is submitted, to when the results are ready for the user, it called the 'turn-around'~~.		The essence of a batch OS is its lack of interaction with [[user]]s; a [[job]] - a [[program]], along with all its input data - is handed in to the system; when there is an opportunity, it is run; and any resultant output is provided back to the person who sumitted the job.

	The earliest batch OS's were not [[multi-tasking]]; each job ran to completion, before the next job started. However, this did not make efficient use of a system; while a job is waiting for [[input/output\|I/O]] to complete, the rest of the system is idle. This was especially a problem for the very expensive computers which were the norm at that stage.		The time from when the job is submitted, to when the results are ready for the user, it called the 'turn-around'. An operational efficiency technique adopted at an early stage unfortunately increased average turn-around times: groups of jobs were collected onto [[magnetic tape]]; once a tape was full, it was mounted on a [[drive]], and all the jobs on it were run. This increased the efficiency of the computer, but also increased the turn-around time considerably

			The earliest batch OS's were not [[multi-tasking]]; each job ran to completion, before the next job started. However, this did not make efficient use of a system; while a job is waiting for [[input/output\|I/O]] to complete, the rest of the system was idle. This was especially a problem for the very expensive computers which were the norm at that stage.

	Before [[interrupt]]s were added, early computers did not have much of a choice; they ''had'' to spend a lot of time watching [[peripheral]]s, waiting for them to complete an operation - generally [[magnetic tape drive]]s, since those were the principal [[secondary storage]] devices at that point in time.		Before [[interrupt]]s were added, early computers did not have much of a choice; they ''had'' to spend a lot of time watching [[peripheral]]s, waiting for them to complete an operation - generally [[magnetic tape drive]]s, since those were the principal [[secondary storage]] devices at that point in time.

Jnc: Role of interrupts

2018-10-22T22:41:06Z

Role of interrupts

← Older revision		Revision as of 22:41, 22 October 2018
Line 1:		Line 1:
	'''Batch''' [[operating system]]s were the first OS's, and were common up the 1980s or so; some are still running today.		'''Batch''' [[operating system]]s were the first OS's, and were common up to the 1980s or so; some are still running today.

	The essence of a batch OS is its lack of interaction with [[user]]s; a [[job]] - a [[program]], along with all its input data - is handed in to the system; when there is an opportunity, it is run; and any resultant output is provided back to the person who sumitted the job. The time from when the job is submitted, to when the results are ready for the user, it called the 'turn-around'.		The essence of a batch OS is its lack of interaction with [[user]]s; a [[job]] - a [[program]], along with all its input data - is handed in to the system; when there is an opportunity, it is run; and any resultant output is provided back to the person who sumitted the job. The time from when the job is submitted, to when the results are ready for the user, it called the 'turn-around'.

	The earliest batch OS's were not [[multi-tasking]]; each job ran to completion, before the next job started. However, this ~~does~~ not make efficient use of a system; while a job is waiting for [[input/output\|I/O]] to complete, the rest of the system is idle. This was especially a problem for the very expensive computers which were the norm at that stage.		The earliest batch OS's were not [[multi-tasking]]; each job ran to completion, before the next job started. However, this did not make efficient use of a system; while a job is waiting for [[input/output\|I/O]] to complete, the rest of the system is idle. This was especially a problem for the very expensive computers which were the norm at that stage.

	So multi-tasking was added, because having a mix of jobs running at any time is the best way to maximize the use of the system. However, this brought in other issues: e.g. in the earliest stages of this change, all jobs which were running at any time had to be resident in [[main memory]] together. This then required the addition of security, so that a job which encountered a programing mistake could not damage other job(s).		Before [[interrupt]]s were added, early computers did not have much of a choice; they ''had'' to spend a lot of time watching [[peripheral]]s, waiting for them to complete an operation - generally [[magnetic tape drive]]s, since those were the principal [[secondary storage]] devices at that point in time.

			Once interrupts were available, multi-tasking was added, because having a mix of jobs running at any time is the best way to maximize the use of the system. However, this brought in other issues: e.g. in the earliest stages of this change, all jobs which were running at any time had to be resident in [[main memory]] together. This then required the addition of security, so that a job which encountered a programing mistake could not damage other job(s).

	With the advent of [[time-sharing]] and [[virtual memory]], all modern OS's tend to have the capability to run jobs in batch mode, and so specialized batch OS's are now fading out.		With the advent of [[time-sharing]] and [[virtual memory]], all modern OS's tend to have the capability to run jobs in batch mode, and so specialized batch OS's are now fading out.

	{{semi-stub}}		{{semi-stub}}

Jnc: +turnaround

2018-10-21T01:10:40Z

+turnaround

← Older revision		Revision as of 01:10, 21 October 2018
Line 1:		Line 1:
	'''Batch''' [[operating system]]s were the first OS's, and were common up the 1980s or so; some are still running today.		'''Batch''' [[operating system]]s were the first OS's, and were common up the 1980s or so; some are still running today.

	The essence of a batch OS is its lack of interaction with [[user]]s; a [[job]] - a [[program]], along with all its input data - is handed in to the system; when there is an opportunity, it is run; and any resultant output is provided back to the person who sumitted the job.		The essence of a batch OS is its lack of interaction with [[user]]s; a [[job]] - a [[program]], along with all its input data - is handed in to the system; when there is an opportunity, it is run; and any resultant output is provided back to the person who sumitted the job. The time from when the job is submitted, to when the results are ready for the user, it called the 'turn-around'.

	The earliest batch OS's were not [[multi-tasking]]; each job ran to completion, before the next job started. However, this does not make efficient use of a system; while a job is waiting for [[input/output\|I/O]] to complete, the rest of the system is idle. This was especially a problem for the very expensive computers which were the norm at that stage.		The earliest batch OS's were not [[multi-tasking]]; each job ran to completion, before the next job started. However, this does not make efficient use of a system; while a job is waiting for [[input/output\|I/O]] to complete, the rest of the system is idle. This was especially a problem for the very expensive computers which were the norm at that stage.

Jnc: Need for security, too

2018-09-29T22:20:12Z

Need for security, too

← Older revision		Revision as of 22:20, 29 September 2018
Line 5:		Line 5:
	The earliest batch OS's were not [[multi-tasking]]; each job ran to completion, before the next job started. However, this does not make efficient use of a system; while a job is waiting for [[input/output\|I/O]] to complete, the rest of the system is idle. This was especially a problem for the very expensive computers which were the norm at that stage.		The earliest batch OS's were not [[multi-tasking]]; each job ran to completion, before the next job started. However, this does not make efficient use of a system; while a job is waiting for [[input/output\|I/O]] to complete, the rest of the system is idle. This was especially a problem for the very expensive computers which were the norm at that stage.

	So multi-tasking was added, because having a mix of jobs running at any time is the best way to maximize the use of the system. However, this brought in other issues: e.g. in the earliest stages of this change, all jobs which were running at any time had to be resident in [[main memory]] together.		So multi-tasking was added, because having a mix of jobs running at any time is the best way to maximize the use of the system. However, this brought in other issues: e.g. in the earliest stages of this change, all jobs which were running at any time had to be resident in [[main memory]] together. This then required the addition of security, so that a job which encountered a programing mistake could not damage other job(s).

	With the advent of [[time-sharing]] and [[virtual memory]], all modern OS's tend to have the capability to run jobs in batch mode, and so specialized batch OS's are now fading out.		With the advent of [[time-sharing]] and [[virtual memory]], all modern OS's tend to have the capability to run jobs in batch mode, and so specialized batch OS's are now fading out.

	{{stub}}		{{semi-stub}}