Scheduling Updates

The process command has a built-in scheduling mechanism that allows the run to hibernate and resume at the next scheduled time. When the DBServer sends the Client an end-of-audit-reached status, dbutility normally terminates. However, if you enable scheduling, the DATABridge Client disconnects from the server and the database and hibernates until the next scheduled process command, when it reconnects to the server and the database. This scheduling mechanism only works after you run dbutility for the initial clone of the DMSII database. If the Client crashes or the power fails, scheduling will fail. Service-based scheduling has none of these shortcomings, as the scheduling task is taken over by the service. For details about service-based scheduling, see the DATABridge Client Console Help.

If you use the service, it takes over this functionality. When a DBClient run terminates, the service determines when the next process command should be run and then starts one when that time arrives. The advantage of service-based scheduling is that it immune to system failures, as the service automatically gets restarted when the system is rebooted.

To schedule updates

  1. Uncomment the scheduling parameters in the DATABridge Client configuration file. Scheduling parameters are listed under the [Scheduling] header in the configuration file.
  2. Select one of the following scheduling methods:
    • Daily scheduling
    • Fixed-delay scheduling
  3. Enter appropriate values for the following scheduling parameters, depending on whether you are using daily scheduling or fixed-delay scheduling. Each parameter is explained in [Scheduling].



    ;dbutility process command only


    ;daily = 08:00, 12:00, 17:00, 24:00

    ;exit_on_error = false

    ;sched_delay_secs = 600

    ;sched_minwait_secs = 3600

    ;sched_retry_secs = 3600

    As long as the process command completes successfully, dbutility becomes inactive (sleep) until the next scheduled time. If the scheduled dbutility process command is successful, the following message appears:

    Next update for DataSource datasourcename will run at hh:mm (delay = nn secs)

    Scheduling of updates will continue until any of the following occurs:

    • You reboot the DATABridge Client machine or end the DATABridge Client session
    • You enter a SCHED OFF console command when dbutility is processing updates
    • A DMSII reorganization (other than a garbage collection)

      Note: If you must stop the dbutility program, it is recommended that you use the QUIT command to exit at the next quiet point. If the Client is waiting for the server to send it updates when none are available and the use_dbwait configuration file parameter is set to true, you can use the QUIT NOW command, which resets the connection to the server and terminates the client run. If needed, you can also press Ctrl+C to terminate a session while dbutility is processing updates; however, this approach is not recommended.