Once jobs have been created they can be edited.
A job can only be edited when it is not running and only if the job is scheduled. Completed jobs remain in the list but only logs remain.
To edit a job
Select the job from the middle pane and then right-click to select Edit Job from the context menu.
The Job Definition is displayed.
Edit the fields as required and click OK. The main fields are described in the following table:
| Field | Description |
|---|---|
| Job Name | The Scheduler defaults to the next job number in the sequence. You can alter this to any alphanumeric. Only alphanumerics, spaces, and the underscore are supported in the name. On some UNIX systems, long job names can cause jobs to be canceled (see Knowledge Base article 67), so where possible keep the name short. |
| Description | A description of the job |
| Frequency | When the job runs. The options available in the drop-down list box are:
|
| Start Date and Start Time | The date and time for the job to start. |
| Max Threads | The maximum number of threads allocated to run the job, e.g, if some tasks can run in parallel then if more than one thread is allocated they will run in parallel. Users must be aware that adding additional threads to a job increases the communication overhead with the DB server containing the Data Warehouse repository. Each job thread holds a dedicated connection to the server for its lifetime. |
| Scheduler | Certain types of jobs will only run in a specific environment. For example, ODBC-based loads can only be handled by the Windows' scheduler. It is possible to have multiple schedulers running. Select the desired scheduler from this drop-down. The valid options are: UNIX Preferred, UNIX Only, Windows Preferred, Windows Only, or the name of a specific scheduler can be entered (e.g. WIN0002) |
| Dependent On | A job can be dependent on the successful completion of one or more other jobs. Click the Add Parent Job button to select a job that this job will be dependent on. The maximum time to look back for the parent job completion field prevents older iterations of the parent job as being identified as a completion. The maximum time to wait specifies how long to await a successful completion of the parent job. The action if that wait expires can also be set. Refer to the Job Dependency example in Scheduling a Job for details. |
| Logs Retained | Specify the number of logs to retain for the job. By default, all logs are retained. This field can be used to reduce the build-up of scheduler logs by specifying the number of logs to retain. |
| Success command and Failure command | These are either UNIX or Windows shell commands depending on which scheduler is used. They are executed if the condition is met. Typically, these commands would mail or page on success or failure.
|
The following fields are available if a frequency of Custom is chosen:
| Field | Description |
|---|---|
| Interval between jobs (Minutes) | Specify the number of minutes between iterations of the job. For example, to run a job every 30 minutes set this value to 30. If a job is to run only once but on selected days set this value to 1440 (daily) |
| Start at or after HHMM | The time that the job may run from. To run anytime set to 0000. |
| Do not start after HHMM | If multiple iterations are being done then this is the time after which a new iteration will not be started. For example, if a job is running every 10 minutes it will continue until this time is reached. To run till the end of the day set to 2400. |
| Active on the days | Select each day of the week that the custom job is to be active. |