This document covers the following topics:
A transaction that changes the master file is logged in the master file's log file to be applied later to the replicate files. After ETP applies the transactions to the replicate files, you can remove the completed transactions from the log file using this function.
By either entering the Cleanup Logfile direct command
CL or selecting the CL
task on the ETP main menu,
the Clean Up Log File screen appears.
23:59:59 ***** ENTIRE TRANSACTION PROPAGATOR ***** 2000-12-24
Clean up log file
DBID FNR
First log file to be processed ..* _____1 _____1
Last log file to be processed ..* ___254 ___255
Time stamp or time value for last transaction to be deleted
Time stamp .. A6A6BDBD561F6000 (hexadecimal value)
Time ........ 1992-11-26 10:07:29.3 (yyyy-mm-dd hh:mm:ss.t)
Refresh file if all transactions are replicated .... N (Y/N)
Self-restart interval .............................. (hh:mm:ss)
Number of updates for which ETs are to be skipped .. 0
Number of READs before STOP TASKS flag is checked .. 1000
Command ===>
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Menu Exit Last Flip Tech Canc
|
| First log file to be processed (DBID/FNR) |
Enter the beginning database ID and file number of the first (inclusive) or only log file for which replicated transactions are to be deleted. If you enter a wild card in either the database ID or file number field, a window appears from which you can select a single log file. |
| Last log file to be processed (DBID/FNR) |
Enter the ending database ID and file number of the last (inclusive) or only log file for which replicated transactions are to be deleted. If you wish to specify only one log file on one database, enter that DBID/file number in both this field and in the Start DBID/FNR field. If you enter a wild card in either the database ID or file number field, a window appears from which you can select a single log file. |
You can limit deletion to all transactions up to and including a time earlier than the current time by entering that earlier time in one of the following fields:
| Time stamp | Enter a valid time stamp as stop time. Transactions that are time-stamped with a later (newer) time will not be deleted. If you enter a time stamp value here, do not enter a date/time value in the next field. The default is the current time (the time when you called this screen). |
| Time | Enter a valid date/time value for the confirmation file.
Transactions that are time-stamped with a later (newer) time will not be
deleted. If you enter a date/time value here, do not enter a time stamp value
in the previous field. The default is the current time (the time when you
called this screen).
Entries in the Time field are first converted to the time stamp value and then back to normal notation. This conversion can result in a value slightly different from the entered value. |
| Refresh file if all transactions are replicated |
If you specify Y, ETP refreshes the log file when
all transactions are applied to all replicate databases. Because updating the
Adabas index for deletions is quite resource consuming, refreshing a file is
much more efficient than deleting all transactions separately. Note that to use
this option, the ADALOD parameter PGMREFRESH=YES must
have been specified when the log file was created. The default is
N, meaning no automatic refresh of the log file occurs.
Note that it is impossible to refresh a log file that is also used as an administration or confirmation file. |
| Self-Restart Interval | Specify the elapsed time between restarts of the clean-up task.
If this field is left blank, no restart interval applies. Valid values range
00:00:01 through 24:00:00.
|
| Number of updates for which ETs are to be skipped |
Enter the count of update calls to the log file for which
corresponding ET calls will not be made. With this count
(n), you can specify that the first
n update calls to the log file will not
result in ET calls. The default (0) means that no ET calls to the replicate file's database are skipped. When the specified count of calls has been skipped, the calls begin and continue until the next ET call to the master file. The count is then reset, and skipping begins anew. |
| Number of READs before STOP TASKS flag is checked |
This number is the count of |
The subprogram WADUSER3 is used to
display all messages issued by the clean-up task. WADUSER3 can be
modified to filter the task messages and, if desired, send them directly to the
operator console. (For more information about the WADUSER3
subprogram, which is delivered in source form with ETP, see ETP
Installation.)
