[Scheduling]

The Scheduling parameters section only applies to the dbutility process command. You must run the process command once before the scheduling takes effect. For more information, see Scheduling dbutility Updates.

To schedule Client runs that are initiated from the Client Console, use the Scheduling parameters in the Client Configuration dialog box. For more information, see the DATABridge Client Console Help.

Parameter	Description
blackout_period	Use this parameter to specify a fixed block of time during which the client cannot run. This parameter is useful for operations, such as database backups, that can only take place when the Client is inactive. For example, if you want to back up the database daily between 1:00 a.m, and 2:30 a.m. daily, define a blockout period from 0:55 to 2:30. The extra 5 minutes ensures that the Client finishes any long transactions before the database backup begins. If the Client is running when the blackout period starts, the Client automatically stops. If the Client is waiting for an idle host to send it updates when the blackout period starts, the Client resets the TCP/IP connection and aborts the run if it hasn't received any updates after 15 seconds. If you try to run the Client during a blackout period, nothing happens. When the blackout period ends, the Client automatically restarts (dbutility) or is restarted by the service (DBClient).
daily	Default: daily = 08:00, 12:00, 17:00, 24:00 Range: 12 entries in ascending order from 00:00 to 24:00 Note: The daily parameter is mutually exclusive with the sched_delay_secs parameter. If you specify both daily and sched_delay_secs in the [scheduling] section of the configuration file, sched_delay_secs overrides daily regardless of the order in which they are specified. Enter the times you want the dbutility process command to wake up and gather updates from the DMSII database. You must specify 24-hour time (for example, 5:00 for 5:00 a.m. and 17:00 for 5:00 p.m.). The range for minutes is 00–59. You can specify up to 12 times for the daily parameter. However, you must specify the times in ascending order. Note the following: The values 00:00 and 24:00 are equivalent for midnight. 24:00 is allowed only so that you can put it at the end of the list of times in ascending order. 24:01 is not allowed; instead, specify, 00:01.
exit_on_error	Default: True Range: True or False The exit_on_error parameter indicates that the scheduling should be terminated if an error occurs. If this parameter is set to false, the process command is retried at the next scheduled time.
fixed_delay	Deprecated in DATABridge Client 6.1. Use sched_delay_secs instead.
min_wait	Deprecated in DATABridge Client 6.1. Use sched_minwait_secs instead.
retry_time	Deprecated in DATABridge Client 6.1. Use sched_retry_secs instead.
sched_delay_secs	Default: 0 Range: 0–86,400 seconds (24 hours) Note: The sched_delay_secs parameter is mutually exclusive with the daily parameter. If you specify both daily and fixed_delay in the [scheduling] section of the configuration file, fixed_delay overrides daily regardless of the order in which they are specified. Use the sched_delay_secs parameter to specify a time delay between successive executions of the process command. The sched_delay_secs parameter does use the retry_time parameter. To disable the sched_delay_secs parameter, comment it out or set its value to 0. Replaces the fixed_delay parameter.
sched_minwait_secs	Default: 0 Range: 0–86,400 seconds (24 hours) This parameter ensures that next scheduled process command is delayed by the specified interval and doesn't occur too soon after the current scheduled time. Replaces the min_wait parameter.
sched_retry_secs	Default: 3600 seconds (1 hour) Range: 0–86,400 seconds (24 hours) The sched_retry_time parameter only applies after a failed process command. A value of 0 means that dbutility schedules the next run at the next regularly scheduled time without any retries. For example, if the mainframe is down when dbutility attempts a process command using the scheduling option, dbutility will retry the operation after the specified amount of time has elapsed. If the retry time value is larger than the next scheduled time, dbutility retries at the next scheduled time. Replaces the retry_time parameter.