Advanced scheduling

Advanced scheduling uses the Network Configurator to enter Fileset Local, Fileset FTP, Database, HTTP Client, Java, and UPoC schedules. This is in terms of absolute dates and time, instead of offset seconds. Schedules can be set for backups, alerts, file transfers, and so on.

When selected, advanced scheduling is used in place of interval-based scheduling for the thread being configured.

Caution: 
Exercise caution when using advanced scheduling, as you could create schedules that request impossible behavior from the engine.

Absolute time entry circumvents the problem of using an offset time if the thread is restarted. For example, if an offset seconds equivalent of 12 hours is entered and the thread is restarted, the event happens 12 hours later.

Each event that is listed under a schedule has an entry similar to crontab. This specifies the recurrence times, a description, and, in the case of UPoC, a Tcl procedure stack and corresponding arguments.

After the Network Configurator obtains the protocol selection and timer event schedules from the user, it generates a Tcl list containing this schedule. This list is stored in the NetConfig file. The engine extracts the scheduling information from this Tcl list, and registers and updates the timer events.

Because scheduled events are recurring events, certain commands are provided to check the status and to disable and enable individual events or entire schedules.

Note: User discretion is required when using advanced scheduling. If the running of a Fileset or UPoC activity takes a long time, then the scheduling of the next event could be missed.

For example, several files take ten minutes to be read by the engine using the Fileset protocol. These events are scheduled every five minutes. At least one activity does not get scheduled. This is because the next event is scheduled after the last event has finished running. Only one event is scheduled at a time per thread.

If advanced scheduling is set, then the timer event is run only when advanced scheduling is triggered. Fileset-local and Fileset-FTP protocol threads do not immediately run the event when the thread starts. This also applies to the database and Java driver protocols.