Using the Blueworx Voice Response report schedule

The Blueworx Voice Response report schedule is a file called $SYS_DIR/report_schedule containing the commands described in Using line commands, prefixed with a schedule specification.

An example of the report schedule is shown in Figure 1. Note you can have a different schedule for each item; you can even schedule the same task to be done on the same item daily, weekly, and monthly, or more than once a day or once a week.

Schedule specification

When you include one of the statistics management commands in a report schedule, the full command syntax is as follows:

{monthly day_of_month | weekly day_of_week| daily} hour_of_day any_command

monthly day_of_month hour_of_day: Run the command on the day_of_month, at hour_of_day.
weekly day_of_week hour_of_day: Run the command each week on day_of_week, at hour_of_day.
daily hour_of_day: Run the command each day, at hour_of_day.
day_of_month: The day on which the command is to run if it is to be run monthly. The value must be a number between 1 and 31.
day_of_week: The day on which the command is to run if it is to be run weekly. The value must be sunday, monday, tuesday, wednesday, thursday, friday, or saturday.
hour_of_day: The hour at which the command is to run. The value must be a number from 1 (one o'clock in the morning) through 24 (midnight).
any_command: You can use the $SYS_DIR/report_schedule file to schedule any other command to be run regularly, just by appending a schedule specification to it. For example, you could include the dt.log_mgr command.

Although you can use the -b flag to specify previous_day, previous_week, or previous_month in any combination with a daily, weekly, or monthly schedule, some combinations are more useful than others, as Table 1 shows.

Figure 1. An example of the $SYS_DIR/report_schedule file

# Archive all log files every day at one o'clock in the morning
daily 1 DTlogs -a -n "*"
# Print each report, covering the last seven days,
# every day at one o'clock in the morning
daily 1 DTreports -p -n Application -b previous_week
daily 1 DTreports -p -n Event -b previous_week
daily 1 DTreports -p -n HostApplErrors -b previous_week
daily 1 DTreports -p -n HostApplUsage -b previous_week
daily 1 DTreports -p -n HostLinkErrors -b previous_week
daily 1 DTreports -p -n HostLinkUsage -b previous_week
daily 1 DTreports -p -n RecoVocabUsage -b previous_week
daily 1 DTreports -p -n SystemStats -b previous_week
daily 1 DTreports -p -n Termination -b previous_week
daily 1 DTreports -p -n Traffic -b previous_week
# Create archive file of each report, covering Sunday through Saturday,
# every Sunday at two o'clock in the morning
weekly sunday 2 DTreports -a -n "*" -b previous_week
# Print all reports, covering the previous month's data
# on the first day of each month, at three o'clock in the morning
monthly 1 3 DTreports -d -n "*" -b previous_month
# Delete all statistics database tables, covering the previous month's data
# on the third day of each month, at three o'clock in themorning
monthly 3 3 DTdata -d -n sm_appl -b previous_month
monthly 3 3 DTdata -d -n sm_ccr -b previous_month
monthly 3 3 DTdata -d -n sm_events -b previous_month
monthly 3 3 DTdata -d -n sm_host_appl -b previous_month
monthly 3 3 DTdata -d -n sm_host_link -b previous_month
monthly 3 3 DTdata -d -n sm_reco_usage -b previous_month
monthly 3 3 DTdata -d -n sm_sys_stats -b previous_month
monthly 3 3 DTdata -d -n sm_term -b previous_month
monthly 3 3 DTdata -d -n sm_traffic -b previous_month
# Clean up oamtrace and errorlog files
# on the third day of each month, at four o'clock in the morning
monthly 3 4 DTlog_mgr

Table 1. Which combinations of schedule frequency and coverage are useful?
How Often is the Command Run?	How Much Data is Processed?
How Often is the Command Run?	previous_day	previous_week	previous_month
daily	Data for the preceding day.	Data for the preceding seven days.	Daily or weekly processing of the same (the previous month's) data is not really useful.
weekly	Processing one day's data only once a week or once a month is not really useful.	Data for the preceding seven days.
monthly		Processing one week's data only once a month is not really useful.	Data for the previous month.

Note: If you are deleting data monthly but creating weekly reports, make sure that you delete data on the 7th of the month or later, so that you always have a complete week of data to report.