Edit Scheduled Job

This dialog allows you to edit the configuration for jobs that are currently scheduled to run for your site.

Job command
The URL-based name of the command you are editing.
Job parameters
The queryString of the command to be run. All special characters, such as &, =, /, and ?, must be encoded.
Start date
The date the first running of this job should occur.
Start time
The time the first running of this job should occur.
Associated user
The user on whose behalf this job is run. By default, the username 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 database table.
Allowed Host
The name of the host allowed to run this job. If this parameter is omitted, the job can be run by any host. The parameter is only needed if the scheduler is running on multiple hosts and if a job needs to be restricted to one of them. The host name should be in the following form: name.domain
Schedule interval
The number of seconds between successive runs of this job. If this parameter is omitted, the job is only run once.
Job attempts
The number of times that the scheduler retries the job if it fails. Use this parameter together with the delay parameter. Both parameters must be present to re-try the job.
Seconds to retry
The number of seconds before a failed job is retried. Use this parameter together with the attempts parameter. Both parameters must be present to re-try the job.
Scheduler policy
Specifies the policy to be used by the scheduler when the job has failed to run more than once. Two possible values are defined:
  • The job is run only once. The next run of a job is scheduled for the future. This is the default.
  • The job is run as many times as necessary to recover all missed runs.
Job priority
The number associated with the priority of this job. This value is inserted into the SCCPRIORITY column of the SCHCONFIG table. A greater number indicates a higher priority job.
Application type
The parameter used to identify a grouping for the job being added. The purpose of this parameter is to constrain resource-intensive jobs to a limited number of threads. The application types, and the rules governing their access to resources, are defined by the user in the XML Server Configuration file. The default application type is null or default.