Versions Compared

Old Version 1

changes.mady.by.user Wara Hermosa

Saved on

compared with

New Version Current

changes.mady.by.user eric revollo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

FieldDescription
Job Name

The Scheduler defaults to the next job number in the sequence. You can alter this to any alphanumeric. 

Tip

Only alphanumerics, spaces, and the underscore are supported in the name.


Warning

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.

DescriptionA description of the job
FrequencyWhen the job runs. The options available in the drop-down list box are:
  • Once Only - job is deleted on completion
  • Once and Hold - runs and puts another copy of the job on hold
  • Hold - puts the job on hold for manual release
  • Daily - runs the job daily
  • Custom - enables custom definition
  • Weekly - runs the job weekly
  • Monthly - runs the job monthly
  • Annually - runs the job annually
Start Date and Start TimeThe 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.

Warning

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.


SchedulerCertain 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 OnA 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 RetainedSpecify 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.

Note
  • The RED scheduler does not check return codes from called commands, scripts, and programs.
  • It is recommended that all output from commands, scripts, and programs is redirected to a log file. For example, add this to the end of any SUCCESS/FAILURE commands: >> c:\scheduler\success_failure_prod.log 2>&1


...