Jobs

 

All work done on a system is performed through jobs. Each job has a unique name within the system. All jobs, with the exception of system jobs, run within subsystems. A job can enter the subsystem from any of the work entries, such as a job queue entry, workstation entry, communications entry, autostart job entry, or prestart job entry.

Each active job contains at least one thread (the initial thread) and may contain additional secondary threads. Threads are independent units of work. Job attributes are shared among the threads of the job, however threads also have some of their own attributes, such as a call stack. The job's attributes contain information about how the work is processed. The job serves as the owner for attributes that are shared among threads within the same job. Work management provides a way for you to control the work done on your system through a job's attributes.

• Proper authority
  To make most changes to a job's attributes, you need to have job control special authority (*JOBCTL) or your user profile matches the job user identity of the job being changed.

• Job characteristics
  Work management provides a way for you to control the work done on your system through a job's attributes. However, before you can control the various aspects of a job, you need to understand the different characteristics of a job.

• Job types
  Your system processes several different types of jobs. This information describes those jobs and how they are used.

 

Parent topic:

Concepts