STOP
STOP BEFORE or AFTER option
Use the STOP parameter to limit how much the Span Accessory will replicate by specifying when it should stop processing audit information.
Note: 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 the Span Accessory start date. For example, when Span Accessory starts, it calculates an Audit file STOP date based on the current date plus or minus the “+/- days” parameter. Span Accessory stops when it reaches an Audit file with this calculated date.
The following table explains the STOP parameters:
STOP Parameter |
Description |
STOP AFTER n AUDIT FILES |
Span Accessory will stop processing at the first quiet point after n audit files have been processed. Use this option to set the maximum number of audit files Span Accessory will read during a Span Accessory run. For example, the following command informs Span Accessory to stop processing after seven audit files: STOP AFTER 7 AUDIT FILES |
STOP AFTER n RECORDS |
Span Accessory will stop processing at the first quiet point after n records have been processed. Use this option to limit the number of records Span Accessory will write to its update files during a run. For example, the following command informs Span Accessory to stop processing at the first quiet point after 1000 records: STOP AFTER 1000 RECORDS |
STOP BEFORE or AFTER hh:mm [AM or PM] [ON + days] |
Span Accessory will stop processing at either the last quiet point before or the first quiet point after the time (hh:mm) and number of days (0 indicates current) specified. Use this option to set the earliest or latest time and date at which Span Accessory will stop processing. For example, the following command informs Span Accessory to stop processing at the last quiet point before 10:30 p.m.: STOP BEFORE 10:30 PM |
STOP BEFORE or AFTER "[(usercode)]taskname" |
Span Accessory will stop processing at either the last quiet point before the designated task started or the first quiet point after the designated task is completed. If you specify a usercode, Span Accessory looks for a task name match under the specified usercode. Otherwise, Span Accessory looks for task name match under any usercode. Use the STOP AFTER option to coordinate termination of Span Accessory with that of another, unrelated task. When Span Accessory finds a record in the audit trail that is a result of the specified task doing a CLOSE on the database, it stops at the next QPT. Use the STOP BEFORE option to ensure that Span Accessory update data represents the data available before the specified task started. When Span Accessory finds a record in the audit trail that is a result of the specified task doing an OPEN UPDATE on the database, it rolls back to the previous QPT, which results in stopping before the specified task. For example, the following command informs the Server Accessory to stop processing at the first quiet point after the EOT of a task named 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, Span Accessory will stop processing at either the last quiet point before the designated task started or the first quiet point after the designated task finished 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 the Server Accessory 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 |
|
|
 |