|
Create a new scheduled job
| 1.
| From the Configuration menu, select Scheduler.
|
| 3.
| Complete the job parameters based on the following definitions:
|
Job Command Select the URL-based command that to run.
|
|
Job Parameters The queryString of the command that is to be run. All special characters, such as &, =, /, and ?, must be encoded using standard HTML coding. If you use the form provided, encoding will be done for you.
|
|
Start date The date this job should start running.
|
|
Start time The time this job should start running. The time must be entered in the 24-hour-clock format.
|
|
Associated user The user on whose behalf this job is run. By default, the user ID of the current user is entered in this field. It may be replaced by typing in another user ID. This parameter is stored in the LOGONID column of the USERREG table.
|
|
Allowed host The name of the host that is allowed to run this job. If this parameter is omitted, the job can be run by any host. This parameter is needed only if the scheduler is running on multiple hosts. The host name should be in the name.domain format.
|
|
Schedule interval The number of seconds between successive runs of this job. If this parameter is omitted, the job is run only once.
|
|
Job attempts The number of times the scheduler retries the job if it fails. Use this parameter with the Seconds to retry parameter. Both parameters must be present to retry the job.
|
|
Seconds to retry The number of seconds before a failed job is retried. Use this parameter together with the Job Attempts parameter. Both parameters must be present to retry a job.
|
Scheduler policy Specifies the policy to be used by the scheduler when the job has failed to run. Two possible values are defined:
0 - The job is run only once and the next run is scheduled for the future; this is the default.
1 - The job is run as many times as necessary to recover all missed runs.
|
|
Job priority The number associated with the priority of the job. This value is inserted into the SCCPRIORITY column of the SCHCONFIG table. A greater number indicates a higher-priority job.
|
|
Application type The application schedule pool that the job will be part of. The purpose of this parameter is to constrain resource-intensive jobs to a limited number of threads. The default application type is null.
|
|
