Data Source Run Commands
The Run menu is only enabled when there is an active DBClient run for the data source. This program only executes
clone commands. See the available options below:
The Stop command allows the operator to stop the Client. When this command/option is selected the following dialog is opened:
See below for the available options:
Normal: indicates that the run will stop at the next quiet point. If you issue this command during the data extraction the run will stop only when the fixup phase begins.
AFN: the run will stop at the first quiet point in the audit file immediately following the one whose number is entered in the provided edit-box has been processed.
Time: Allows the operator to provide a date and time after which the run will stop at the next quiet point.
The Abort command allows the operator to stop the Client by forcing it to reset the connection to the server.
When this command is selected, a window that requests confirmation of the Abort command appears. Once the action is confirmed, the run terminates immediately regardless of whether it is processing updates or doing data extractions. Any uncommitted updates will be rolled back. If the Client was in the data extraction phase, all data sets that were currently being cloned will have a
ds_mode of 0, which will cause them to be re-cloned when the next
process command is issued.
The Commit Parameters command allows the operator to dynamically change the commit frequency parameters being used by the Client. The changes only remain in effect for the duration of the run. If the
batch_job_period parameter is enabled in the Client configuration file, changes made to the commit frequency parameters will be overridden when the current period ends. This command opens the following dialog, which is initialized using the Client's effective commit parameters.
Use the supplied input fields to change any of the parameters, and select OK to confirm the changes. Confirmed changes will be updated in the next commit. If you do not wish to modify the commit parameters, push the Cancel button to close the dialog without making any changes.
Switch Client Log
Selecting Switch Client Log causes the Client (DBClient) to close the current log file and open a new one.
The file name(s) include the date when the file is created (for example
db20210722.log). If the old log file was created on the same day as the new file, the new file name will also contain the current time to make the name identifiable (for example
db20210722_144825.log). When switching to a new log file the last line of the old log file will contain a line with the text:
14:48:25 Log file switched to "logs\\db20210722_144825.log" (Operator Keyin)
Selecting Switch Client Trace causes the Client (DBClient) to close the current trace file and open a new one.
The file names include the date when the file is created (for example
trace20210722.log). If the old trace file was created on the same day as the new file, the new file name will also contain the current time to make the name identifiable (for example
trace20210722_144825.log). When switching to a new trace file the last line of the old trace file will contain a line with the text:
Trace file switched to "trace20210726_091904.log" (Operator Keyin)
The Statistics command allows the operator to see the current performance statistics for the Client run. The output is displayed in a new page that has 3 tabs (Run, Client, and Statement).
The Run tab contains the performance statistics, which are the equivalent of the
"pstats" command in the command-line client. The Client contains the client status, which is equivalent to the
"status" commands in the command-line client. Finally, the Statement tab contains the statement statistics, which are equivalent to the
"astats" command in the command-line client.