Restoring journal receivers

The system does not restore a journal receiver over the journal receiver that is currently attached. The system does not restore a journal receiver over an existing journal receiver that contains more entries.

If you use the Save Changed Objects (SAVCHGOBJ) command to save journal receivers, this is likely to occur. The journal receiver that is attached at the time of the save operation is a changed object and is saved by the command. When you restore, you receive message CPF3706 and the system continues with the next journal receiver.

If your save procedure saves the currently attached journal receiver, you can try to restore a journal receiver with fewer entries than the journal receiver on the system. For example, assume that you save your journal receivers when receiver RCVR0006 is attached. RCVR0006 has 1500 entries. Later, you use the CHGJRN command to create and attach a new receiver. Now receiver RCVR0007 is attached. Receiver RCVR0006 is still on the system and has 4300 entries. If you attempt to restore receiver RCVR0006 from your save media volume, the operation fails because the saved copy has only 1500 entries.

If the library you specify on the restore command for a journal receiver does not exist, the system restores the journal receiver to the library that contains the journal. If you specify RSTASP(*SAVASP) and the ASP does not exist, the system typically restores the journal receiver to the same auxiliary storage pool (ASP) as the library that contains the journal.

Placing journal receivers in the correct auxiliary storage pool: If the attached journal receiver is not in the ASP that you want after the restore operation, follow these steps:

  1. Create a journal receiver in the ASP that you want.
    Follow your existing naming convention and use the same journal receiver attributes.
  2. Use the Change Journal (CHGJRN) command to attach the new journal receiver to the journal.