Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ OSM Administration

Scheduling a job

  • Last UpdatedSep 24, 2024
  • 4 minute read

Most jobs are mandatory. Mandatory jobs are provided with OSM Administration to be executed by the Oracle database. For the most part, customers cannot create jobs; however it is possible to have a custom job created for you by the AVEVA Solutions team.

There are not many details of the job that are modifiable, but you have control over when to execute the jobs and what error message options you would like to see.

Reminder A job is not editable in Active state.

To open the Job Schedule window

  1. From the Tools menu, open the System Management window, then double-click Job Schedule.

    The Job Schedule window opens.

Scheduling a job

This section focuses on the time scheduling options of the job.

Specify a Start and End date for running the job

  • Select value for Start date/time. The Start date must be scheduled at least 24 hours after the current database time.

Property

Description

Start date/time

Select the beginning date and time of the scheduled job in local database time. The scheduled job will begin executing on this scheduled date and time and continue to execute from this time forwards. There is no end date.

If the Start date/time is not at least 24 hours after the current database time, you may see this message. Change the Start date/time to satisfy the condition.

Specify how often the job should run and at what interval

Interval type

  • Specify the type of time interval between executing the job. Depending on the selection you make, the values in the Interval drop-down menu will change.

Interval

  • Specify the specific interval between executions. Depending on the selection you made in the Interval type menu, the options can be numeric or days of the week.

    If you select Day in month, you can specify a numeric day of the month up to day 28, since all months have at least 28 days. If you specify 31 and a month does not have 31 days, the system will interpret this as last day of the month according to the number of days in that month.

Priority

There are two options for determining when the next job should run after the last job has executed.

Scheduled time has priority

The Scheduled time has priority option is available when the interval unit is Days. You might want to choose this option for less frequent jobs, such as when the job runs only once a week or once a month.

This option executes the job at same scheduled time every unit of time. It stays true to the scheduled time.

Examples

For example, if the interval type is Day in month and the job is scheduled to run at 2:00 am on the first of the month, the job executes 2:00 am on the first of the month.

Interval Type

Example scenario

Behavior

Number of days

Scheduled to run every 15 days at 2:00 am.

Runs every 15 days at 2:00 am.

Day in month

Scheduled to run on first day of the month at 2:00 am.

Runs on first day of the month at 2:00 am.

Day in week

Scheduled to run every Sunday at 2:00 am.

Runs every Sunday at 2:00 am.

Forward interval has priority

If interval unit is Minutes or Hours, only the Forward interval has priority option is available. This option is for jobs that run more frequently.

This option executes the job when the interval time after the last job finished has elapsed.

Example

For example, if the interval type is Hour and the job is scheduled to start running at 6:00 am on the start day. The interval time is one hour.

A job that starts at 6:00am takes 15 minutes. It finishes at 6:15 am. The next job is scheduled for one hour after the finish time of the last job. The next job starts at 7:15 am.

Job starts

Time for job to execute

Job finishes

Next schedule job will run at

6:00 am

15 minutes

6:15 am

7:15 am

7:15 am

17 minutes

7:32 am

8:32 am

8:32 am

15 minutes

8:47 am

9:47 am

In This Topic
Related Links
TitleResults for “How to create a CRG?”Also Available in