As with local journals, regularly save and delete your journal receivers to minimize the amount of online auxiliary storage which is used by the journal receivers.
The swapping of journal receivers for a remote journal is driven by the swapping of journal receivers on the source journal.
If you plan to move the responsibility for storing journal receiver data from the primary system to the remote system, you can elect to quickly delete journal receivers from the primary system after they have been replicated to the backup system with automatic deletion of journal receivers. On your backup system, you can then select to not use the automatic deletion of journal receivers on the remote journal, and manage the receiver save processing as you did before. Remember that once you add a remote journal, you cannot delete the source journal receiver until it has been replicated to all associated remote journals. Any journal receivers that are attached subsequently are also protected. The protection is eliminated when you remove the remote journal. If you have cascaded remote journals, consider using automatic deletion of journal receivers on the local journal, and on the lowest level remote journal. You would then not use automatic deletion of journal receivers on the cascaded remote journal since you plan to do your save processing on that system.
The Delete Journal Receiver exit point, QIBM_QJO_DLT_JRNRCV can be of assistance as well. For example, you might want to add an exit program to QIBM_QJO_DLT_JRNRCV which verifies that the journal receiver is no longer needed for any hot-backup application apply processing before it can be deleted. Refer to Delete journal receivers for information about this exit program.