When you create a journal with iSeries Navigator or the Create Journal (CRTJRN) command, you can select to have either system managed or user managed journal receivers.
The default for the CRTJRN command is to have the system manage the journal receivers.
If you specify user journal receiver management, you are responsible for changing the journal receiver when it approaches its storage threshold. If you choose this option, you can have the system send a message to a message queue when the journal receiver approaches its storage threshold.
If you use system journal-receiver management, you can avoid having to do some journal management chores. However, if you are journaling for recovery purposes, you need to ensure that you save all journal receivers that have not been saved, not just the currently attached receiver. Also, if you are journaling for recovery purposes, be sure to specify that the system does not automatically delete receivers when no longer needed. Automatic deletion of journal receivers describes this option.
If you use system journal-receiver management, you must ensure that your environment is suitable and that you regularly check the QSYSOPR message queue and the message queues assigned to your journals.
If the system cannot complete the change journal operation because it cannot obtain the necessary locks, it retries every 10 minutes (or as specified by the MNGRCVDLY parameter). It sends messages (CPI70E5) to the journal's message queue and to the QSYSOPR message queue. If this occurs, you may want to determine why the operation cannot be performed and either correct the condition or swap the journal receiver your self with iSeries™ Navigator or the CHGJRN command.
If the system cannot complete the change journal operation for any reason other than lock conflicts, it temporarily discontinues system journal-receiver management for that journal and sends a message (CPI70E3) to the message queue assigned to the journal or to the QSYSOPR message queue. This might occur because a journal receiver already exists with the name that it would generate. Look at the messages in the QHST job log to determine the problem. After you correct the problem, perform a swap journal operation to do the following:
When you restart the system or vary on an independent disk pool, the system performs a CHGJRN command to change the journal receiver and reset the journal sequence number.
Also, if the journal is attached while a maximum receiver-size option is specified, the system attempts to perform a CHGJRN command to reset the sequence number when the following is true:
For all other journal receivers, the system attempts this CHGJRN when the sequence number exceeds 2 147 000 000.
The system does not reset the journal sequence number when you restart the system or vary on an independent disk pool if the entries in the receiver may be needed for commitment control recovery.
If you use the CRTJRN or CHGJRN command, you can use the Manage Receiver Delay Time (MNGRCVDLY) parameter. When you use system journal-receiver management for a journal, if the system cannot allocate an object needed to attach a new journal receiver to the journal, it will wait the length of time that you specify in the MNGRCVDLY parameter before its next attempt to attach the new journal receiver. If you do not specify this parameter, the system will wait ten minutes, which is the default.
The following topics have information related to management of journal receivers: