The following items should be read and understood before working with timetables.
General
You cannot schedule real-time reports, Vector Contents, or custom report creation through a timetable.
Timetables run in the background, not in the terminal session.
Timetables that fail at some point during execution are logged in the Maintenance Error Log Report.
Up to five timetables can be scheduled to run at the same time.
You can have tasks associated with different ACDs in the same timetable.
Do not create a timetable that attempts to write a file in the home directory of different user.
The ACD that is currently selected when a timetable task is created will be the ACD on which the task runs. To change the ACD, you must delete the task and reset the current ACD before adding the correct task.
When a CMS user is deleted, any timetables associated with that user ID are also deleted. For this reason, it is recommended that mission-critical timetables be created under the cms user ID.
If the System Administration Terminal (SAT) terminal is still logged in to the Communication Manager system and is displaying a screen used in timetables, those timetables will not run.
Timetables cannot run if CMS is in single-user mode.
Printing
You cannot select the terminal as the destination for report output through a timetable.
To print a report more than once from a timetable, you must enter a task for each copy of the report.
Print jobs from timetables go to the default printer for the user who owns the timetable unless otherwise specified when the timetable is created. If the default printer for a user is changed, there is no need to edit the timetable as CMS automatically sends the print jobs from the timetable to the new default printer.
If a user specifies a printer other than their default printer for a timetable task and that printer is out of service, the timetable will not execute.
If the printer jams while attempting to print timetable tasks, you must resubmit the request that did not print.
Backups
Timetables for incremental and full backups are created when the system is installed, but are not scheduled.
Be sure to schedule backups to run either before archiving begins or after archiving has been completed.
