Journal state and delivery mode

 

The journal state describes an attribute for a journal. The attribute value can be *ACTIVE, *INACTIVE (remote journal only), or *STANDBY (local journal only). For a local journal, *ACTIVE indicates that journal entries are currently allowed to be deposited into the journal. *STANDBY indicates that most journal entries are not deposited.

You can view the journal state for a remote journal on a target system that is associated with a journal on a source system in one of two ways:

• When viewing the remote journal information of the local journal from the source, *ACTIVE indicates that journal entries are currently being replicated to that remote journal on the target system. *INACTIVE indicates that journal entries are not currently being replicated.

• When viewing the journal attributes of the remote journal from the target, *ACTIVE indicates that journal entries are currently being received from the journal on the source system. *INACTIVE indicates that the target journal is not ready to receive journal entries from the source journal.

The following table provides a summary of the journal type, delivery mode and journal state interactions.

Journal type	Delivery mode	Journal state	Comments
*LOCAL	Not applicable	*ACTIVE	Objects journaled to the local journal can be changed, and entries can also be deposited into the local journal using the Send Journal Entry (SNDJRNE) command or the Send Journal Entry (QJOSJRNE) API interfaces. The currently attached journal receiver may or may not be currently replicated to one or more remote journals. This depends upon whether any remote journals have been added to the local journal's definition, and if so, the current journal state for each of those remote journals.
*LOCAL	Not applicable	*STANDBY	This is the state of a local journal after the Change Journal (CHGJRN) command specifying JRNSTATE(*STANDBY) is used to not allow deposits into the local journal. The local can journal can also be in *STANDBY state after an IPL if the local journal is in *STANDBY state when the system ends. Objects journaled to the local journal can be restored or changed, but most journal entries are not deposited until the journal state for the local journal is again changed to *ACTIVE. This can be performed by using the Change Journal (CHGJRN) command specifying JRNSTATE(*ACTIVE).
*REMOTE	*SYNCPEND	*ACTIVE	This is the state after a remote journal has been activated using the Change Journal State (QjoChangeJournalState) API or CHGRMTJRN command and the processing is still in the catch-up phase of remote journal activation. Synchronous delivery mode was requested on the API invocation.
*REMOTE	*SYNC	*ACTIVE	This is the state after a remote journal has been activated using the Change Journal State (QjoChangeJournalState) API or CHGRMTJRN command, after catch-up has completed, and changes to the currently attached journal receiver for the journal on the source system are being replicated synchronously to the remote journal on the target system.
*REMOTE	*ASYNCPEND	*ACTIVE	This is the state after a remote journal has been activated using the Change Journal State (QjoChangeJournalState) API or CHGRMTJRN command and the processing is still in the catch-up phase of remote journal activation. Asynchronous delivery mode was requested on the API invocation.
*REMOTE	*ASYNC	*ACTIVE	This is the state after a remote journal has been activated using the Change Journal State (QjoChangeJournalState) API or CHGRMTJRN command, after catch-up has completed, and changes to the currently attached journal receiver for the journal on the source system are being replicated asynchronously to the remote journal on the target system.
*REMOTE	*SYNC	*INACTPEND	This is the state of a remote journal, viewed from the target system where some failure has occurred and either the system is in the process of inactivating the remote journal, or unconfirmed journal entries exist in the remote journal. See Confirmed and unconfirmed journal entries for more information.
*REMOTE	*ASYNC	*INACTPEND	This is the state of a remote journal, viewed from the target system where some failure has occurred and the system is in the process of inactivating the remote journal.
*REMOTE	*ASYNC	*CTLINACT	This is the state after a remote journal has been made inactive using the Change Journal State (QjoChangeJournalState) API or CHGRMTJRN command, a controlled deactivate was requested on that call and that controlled deactive has not yet completed.
*REMOTE	Not applicable	*INACTIVE	This is the state after a remote journal has been added and associated with a journal on a source system. However, the journal state for the added remote journal has yet to be activated or has been made inactive using the Change Journal State (QjoChangeJournalState) API, CHGRMTJRN command, or by an IPL. No delivery mode is in effect for an inactive remote journal.

 

Parent topic:

Remote journal concepts

Related concepts
Confirmed and unconfirmed journal entries