Scheduling Adhoc Tab

This tab contains the definitions of scheduled run times for the ad hoc processes.

Table 5-11 Scheduling Adhoc

Field Description Modifiable? - Possible values

Process

Adhoc process name.

No

Description

Description of reason for running this Adhoc process at the specified time.

Yes - Optionally describe the purpose for scheduling the Adhoc process at the specified time

Frequency

Frequency in minutes at which this Adhoc process is to be run.

Yes - Valid values are Daily meaning run this process once at the specified time, or EVERY:x, where x is number of minutes. For example EVERY:120 means run this process every two hours.

Limit Occurrences

Relevant only when frequency of EVERY:x is used. If a Limit Occurrences value is entered, the process will run a maximum of times equal to the specified limit.

Yes - A positive integer. For example: Frequency of EVERY:120 with a Limit Occurrences of 4 means the process will run every two hours a maximum of four times

Prevent start during nightly

A flag which, when set to Y, indicates that this process is not to be started when the Nightly process is running. If the Scheduler tries to start a run while Nightly is running, the execution's status is set to Error with an Info message of "Nightly started running so can't run the process."

Yes - Valid values are Y or N.

Schedule Time

Entering a time in this field causes the process to be scheduled at that time in case of a DAILY frequency or to start the first run at that time in case of an EVERY:x frequency.

Leaving this field blank causes the process to run immediately or the first run to start immediately when the scheduler day starts.

If a specific time is entered in this field but the scheduler day starts after that time, the process will be scheduled for the next day at that time.

Yes - Enter a valid military time format such as 6:00 (6am) or 22:00 (10pm).

Enabled

Flag indicating if this process is to be scheduled.

Yes - Valid values are Y or N.

Timezone Region ID

Timezone corresponding to the time entered in the subsequent cell(s). Timezone region ID is required rather than a UTC offset such as UTC-06:00. This is to accommodate Daylight Saving Time.

Yes - Valid timezone region IDs such as US/Eastern can be found as TZ database name at https://en.wikipedia.org/wiki/List_of_tz_database_time_zones