The EVERY keyword causes synchronization to occur on startup, and then repeat indefinitely after the specified time period.
If the synchronization process takes longer than the specified period, synchronization starts again immediately.
Given one or more single schedules, synchronization occurs only at the specified days and times.
An interval is specified as @hh:mm-hh:mm (with optional specification of AM or PM). If AM or PM is not specified, a 24-hour clock is assumed. 24:00 is interpreted
as 00:00 on the next day. When an interval is specified, synchronization occurs, starting at a random time within the interval.
The interval provides a window of time for synchronization so that multiple remote databases with the same schedule do not
cause congestion at the MobiLink server by synchronizing at exactly the same time.
The interval end time is always interpreted as following the start time. When the time interval includes midnight, it ends
on the next day. If dbmlsync is started midway through the interval, synchronization occurs at a random time before the end
EVERYDAY is all seven days of the week.
WEEKDAY is Monday through Friday.
Days of the week are Mon, Tue, and so on. You may also use the full forms of the day, such as Monday. You must use the full
forms of the day names if the language you are using is not English, is not the language requested by the client in the connection
string, and is not the language which appears in the server messages window.
To specify the last day of the month regardless of the length of the month, set the dayOfMonth to 0.
The INFINITE keyword causes dbmlsync to synchronize on startup, and then not to synchronize again until synchronization
is initiated by another program sending a window message to dbmlsync. You can use the dbmlsync extended option NoSyncOnStartup
to avoid the initial synchronization. For more information, see NoSyncOnStartup (nss) extended option.
You can use this option in conjunction with the dbmlsync -wc option to wake up dbmlsync and perform a synchronization. For
more information, see -wc dbmlsync option.
If a previous synchronization is still incomplete at a scheduled time, the scheduled synchronization commences when the previous
The default is no schedule.
The Schedule option is ignored when the Dbmlsync API is used or when the SQL SYNCHRONIZE statement is used.
The IgnoreScheduling extended option and the -is option instruct dbmlsync to ignore scheduling, so that synchronization is
immediate. For more information, see IgnoreScheduling (isc) extended option.