Maintaining Journals and Log Files

SQDR Plus takes advantage of the standard OS/400 pruning operations to prune the SQDR control tables and journal receivers. If you have the autoJournal configuration parameter enabled (see autoJournal in the Configuration Reference), there should be no need to manage the journal receivers. If you are manually managing journal receivers you can remove only journal receivers that are not currently being used by SQDR Plus. As is typical with sharing objects in a multitasking environment, SQDR Plus places a transient lock on objects while they are in use. SQDR Plus will never delete a system or user journal, journal receiver, file, or table.

If SQDR Plus is not running, an Exit Program named CADLTRCV (Capture Agent Delete Receiver) manages which receivers the Log Reader will need when the Capture Agent is restarted.

Be careful not to delete receivers that the Capture Agent needs when it is started again. If you override the protection of the CADLTRCV exit program and delete receivers from the chain you will need to re-run a baseline snapshot before the subscription can resume tracking and replicating incremental changes.

After SQDR Plus is monitoring subscriptions for incremental changes there may be repetitive notification messages sent to the operator’s QSYSOPR message queue if there is a long delay, such as 30 minutes, between an IPL and restarting the SQDR subsystem. You can avoid flooding the message queue while the SQDR journal receivers are unavailable by issuing the following Change Journal (CHGJRN) command, replacing SQDR/SQDR with your schema and subsystem name if they are different:


This command changes the Delete Receiver Delay from the default value of 10 minutes to 1440 minutes so that notifications about the SQDR receivers are sent only once per day. Whatever time interval is specified for the DLTRCVDLY command option is used until the command is issued again.