Getting Started with IBM Data Studio for DB2

Chapter 6 – Managing jobs 195
6.3 Jobs and job components
A job is a container that holds the components that are required to run a script on one or
more databases. When you create a job, you can either schedule it to run on one or more
databases, or you can leave the schedule component of the job empty. A job can also be
run manually from the Job List tab of the job manager. You can also configure multiple jobs
to run sequentially by adding a chain of jobs to the job that you are creating.
The job does not contain any information about which databases that the job will run on.
The database information is included in one or more schedules that you can create for
each job.
6.3.1 The components of a job
A job consists of several components, all of which can be defined when you create a job.
The only job components that are required to create a valid job are the job name, the job
ID, and the script. These components are described in Table 6.1.
Job
component
Job ID and
name
(required)
Script
(required)
Schedule
Description
The job ID is the unique identifier of the job and is generated automatically by
job manager. The job name that you specify can be used as a descriptive way
to easily identify the job in the job list or when scheduling jobs.
The script is the executable part of a job and defines the actions that are done
on the database when the job is run. You can enter one script per job.
Important: The job manager does not provide a script editor and does not
verify that the scripts that you enter are valid. Run the script on a database or
use other methods to verify that the script is correct and that it produces the
expected results before you schedule the job in the job manager.
A schedule defines when a job will be run, whether the job is repeating, and
whether the schedule is limited in number of runs or in time. The schedule
also defines one or more databases on which to run the job.
A job can have any number of schedules attached to it, but each schedule
only applies to one job. A schedule must be active to run the job. Each
schedule has a unique ID that is based on the job ID with an integer
appended at the end of the ID.
Example:
The first schedule that is attached to job ID 1234 will have schedule ID 1234-
1. The second schedule that is attached to the same job will have schedule ID
1234-2, and so on.
A schedule is not required; you can also run jobs manually from the job
manager. When you schedule a job on a single database, you can define the