Previous Topic: SCHEDULE CommandNext Topic: Resource Limit Options


Initial Date/Time Options

AT hh:mm:ss

Specifies the time of day to initiate the request. If you do not specify AT nor FROMTIME, the time of day defaults to a site-specified delay interval from the moment you issued the command. See Start Times for more information about when requests are scheduled to start.

CLASS class

Specifies the initiation class for the request. class is the one-character class identifier under which the command is to operate. Valid class values are A-Z and 0-9, and your system administrator defines these values. You cannot use this option with the following options:

Note: Requests scheduled with the CLASS option are initiated by a CA VM:Schedule operator or through a schedule determined by your site. You can reschedule classed requests, but not more than once per day. To determine what classes (and resource limits per class) have been specified at your site, use the CONFIG command.

Note: For information about the request processing classes that correpond to the SCHEDULE CLASS option, see "CLASS: Defining Classes" in the CA VM:Schedule Administration Guide.

FROMTIME hh:mm:ss

Specifies the time of day at which the EXEC is to initiate. Use FROMTIME with TO to specify a time period that spans midnight. If FROMTIME is used with AT time, the FROMTIME option takes precedence. See Start Times for more information about when requests are scheduled to start.

FROM mm/dd/yy

Specifies the date of the first (or only) request initiation. If the FROM option is not specified, the first initiation defaults to the current date unless you specify that initiation is to occur on certain days of the week or the specified time has passed for the current day.

All dates that you specify with the FROM option must contain a month and a day. If you omit the year, the default is the current year. The latest date that you can specify is December 31, 2041. Year ranges from 00 through 41 are taken to be in the 21st century.

FROM dayname

Specifies the day of the first (or only) request initiation. If dayname is today, the server schedules the request to run a week from today. If the FROM option is not specified, the first initiation defaults to the current date unless you specify that initiation is to occur on certain days of the week or the specified time has passed for the current day.

FROM options

Schedules a request’s first, or only initiation on a given day, or week of a particular week, month, or quarter. The following table describes the options and meanings:

Option

Meaning

nnn

Starts the request on the nth day or week. For example, to start a request on the second Monday in January, use these FROM options:

from 2 mon jan

F

Starts the request on the first day of the specified time unit (weekend, business week, week number, month number). For example, to start a request on the first Monday in November, use these FROM options:

from f mon nov

L

Starts the request on the last day of the specified time unit (weekend, business week, week number, month number). For example, to start a request on the last Monday in November, use these FROM options:

from l mon nov

dayname

Starts a request on a specific day of the week (MON, TUE, WED, THU, FRI, SAT, or SUN)

WE

Starts a request on a weekend day

W

Starts a request at the beginning (Monday) of the specified week. For example, to start a request the beginning of the third week in July, use these FROM options:

from 3 w jul

B

Starts a request on a business day

weeknumber

Starts a request the nth week from the current week: 001 means next week, 002 means the week after that, and so on. For example, to start a request on Tuesday of next week if specified on Monday of the current week, use the following FROM options:

from 1 tue 001

M

Starts a request on the specified day or week of the current month. For example, to start a request on the third week of this month, use these FROM options:

from 3 w m

monthname

Starts a request on the specified day or week of the named month (such as JAN or FEB). For example, to start a request on the second weekend day in January, use these FROM options:

from 2 we jan

Q

Starts a request on the specified day or week of the current quarter. For example, to start a request on the last business day of this quarter, use these FROM options:

from l b q

nQ

Starts a request on the specified day or week of the nth quarter. For example, to start a request the first week of the fourth quarter, use these FROM options:

from f w 4q
ON day

Specifies the day of the week on which the EXEC is scheduled to execute. Valid day values are MON, TUE, WED, THU, FRI, SAT, and SUN. The initial run date is calculated to fall on the next occurrence of day. EXECs scheduled for a specific day cannot be repeated using the AGAIN DAILY or AGAIN MONTHEND options; however, any other AGAIN scheduling intervals can be specified. You can use ON with the FOR option as a repeat factor.

RELEASE userid

Specifies this request as a dependent request. Requests scheduled with the RELEASE option are never explicitly scheduled for execution. Therefore, the server ignores all scheduling parameters except WITHIN. The user ID specified is a user ID that is allowed to release the request for initiation using the RELEASE command. Other user IDs can release the request, including the user ID of the person owning the request and a user ID having NOPASS authority. Also, a person knowing the password of the person owning the request can release the request.

WITHIN {hh:mm:ss | *}

Specifies the amount of time CA VM:Schedule is to keep trying to start the request if it cannot start at the scheduled time. If the EXEC does not start within this amount of time, it is skipped. Your site can define the default initiation time limit. If you specify *, the WITHIN time is unlimited.

Repeat Options

[AGAIN [BI] interval]

Specifies how often you want to run the request.

BI repeats the request every other interval. For example, AGAIN BI DAILY repeats a request every other day. BI is not valid with the HOURLY, YEARLY, number DAYS, or number BDAYS options.

The following table describes the intervals and purpose:

Interval

Purpose

HOURLY

Starts the request every hour (not valid with BI)

DAILY

Starts the request every day; for example, AGAIN DAILY starts a request every day; AGAIN [BI] DAILY starts a request every other day

BDAILY

Starts the request every business day

WEEKLY

Starts the request every week

WEEKEND

Starts the requests every weekend day

MONTHLY

Starts the request every month

QTRLY

Starts the request every quarter

YEARLY

Starts the request every year (not valid with BI)

MONTHEND

Starts the request on the last day of the month

QTREND

Starts the request on the last day of the quarter

number DAYS

Starts the request every number of days (not valid with BI)

number BDAYS

Starts the request every number of business days (not valid with BI)

DURING options

Repeats the request on the requested day or days during the specified period. Options are:

nnn

Repeats a request on the requested days every nnnth week (Monday through Sunday). For example, again daily during three schedules a request to run daily for a week every three weeks.

M

Repeats a request on the specified days or weeks of the current month; for example, on mon during m repeats a request every Monday during this month.

monthname

Repeats a request on the specified days or weeks of the named month (such as JAN or FEB). For example, again daily during feb repeats a request every day during February.

Q

Repeats a request on the specified days, weeks, or months of the current quarter; for example, again weekly during q repeats a request every week during this quarter.

nQ

Repeats a request on the requested days, weeks, or months of the specified quarter; for example, again daily during 1q repeats a request every day during the first quarter.

[ON day[-day]]...

Specifies the day of the week on which the request is scheduled to execute. Valid day values are MON, TUE, WED, THU, FRI, SAT, and SUN. The initial run date is calculated to fall on the next specified day. When you use this option with the DURING option, the server repeats the request on the requested day or days during the specified period.

Requests scheduled for a specific day cannot be repeated using the AGAIN BDAILY, AGAIN DAILY, AGAIN MONTHEND, AGAIN WEEKEND, or AGAIN QTREND options; however, any other AGAIN scheduling intervals can be specified. You can use ON with FOR option as a repeat factor.

You can specify the ON option multiple times, for example, on mon on wed on fri.

You can use a dash to specify a range of days for example, mon-fri, sat-sun.

EVERY hh:mm:ss

Specifies the interval of time until the next initiation of a request on a given day. The maximum interval is 23:59:59 and can extend beyond midnight.