Managing jobs

 

As any work management administrator knows, managing jobs is more than placing jobs on hold and moving jobs from job queue to job queue. This topic discusses the most common job management tasks as well as some of the more involved tasks that can help improve your system's performance.

• Common job tasks
  These are the most common tasks that you can perform with jobs. The instructions apply to both iSeries™ Navigator (where available) and the character-based interface.

• Managing job descriptions
  Since a job description collects a specific set of job-related attributes, the same job description can be used by multiple jobs. Thus, if you use a job description, you do not need to specify the same parameters repeatedly for each job. You can create job descriptions to describe batch jobs or interactive jobs. You can also create unique descriptions for each user of the system. Job descriptions are created and managed by using the character-based interface.

• Managing batch jobs
  Jobs that do not require user interaction to run can be processed as batch jobs. A batch job typically is a low priority job and can require a special system environment in which to run.

• Managing interactive jobs
  An interactive job starts when you sign on to the system or, transfer to a secondary or group job. The interactive job ends when you sign off. Working from a display station, you interact with the system by issuing commands, using function keys, and running programs and applications. The following information discusses the various methods for managing and controlling interactive jobs.

• Managing prestart jobs
  You can use prestart jobs to reduce the amount of time required to handle a program start request. These are the most common tasks associated with prestart jobs that you can perform.

• Managing job class objects
  A class object contains the run attributes that control the run-time environment of a job. IBM-supplied class objects, or classes, meet the needs of both typical interactive and batch applications. The class used by a job is specified in the subsystem description routing entry used to start the job. If a job consists of multiple routing steps, the class used by each subsequent routing step is specified in the routing entry used to start the routing step.

• Managing threads
  You can perform many tasks when managing threads.

 

Parent topic:

Managing work