Automatic deletion of journal receivers

If you choose system journal receiver management, you can also have the system delete journal receivers that are no longer needed for recovery. You can only specify this if you are using system journal receiver management.

The system can only evaluate whether a receiver is needed for its own recovery functions, such as recovering access paths or rolling back committed changes. It cannot determine whether a receiver is needed to apply or remove journaled changes.

Attention: Use automatic deletion of journal receivers with care if you use save-while-active operations to save objects before they reach a commitment boundary. Ensure that you save the journal receivers before the system deletes them. If an object is saved before it reaches a commitment boundary it can have partial transactions. To avoid data loss you must have access to the journal receivers that were attached during the save-while-active operation when you restore the objects with partial transactions.

The system will automatically delete journal receivers if you do one of the following:

However, even if you select one of the previous items, the system cannot delete the journal receiver if any of the following conditions is true:

If you use system delete-receiver support, you must ensure that your environment is suitable. You must also regularly check the QSYSOPR message queue and the message queues that are assigned to your journals.

Do not select to have the detached journal receiver deleted if you might need it for recovery or if you want to save it before it is deleted. The system does not save the journal receiver before deleting it. The system does not issue the warning message (CPA7025) that it sends if a user tries to delete a receiver that has not been saved.

Examples of when you might specify automatic journal deletion include:

Delay the next attempt to delete a journal receiver

If you are using the CRTJRN or CHGJRN command, you can use the Delete Receiver Delay Time (DLTRCVDLY) parameter. The system waits the time you specify (in minutes) with the DLTRCVDLY parameter before its next attempt to delete a journal receiver that is associated with the journal when one of the following is true:

If you do not specify this parameter, the system waits ten minutes, which is the default.

Save your server while it is active has instructions for saving an object with transactions in a partial state. Example: Recover objects with partial transactions has instructions for recovering objects with partial transactions.

Related concepts
Manual versus system journal-receiver management
Journals that are good candidates for remote journal management
Journal receiver management with remote journals
Related tasks
Save your server while it is active
Example: Recover objects with partial transactions
Delete journal receivers
Related reference
Create Journal (CRTJRN) command
Change journal (CHGJRN) command
Delete Journal Receiver exit point (QIBM_QJO_DLT_JRNRCV) API
Related information
Scenario: Data replication environment for remote journals