Page tree
Skip to end of metadata
Go to start of metadata

                       

Here you can see all the future jobs, both those that recur periodically as well as those that are only started once.

 

More information on a planned job can be obtained by double-clicking on the row.

 

In this case, information on the last execution of the job and on the cyclical or future execution is shown. The job definition can be edited here and temporarily suspended.

Selecting a new job planning:

 

 

Then the following capture assistant (wizard) opens.

 

Please select the job that you plan to execute in the future on the first page. (Only those jobs that should be started by an operator from a functional viewpoint will be available). You can also define a name, a group name and a description for this schedule; these fields are only used for display and search purposes.

Following this, you have to enter the job-specific model parameter. Parameters can have a default value expression. When the toggle button “Evaluate Default Value at Execution” is switched to on, the expression is evaluated at execution time instead of the time the user creates the schedule.

 

On the next page, you can decide on what form the capture of the cycle should take: Cron syntax or simple syntax.

Below are the two masks:

Simple

 

or Cron

Cron expression

A cron expression is a chain with 6 or 7 fields separated by space characters. Fields may contain each of the permitted values together with various combinations of the special characters permitted for the field. The fields are as follows:

 Field name

Mandatory field

Permitted values

Permitted special characters

Seconds

Yes

0-59:

,   - * /

Minutes

Yes

0-59

,   - * /

Hours

Yes

0-23

,   - * /

Day of the month

Yes

1-31

,   - * ? / L W

Month

Yes

1-12   or JAN-DEC

,   - * /

Weekday

Yes

1-7   or SUN-SAT

,   - * ? / L W

Year

No

1970-2099:

,   - * /

Cron expressions can be as easy as the following: * * * * ? * or more complex like these: 0/5 14,18,3-39,52 * ? JAN,MAR,SEP MON-FRI 2002-2010

Special characters

  • * (“all values”) - to select all the values in a field. For example, “” in the field “Minute” means *“every minute”.
  • ? (“No specific value”) -  this can be used when a value has to be defined in one of two fields and this value is only permitted in one of the fields. For example, when the trigger is to be activated on a certain day of the month (e.g. 10th) but the weekday does not matter, “10” is entered in the field “Day of the Month” and “?” in the field “Weekday”.  For illustration purposes, please see the examples below:
  • -- to define ranges. For example, “10-12” in the field “Hours” means the hours 10, 11 and 12”.
  • , - is used to specify additional values. For example, “MON,WED,FRI” in the field “Weekday” means the days Monday, Wednesday and Friday.
  • / - to define increases. For example, “015” in the field “Seconds” means the seconds 0, 30 and 45”. For example, “5/15” in the field “Seconds” means the seconds 5, 20, 35 and 50”. “/” can also be placed after “Character -  in this case”, meaning “0” before “/”. “1/3” in the field “Day of the Month” means “Activate trigger every 3 days from the first day of the month”.
  • L(last) - has different meanings in each of the two fields where it is permitted. For example, the value “L” in the field “Day of the Month” means “the last day of the month” - 31st for January, 28th for February in non-leap years. When “L” is in the field “Weekday”, this means “7” or “SAT”. However, if a different value is used in the field “Weekday”, this means “the last XXX day of the month” - e.g. “6L” means “the last Friday in the month”. It is also possible to define a gap before the last day of the month, e.g. “L-3” means the third day before the last day of the calendar month. If the value “L” is used, no lists or ranges of values should be used because then the results will be confusing or not be as expected.
  • “W” (“Weekday”) - defines the weekday (Monday-Friday) that is nearest to the set date. For example, if “15W” is in the field “Day of the Month, this would mean “the weekday that is nearest to the 15th of the month”. If the 15th is a Saturday, the trigger is activated on Friday 14th. If the 15th is a Sunday, the trigger is activated on Monday 16th. If the 15th is a Tuesday, the trigger is activated on Tuesday 15th. If “1W” is entered as the  value for the day of the month, and the 1st is a Saturday, the trigger is activated on Monday 3rd because it cannot “jump” over the boundary between months. The value “W” can only be defined, if the day of the month is a single day and not a range or list of days.
  • # - is used to define the “n-th day XXX of the month”. For example, the value “6#3” in the field “Weekday” means “the third Friday in the month” (Day 6 = Friday and “6#3” = the third day in the month). Other examples: “2#1” = the first Monday in the month and “4#5” = the fifth Wednesday in the month. Please note that if “#5” is defined as a value and the month in question does not have 5 such weekdays, no trigger is activated for this month.

At the end, the most important data for the newly scheduled job is shown again and should be confirmed by “SAVE”.

 

For an ad hoc execution of a job, please click on:

 

Then the following capture assistant (wizard) opens.

 

 
On the first page, you can select the job that you want to start:

 

 

Following this, you have to enter the job-specific model parameter.

 

Finally, please enter the level of the (trace) messages that are to be generated by the job. This parameter can remain set at the default value “Notice” for normal operation.

The job is started by clicking on OK.

 

Following this, the execution of the job can be followed on the tile “Monitor”.

 

 

 

  • No labels