How work gets done

Use this information to learn about what work is, what needs to be set up before work can begin, how work travels through the system, and what happens to work after it is done running.

• What work is
  On the iSeries™ server, work is always being done, whether you initiate it or the system initiates it. Any action done on the iSeries™ server has some type of work being performed to complete it.
• What happens before work enters the system
  All jobs, with the exception of system jobs, run within subsystems. For work to start in an active subsystem, memory pools and at least one source of work entry point need to be established. Job queues are an example of a source of work.
• How work enters the system
  Work entries identify the sources where jobs enter a subsystem to become available to run. Each type of job on the iSeries™ has different types of work entries that it uses.
• How work gets processed
  When the iSeries™ server is started, a subsystem monitor job begins running. The subsystem monitor job controls the jobs within subsystems. It also starts and ends work, as well as manages the resources for work in the subsystem.
• How work leaves the system
  The output queue works similarly to a job queue in that it schedules output to be printed. Both the printer output and the output queue carry attributes that are used to print the information.