Generates the command and opens the Run Now or Save Command window.
Cancels any changes that you made and closes this window.
Select a schema that identifies a running Q Apply program whose parameters you want to change.
Shows the parameter values that the Q Apply program is currently using. To change a value, select a keyword and use the controls in the Value area.
Find
Resets the value of the selected parameter to the default.
Select if you want the Q Apply program to stop running after all receive queues have been empty once. Clear if you want the Q Apply program to continue running even when all receive queues are empty (the default).
Specify how often the Q Apply program saves statistics about its performance. The default is every 60000 milliseconds (1 minute) on z/OS, or 30000 milliseconds (30 seconds) on Linux, UNIX, and Windows.
Specify a unit of time for the Q Apply monitor interval: seconds, minutes, or hours.
Specify how long the Q Apply program keeps statistics about its performance before deleting them. The default is one week.
Specify a unit of time for the Q Apply monitor limit: minutes, hours, days, or weeks.
Specify how long the Q Apply program saves trace data. The default is one week.
Specify a unit of time for the Q Apply trace limit: minutes, hours, days, or weeks.
Specify the number of times that the Q Apply program can try to reapply changes to targets or update its control tables after an SQL deadlock. The default is three attempts.
Specify how often the Q Apply program checks to see if performance data or trace data is old enough to delete. The default is 5 minutes.
Specify a unit of time for the Q Apply prune interval: minutes, hours, days, or weeks.
Select to have the Q Apply program reuse its log file when it restarts by erasing the file contents then writing to the blank file. Clear if you want the Q Apply program to append messages to the end of the file when it restarts (the default).
Select to stop the Q Apply program when DB2 is unavailable (quiesced, stopped, etc.). Clear if you want the Q Apply program to keep running while DB2 is unavailable. On z/OS, Q Apply terminates regardless of the setting for term if Resource Recovery Services (RRS) abnormally terminates.