Managing Jobs

You are looking at an older version of the documentation. The latest version is found here.

Changing Job Parameters

Depending on the job type (SQL job or some other job), the corresponding stored procedure can be used to change the job parameters:

SQL

SYSADMIN.changeSQLJob(IN jobid biginteger NOT NULL, IN script string NOT NULL, IN description string, IN parallelRunsAllowed integer, IN retryCounter integer, IN retryDelay integer, IN runTimeout integer)

SYSADMIN.changeJobParameters(IN jobid biginteger NOT NULL, IN parallelRunsAllowed integer, IN retryCounter integer, IN retryDelay integer, IN runTimeout integer)

The job ID should be specified as the required parameter.

The following parameters can be updated:

Parameter	Description
`script`	SQL script (only for the SQL job type)
`description`	Job description (only for the SQL job type)
`parallelRunsAllowed`	Number of parallel runs the job can have; If the number is reached, further starts of the particular job will be ignored. Default: `1`
`retryCounter`	Number of retry attempts before the job is set to `FAILED` state
`retryDelay`	Delay in seconds between the retry attempts
`runTimeout`	Individual job timeout in minutes. If no `runTimeout` is set, configuration set via default value option `JOB_RUN_TIMEOUT` will be considered for the job; if `runTimeout` is reached before the job is finished, the job terminates with the `INTERRUPTED` state

jobName Parameter

The jobName parameter serves as a job's unique identifier meant to support synchronization processes between the Data Virtuality Server instances. It can be specified in all procedures creating any of the non-system jobs. It cannot be specified in job-changing procedures.

Here are some other points to keep in mind:

When jobName is absent in procedure call, it is created by the system automatically;
The system will also create names for jobs on the Data Virtuality Server start when it encounters any job without a jobName set;
These names are not meant to be freely editable or selectable and we do not recommend to change them without a very good reason.

Stopping a Job

The stopJob procedure stops all currently running schedules for a particular job:

SQL

 SYSADMIN.stopJob(IN id biginteger NOT NULL)

Enabling/Disabling a Job

The enableSchedulerJob procedure enables or disables a job:

SQL

 SYSADMIN.enableSchedulerJob(IN id biginteger NOT NULL, IN enabled boolean NOT NULL)