Getting Started with IBM Data Studio for DB2

196 Getting Started with IBM Data Studio for DB2
Notification
Chains
user ID that will run the job. If you schedule a job to run on more than one
database, the job is run on each database by the user ID that is stored in the
database connection for that database.
Notifications are one of two methods that you can use to determine whether
your jobs ran successfully. Use notifications to alert you by email on the
successful or failed run of a job on your databases.
The other method of determining the outcome of your jobs is to look in the job
history tab of the job manager, where you can see the status of all jobs on all
databases that are configured for your system.
You can add a chain of subsequent jobs that run depending on the outcome
of the primary job. A job chain can consist of three consecutive jobs: the
primary job, a job that runs if the primary job is successful or a job that runs if
it is unsuccessful, and finally an ending job that runs at the end of the chain
regardless of the outcome of the preceding jobs.
Important:
When a job is run as part of a chain, any schedules and chains that are
associated with that job are ignored.
Table 6.1 – Components of a job
6.3.2 Job types
The job manager supports three default job types. The job type indicates the way that the
job manager connects to the databases to run the scripts.
Job type
SQL-only script
DB2 command line
processor script
Executable/Shell
script
Connection method
The job manager connects to the database and runs the SQL
commands that are included in the job script directly on the
database.
The job manager logs in to the database server by using SSH as
the user ID defined in the database connection, and then it runs
command line processor commands directly on the DB2 console
of the server.
The job manager logs in to the database server by using SSH as
the user ID that is defined in the database connection, and then
runs shell commands directly on the server.
Note:
To run DB2 command line processor script jobs or executable/shell script jobs on a
database, the user ID that is used to run the job must have permission to log in to the
database server by using SSH.