STOP

Enter this command to stop DBServer from returning updates beyond a specified quiet point. The quiet point can be before or after a specified time, day, program, or a specific program on a specific date. For example, if you wanted to limit daily transactions to only those processed before 4:00 p.m., you would configure the STOP command to stop processing at the last quiet point before 4:00 p.m.

Time in the STOP command refers to the time the update occurred on the primary system, not the current time of day.

The “+/- days” are in relation to DBServer Worker start date. For example, when the Worker starts, it calculates an Audit file STOP date based on the current date plus or minus the “+/- days” parameter. The Worker stops when it reaches an audit location with this calculated date.

Use the following syntax when entering a STOP command:

STOP BEFORE or AFTER [timedate or "[(usercode)] taskname"]

The following table explains the STOP parameters:

STOP Options

Description

STOP BEFORE or AFTER hh:mm [AM or PM]

DBServer stops processing at either the last quiet point before or the first quiet point after the designated time. Note that the time entry hh:mm can be either 24-hour time format (22:30 for 10:30 p.m.) or 12-hour format (10:30 p.m.)

For example, the following command informs DBServer to stop processing at the last quiet point before 10:30 p.m.

STOP BEFORE 10:30 PM

STOP BEFORE or AFTER hh:mm [AM or PM] ON [+ or -] days

DBServer stops processing at either the last quiet point before or the first quiet point after the designated time and after the designated number of days. Note that the time entry hh:mm can be either 24-hour time format (22:30 for 10:30 p.m.) or 12-hour format (10:30 p.m.). Also note that a days entry of zero indicates the current day.

For example, the following command informs DBServer to stop processing at the last quiet point that occurs tomorrow before 10:30 p.m.

STOP BEFORE 22:30 ON + 1

STOP BEFORE or AFTER hh:mm [AM or PM] ON mm/dd/yyyy

DBServer stops processing at either the last quiet point before or the first quiet point after the designated time on the designated day. Note that the time entry hh:mm can be either 24-hour time format (22:30 for 10:30 P.M.) or 12-hour format (10:30 P.M.).

For example, the following command informs DBServer to stop processing at the first quiet point after 1:30 p.m. on December 9, 2009.

STOP AFTER 13:30 ON 12/9/2009

STOP BEFORE or AFTER "[(usercode)]taskname"

DBServer stops processing at either the last quiet point before the BOT or the first quiet point after the EOT of the designated task name.

If you specify a usercode, DBServer looks for a task name match under the specified usercode. Otherwise, DBServer looks for task name match under any usercode.

For example, the following command informs DBServer to stop processing at the first quiet point after the EOT of task name "OBJECT/SAVINGS/POSTING".

STOP AFTER "OBJECT/SAVINGS/POSTING"

STOP BEFORE or AFTER "[(usercode)]taskname" OR BEFORE or AFTER hh:mm [AM or PM] ON MM/DD/YYYY

Depending on which occurs first, DBServer stops processing at either the last quiet point before the designated task started or the first quiet point after the designated task ended OR at either the last quiet point before or the first quiet point after the designated time on the designated date.

For example, the following command informs DBServer to stop processing at the first quiet point after the EOT of task name "OBJECT/SAVINGS/POSTING" on December 9, 2009 or to stop processing at the last quiet point before 10:30 p.m. on December 9, 2009, whichever occurs first:

STOP AFTER "OBJECT/SAVINGS/POSTING" OR BEFORE 10:30 PM ON 12/9/2009

Keep in mind the following when using the STOP command:

  • If you enter a STOP BEFORE or AFTER "[(usercode)]taskname" OR BEFORE or AFTER hh:mm [AM or PM] ON MM/DD/YYYY command, DBServer will stop when either STOP command is satisfied.
  • If a STOP BEFORE "taskname" command is specified, DBServer will stop at the last quiet point before the task opened the database.
  • If a STOP AFTER "taskname" command is specified, DBServer will stop at the first quiet point after the task closed the database.
  • If more than one task name is specified, only the last one specified is used. Similarly, if more than one time/date is specified, only the last time/date specified is used.