A wildcard character (*) generates a repetition and is an abbreviated way of listing individual entries, e.g., writing 3.* is a short way of representing 3.1., 3.2., 3.3., 3.4., 3.5., etc.
All data structures of the scheduler or calendar objects support dates with wildcards. Date ranges and time specifications do not support wildcards. Invalid weekdays are ignored.
Date entries with wildcards
Date | Meaning |
|---|---|
23.April.2001 /Monday | 23.April.2001, Monday |
23.April.2001 /Tuesday | Never, since 23.April 2001 is a Monday |
23.April.2001 /* | 23.April.2001 |
23.April.* /Monday | Each April 23rd, each year if the weekday is a Monday |
*.April.2001 /* | Every day in April 2001 |
*.April.* /Tuesday | Each day in April of each year if the weekday is a Tuesday |
31.*.* /* | Each January 31, March 31, May 31, … of each year |
If a date contains a wildcard in the month or year, the last day of the month is used for the day, if the value of the day is greater than the maximum number of days in the month.
Week and day with wildcards
The following table shows an example of entering a week and day (WeekNDay) using wildcards. During the evaluation, a wildcard is replaced by the corresponding value of the current date. If the WeekNDay generated in this way is equivalent to the current date, this is an exception day.
Day of the week | Meaning |
|---|---|
January/2/Monday | Monday in the second week of January |
*/1/Tuesday | Every first Tuesday of a month |
February/*/Wednesday | Every Wednesday in February |