The job manager provides job creation, job scheduling,
and job management for your DB2® for Linux, UNIX and Windows and DB2 for z/OS® databases.
With the job manager you can:
- Create and schedule jobs directly from the Data Studio client workbench.
- Use the workbench script editor to create your script and then
schedule the script to run as a job in the job manager.
- Access the Data Studio web console either
embedded in the workbench or in a stand-alone web browser window.
- Access the job history for a database directly from the Administration
Explorer in the workbench.
- Create jobs based on database scripts:
- SQL-only scripts
- The SQL-only scripts are run by the job manager by running the
SQL commands that are outlined in the script part of the job directly
against the database.
- DB2 CLP scripts
- The DB2 CLP script jobs are run on the database server by the
job manager, which logs in to the database server by using SSH. For
multiple databases, the job manager logs in as the user ID that is
defined in the database connection. For a single database, based on
the user's selection, the job manager logs in by using SSH credentials
that the user supplies or the user ID that is defined in the database
connection. When logged in, the job manager runs command line processor
commands directly on the DB2 console of the server.
Important: To be able to run DB2 CLP 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.
- Executable/shell Scripts
- The Executable/Shell script jobs are run on the database server
by the job manager, which logs in to the database server by using
SSH. For multiple databases, the job manager logs in as the user ID
that is defined in the database connection. For a single database,
based on the user's selection, the job manager logs in by using
SSH credentials that the user supplies or the user ID that is defined
in the database connection. When logged in, the job manager runs shell
commands directly on the server.
Important: To be able
to run 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.
- Schedule jobs to run at a specific time, or to repeat at certain
intervals for one or more databases.
- Run jobs for multiple databases as the default user stored in
the database connection, or specify a user ID to run the job as when
running a job on one database.
- Add jobs together in chains, where the main job is followed by
a secondary job dependent on the outcome of the main job, and where
a finishing job, such as RUNSTATS and BACKUP,
is run last.
- Configure email notifications to be sent to one or more users
depending on the success or failure of the job.
- View the history of all jobs that run on your databases.
- The job history view gives you a high-level overview of the job
results and the option to drill down into each job.
- You can configure the job manager to retain job history for all
jobs that were run, or for a subset depending on the success or failure
of the job.
- Manage user access to job manager tasks across your databases.
- Enable or disable job management privileges requirements for the
users of the web console.
- For each database, grant or revoke job management privileges for
each user of the web console.