16.10.2015 Views

Getting Started with IBM Data Studio for DB2

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

202 <strong>Getting</strong> <strong>Started</strong> <strong>with</strong> <strong>IBM</strong> <strong>Data</strong> <strong>Studio</strong> <strong>for</strong> <strong>DB2</strong><br />

Figure 6.8 – Select a database<br />

When you schedule a job on a single database, you can define the user ID that will run<br />

the job. If you schedule a job to run on more than one database, the job is run on each<br />

database by the user ID that is stored in the database connection <strong>for</strong> that database.<br />

Important:<br />

If the user ID that is used to run the job does not have the required permissions<br />

to per<strong>for</strong>m the commands that are defined by the script <strong>for</strong> the database, the job<br />

fails <strong>with</strong> a permissions error. If you are scheduling the job <strong>for</strong> a single database,<br />

update the schedule <strong>with</strong> a user that has the required permissions. If you are<br />

scheduling the job to run on more than one database, use the <strong>Data</strong>bases page<br />

to update the database connection <strong>with</strong> a user ID that has the required<br />

permissions.<br />

<br />

(Optional) Click Chain to add a chain of additional jobs that will run conditionally when<br />

the main job has completed. In a chain, the main job is followed by a secondary job that<br />

is dependent on the outcome of the main job, and then followed by a finishing job that<br />

per<strong>for</strong>ms cleanup operations, such as RUNSTATS and BACKUP. You can add a chain of<br />

subsequent jobs that run depending on the outcome of the primary job.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!