Difference between revisions of "Job"
m (+cat) |
m (Avoid dab) |
||
| 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 | + | 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 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. | 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 | + | 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'. | E.g. on the [[Incompatible Timesharing System]], processes running below a user's top-level [[command processor]] (usually applications) are referred to as 'jobs'. | ||
Revision as of 15:02, 9 September 2022
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 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 - 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 systems 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'.
