A job's life

 

To understand the basics of System i™ work management, follow a simple batch job as it moves through the system.

The life of a simple batch job begins when you submit it to the system. The job is then sent to a job queue where it waits to enter a subsystem where it can run. After the job moves to the subsystem it is allocated memory in which to run. The printer output file (also called spooled files) is then sent to the output queue to await further instruction on what to do (for example, printing). While not every job follows this exact path, you can better understand how other work is completed on the system by learning more about this typical job life cycle.

Submit the job > Job enters the job queue > Job enters the subsystem > The memory pool allocates memory to the subsystem > The job finishes and moves to the output queue

 

Parent topic:

Introduction to work management