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.

• Starting a job
  Interactive jobs are started when the user signs on to a workstation. You start prestart jobs and batch jobs by using iSeries Navigator or the character based interface, depending upon the circumstances.

• Ending a job
  You can use the iSeries Navigator or the character-based interface to end a job. The job can be active or on a job queue. You can end a job immediately or by specifying a time interval so that end of job processing can occur.

• Finding jobs
  It is important to understand how to find jobs on your system. Whatever the reason, at some point in time you might need certain information from a particular job.

• Viewing jobs on the job queue
  Job queues filter some of the work that is processed in work management (for example, some batch jobs). Being able to view jobs in the job queue allows you to see what jobs are waiting to be sent to a subsystem.

• Viewing jobs in the subsystem
  Subsystems coordinate work flow and the resources that a job uses to run. iSeries Navigator allows you to see what jobs are currently active (but not necessarily running) in the subsystem.

• Viewing job attributes
  Job attributes contain information about how jobs are processed. They are originally specified when the job is created. Some of the attributes come from the job description. After the job is created, the job attributes can be viewed and managed through work management in iSeries Navigator. The job properties pages in iSeries Navigator make a system operator's job easier by providing efficient and easy-to-use functions for managing jobs.

• Viewing call stacks
  You can view information about a job or thread's call stack by using either iSeries Navigator or the character-based interface.

• Placing a job on the job queue
  Jobs are placed on the job queue by either moving an existing job from one queue to another, or by submitting a new job. Use iSeries Navigator to move jobs between queues. Use the character-based interface to submit a new job.

• Moving a job to a different job queue
  There are many reasons why you might want to move a job to another queue. For example, sometimes jobs become backlogged in the queue because of a long running job. Perhaps the job's scheduled run time conflicts with a new job that has a higher priority. One way to manage this situation is to move the waiting jobs to another queue that is not as busy.

• Moving a job up in priority within a job queue
  All jobs in a job queue wait in line for processing. As each job in the queue completes, the next job in line begins. The processing order of the jobs in the queue depends upon the job's priority, and the maximum number of jobs that can run at the same time on the subsystem.

• Tips for setting job priorities
  The priorities for jobs that run in batch environments should normally be lower than priorities for jobs in interactive environments. Also, the time slice should be small enough so that a looping program does not dominate processor time and an activity level.

• Submitting a job once
  When you need to run a job once, whether immediately or at a scheduled date and time, use the Submit Job (SBMJOB) command. This method places the job on the job queue immediately.

• Viewing job affinity information
  Each job on the system contains memory and processor affinity information.

 

Parent topic:

Managing jobs