Running Jobs
Each time that you run or schedule a job, you can:
Change the job parameters and parameter values that are associated with the job.
Override default limits for row processing and warning messages that are set for the job run.
Set tracing options.
You set job options in the Job Run Options dialog box. They appear automatically when you start to run or schedule a job.
Setting Parameters
You can use the default parameter values, or enter another value. To reinstate the default values, click the Set to Defaultor All to Default button. Some job parameters, like dates, may be variables that you must enter for each job run.
If no parameters are set for a job, the system does not display the Parameters tab.
Setting Limits
Select the Limits tab to override any default limits for row processing and warning messages that are set for the job run. Click the Validate button to test the new settings or click the Run button to run the job.
Setting Tracing
Tracing helps analysts troubleshoot jobs. You can generate tracing information and performance statistics for server jobs.
The options on this page determine the amount of diagnostic information that is generated the next time a job is run. Diagnostic information is generated only for the active stages in a chosen job.
When the job runs, a file is created for each active stage in the job. The files are named using the format jobname.stagename.trace, and are stored in the &PH& subdirectory of your DataStage server installation directory.
Running, Stopping, Resetting, and Deleting Jobs
To run a job, select Job, Run Now, or click the Run button on the toolbar.
You can stop or reset a job. If a job is stopped or aborted, it might be difficult to trace where it ended. By resetting a job, you set it back to a state that can be run and, optionally, return your target files to their original state. If a job has aborted, it must be reset before you can run it again.
You can remove old or unwanted jobs from your project from either the Director or Designer.