Job - Revision history

Jnc: Tweaks

2025-07-21T09:47:05Z

Tweaks

Jnc: +typically in object code form

2022-09-11T00:25:20Z

+typically in object code form

Vaxorcist: Added a stack of punched cards as an typical example of an old fashioned job.

2022-09-10T20:46:16Z

Added a stack of punched cards as an typical example of an old fashioned job.

Jnc: Avoid dab

2022-09-09T13:02:44Z

Avoid dab

Jnc: +cat

2018-12-16T21:13:07Z

+cat

Jnc: typo

2018-09-30T02:02:30Z

typo

Jnc: A good start

2018-09-29T22:45:38Z

A good start

New page

The term '''job''' is not precisely defined, but it generally means a unit of work for a computer; e.g. an [[application]] together with its input data, often for a [[batch]] [[operating system]].

A [[user]] would hand in his 'job' to the computer's [[computer operator|operator]], which was called 'submitting' the job. The operator would pass the job to the computer, and, when it was done, return the output, etc produced by running the job back to the user.

Early computers (which were very expensive) tended to charge for all resources used by the job - [[Central Processing Unit|CPU]] time, [[main memory]] usage, [[printer]] output, etc. An accounting system measured all the resources used in running a job, added up all the costs, and charged the result to the account given when the job was submitted.

A job was often run as a [[process]], but not all batch OS's supported the process abstraction. Some early interactive OS's retained the term, but used it to refer to a process, or a user's top-level process, etc.

E.g. on the [[Incompatible Timesharing System]], processes running below a user's top-level [[command processor]] (usually application) are referred to as 'jobs'.

{{semi-stub}}

@@ Line 1: / Line 1: @@
-The term '''job''' is not precisely defined, but it generally means a unit of work for a computer; e.g. an [[application]] together with its input data, often for a [[batch operating system]].
+The term '''job''' is not precisely defined, but it generally means a unit of work for a computer; e.g. an [[application]] together with its [[input]] data, often for a [[batch operating system]].
-A [[user]] would hand in his 'job' to the computer's [[computer operator|operator]], which was called 'submitting' the job. The job could e.g. consist of a stack of [[punched card]]s that contained a program (typically in [[object code]] form), along with the data to be processed by that program. The operator would pass the job to the computer, and, when it was done, return the output, etc produced by running the job back to the user.
+A [[user]] would hand in his 'job' to the computer's [[computer operator|operator]], which was called 'submitting' the job. The job could e.g. consist of a stack of [[punched card]]s that contained a program (typically in [[object code]] form), along with the data to be processed by that program. The operator would pass the job to the computer, and, when it was done, return the [[output]], etc produced by running the job back to the user.
-Early computers (which were very expensive) tended to charge for all resources used by the job - [[Central Processing Unit|CPU]] time, [[main memory]] usage, [[printer]] output, etc. An accounting system measured all the resources used in running a job, added up all the costs, and charged the result to the account given when the job was submitted.
+Early computers (which were ''very'' expensive) tended to charge for all resources used by the job - [[Central Processing Unit|CPU]] time, [[main memory]] usage, [[printer]] output, etc. An accounting system measured all the resources used in running a job, added up all the costs, and charged the result to the account given when the job was submitted.
-A job was often run as a [[process]], but not all batch OS's supported the process abstraction. Some early interactive [[operating system]]s retained the term, but used it to refer to a process, or a user's top-level process, etc.
+A job was often run as a [[process]], but not all batch OS's supported the process abstraction. Some early interactive [[operating system]]s retained the term 'job', but used it to refer to a process, or a user's top-level process, etc. E.g. on the [[Incompatible Timesharing System]], processes running below a user's top-level [[command processor]] (usually applications) are referred to as 'jobs'.
 {{semi-stub}}
 [[Category: OS Basics]]

@@ Line 1: / Line 1: @@
 The term '''job''' is not precisely defined, but it generally means a unit of work for a computer; e.g. an [[application]] together with its input data, often for a [[batch operating system]].
-A [[user]] would hand in his 'job' to the computer's [[computer operator|operator]], which was called 'submitting' the job. The job could e.g. consists of a stack of [[Punched card|punched cards]] that contained of a program and the data to be processed by that program. The operator would pass the job to the computer, and, when it was done, return the output, etc produced by running the job back to the user.
+A [[user]] would hand in his 'job' to the computer's [[computer operator|operator]], which was called 'submitting' the job. The job could e.g. consist of a stack of [[punched card]]s that contained a program (typically in [[object code]] form), along with the data to be processed by that program. The operator would pass the job to the computer, and, when it was done, return the output, etc produced by running the job back to the user.
 Early computers (which were very expensive) tended to charge for all resources used by the job - [[Central Processing Unit|CPU]] time, [[main memory]] usage, [[printer]] output, etc. An accounting system measured all the resources used in running a job, added up all the costs, and charged the result to the account given when the job was submitted.

@@ Line 1: / Line 1: @@
 The term '''job''' is not precisely defined, but it generally means a unit of work for a computer; e.g. an [[application]] together with its input data, often for a [[batch operating system]].
-A [[user]] would hand in his 'job' to the computer's [[computer operator|operator]], which was called 'submitting' the job. The operator would pass the job to the computer, and, when it was done, return the output, etc produced by running the job back to the user.
+A [[user]] would hand in his 'job' to the computer's [[computer operator|operator]], which was called 'submitting' the job. The job could e.g. consists of a stack of [[Punched card|punched cards]] that contained of a program and the data to be processed by that program. The operator would pass the job to the computer, and, when it was done, return the output, etc produced by running the job back to the user.
 Early computers (which were very expensive) tended to charge for all resources used by the job - [[Central Processing Unit|CPU]] time, [[main memory]] usage, [[printer]] output, etc. An accounting system measured all the resources used in running a job, added up all the costs, and charged the result to the account given when the job was submitted.

@@ Line 1: / Line 1: @@
-The term '''job''' is not precisely defined, but it generally means a unit of work for a computer; e.g. an [[application]] together with its input data, often for a [[batch]] [[operating system]].
+The term '''job''' is not precisely defined, but it generally means a unit of work for a computer; e.g. an [[application]] together with its input data, often for a [[batch operating system]].
 A [[user]] would hand in his 'job' to the computer's [[computer operator|operator]], which was called 'submitting' the job. The operator would pass the job to the computer, and, when it was done, return the output, etc produced by running the job back to the user.
@@ Line 5: / Line 5: @@
 Early computers (which were very expensive) tended to charge for all resources used by the job - [[Central Processing Unit|CPU]] time, [[main memory]] usage, [[printer]] output, etc. An accounting system measured all the resources used in running a job, added up all the costs, and charged the result to the account given when the job was submitted.
-A job was often run as a [[process]], but not all batch OS's supported the process abstraction. Some early interactive OS's retained the term, but used it to refer to a process, or a user's top-level process, etc.
+A job was often run as a [[process]], but not all batch OS's supported the process abstraction. Some early interactive [[operating system]]s retained the term, but used it to refer to a process, or a user's top-level process, etc.
 E.g. on the [[Incompatible Timesharing System]], processes running below a user's top-level [[command processor]] (usually applications) are referred to as 'jobs'.

← Older revision		Revision as of 21:13, 16 December 2018
Line 10:		Line 10:

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