What replication processes are started by the STRDG command - assure_mimix

What replication processes are started by the STRDG command - assure_mimix - 10.0

Assure MIMIX Operations Guide

Product type

Software

Portfolio

Integrate

Product family

Assure

Product

Assure MIMIX™ Software

Version

10.0

Language

English

Product name

Assure MIMIX

Title

Assure MIMIX Operations Guide

2023

First publish date

1999

Last updated

2024-03-12

Published on

2024-03-12T11:06:36.794496

MIMIX determines how each data group is configured and starts the appropriate replication processes based on the value you specify for the Start processes (PRC parameter). Default configuration values create data groups that use MIMIX Remote Journal support (MIMIX RJ support) for database replication and source-send technology for object replication.

The following table identifies the processes that are started when MIMIX RJ support is used for database replication for each of the possible values on the PRC parameter. An RJ link identifies the IBM i remote journal function, which transfers data to the target system. On the target system, the data is processed by the MIMIX database reader (DBRDR) before the database apply process (DBAPY) completes replication.

For data groups that use MIMIX RJ support, it is standard practice to leave the RJ link active when the data groups are ended. If the RJ link is not already active when starting data groups, MIMIX starts the RJ link when the value specified for the PRC parameter includes database source system processes or all processes. The RJ Link column in the following table shows the result of each process when the RJ link is not active while the Notes column identifies behavior that may not be anticipated when the RJ link is already active.

Table 1. Processes started by data groups configured for MIMIX Remote Journal support. This assumes that all replication processes are inactive when the STRDG request is made.
Value for PRC	Notes	Source Processes					Target Processes
		DB replication	Object replication				DB replication		Object replication
		RJ Link¹	OBJSND	OBJRTV	CNRSND	STSRCV	DBRDR	DBAPY²	OBJRCV	CNRRCV	STSSND	OBJAPY
*ALL		Starts¹	Starts	Starts	Starts	Starts	Starts	Starts	Starts	Starts	Starts	Starts
*ALLSRC	A	Starts¹	Starts	Starts	Starts	Inactive	Inactive	Inactive	Starts	Starts	Inactive	Inactive
*ALLTGT	A,B	Inactive¹	Inactive	Inactive	Inactive	Starts	Starts	Starts	Inactive	Inactive	Starts	Starts
*DBALL	A	Starts¹	Inactive³	Inactive³	Inactive³	Inactive³	Starts	Starts	Inactive³	Inactive³	Inactive³	Inactive³
*OBJALL	A,C	Inactive¹	Starts	Starts	Starts	Starts	Inactive⁴	Inactive⁴	Starts	Starts	Starts	Starts
*DBSRC	A,C	Starts¹	Inactive³	Inactive³	Inactive³	Inactive³	Inactive	Inactive	Inactive³	Inactive³	Inactive³	Inactive³
*DBTGT	A,B	Inactive¹	Inactive³	Inactive³	Inactive³	Inactive³	Starts	Starts	Inactive³	Inactive³	Inactive³	Inactive³
*OBJSRC	A,C	Inactive¹	Starts	Starts	Starts	Inactive	Inactive⁴	Inactive⁴	Starts	Starts	Inactive	Inactive
*OBJTGT	A,C	Inactive¹	Inactive	Inactive	Inactive	Starts	Inactive⁴	Inactive⁴	Inactive	Inactive	Starts	Starts
*DBRDR	A,D	Inactive¹	Inactive³	Inactive³	Inactive³	Inactive³	Starts	Inactive	Inactive³	Inactive³	Inactive³	Inactive³
*DBAPY	A,C	Inactive¹	Inactive³	Inactive³	Inactive³	Inactive³	Inactive⁴	Starts⁴	Inactive³	Inactive³	Inactive³	Inactive³
Notes: A. Data groups which use cooperative processing should have both database and object processes started to prevent objects and data on the target system from becoming not fully synchronized. B. When the RJ link is already active, database replication becomes operational. C. When the RJ link is already active, database journal entries continue to transfer to the target system over the RJ link D. When the RJ link is already active, database journal entries continue to transfer to the target system over the RJ link, where they will be processed by the DBRDR.

Note:

1-This column shows the effect of the specified value on the RJ link when the RJ link is not active. See the Notes for the effect of values when the RJ Link is already active, which is default behavior.

2-In data groups configured for multithreaded database apply processing, starting the database apply process also started the multithreaded job. In data groups configured for single-threaded database apply processing, an access path maintenance job is also started if the access path maintenance (APMNT) policy has been enabled at the installation or data group level.

3-These object replication processes are not available in data groups configured for database-only replication.

4-These database replication processes are not available in data groups configured for object-only replication.

Optionally, data groups can use source-send technology instead of remote journaling for database replication. Data groups created on earlier levels of MIMIX may still be configured this way.

The following table identifies the processes that are started by each value for Start processes when source-send technology is used for database replication. The MIMIX database send (DBSND) process and database receive (DBRCV) process replace the IBM i remote journal function and the DBRDR process, respectively.

Table 2. Processes started by data groups configured for Source Send replication This assumes that all replication processes are inactive when the STRDG request is made.
Value for PRC	Notes	Source Processes					Target Processes
		DB replication	Object replication				DB replication		Object replication
		DBSND	OBJSND	OBJRTV	CNRSND	STSRCV	DBRCV	DBAPY¹	OBJRCV	CNRRCV	STSSND	OBJAPY
*ALL	—	Starts	Starts	Starts	Starts	Starts	Starts	Starts	Starts	Starts	Starts	Starts
*ALLSRC	A	Starts	Starts	Starts	Starts	Inactive	Starts	Inactive	Starts	Starts	Inactive	Inactive
*ALLTGT	A	Inactive	Inactive	Inactive	Inactive	Starts	Inactive	Starts	Inactive	Inactive	Starts	Starts
*DBALL	A	Starts	Inactive²	Inactive²	Inactive²	Inactive²	Starts	Starts	Inactive²	Inactive²	Inactive²	Inactive²
*OBJALL	A	Inactive ³	Starts	Starts	Starts	Starts	Inactive³	Inactive³	Starts	Starts	Starts	Starts
*DBSRC	A	Starts	Inactive²	Inactive²	Inactive²	Inactive²	Starts	Inactive	Inactive²	Inactive²	Inactive²	Inactive²
*DBTGT	A	Inactive	Inactive²	Inactive²	Inactive²	Inactive²	Inactive	Starts	Inactive²	Inactive²	Inactive²	Inactive²
*OBJSRC	A	Inactive³	Starts	Starts	Starts	Inactive	Inactive³	Inactive³	Starts	Starts	Inactive	Inactive
*OBJTGT	A	Inactive³	Inactive	Inactive	Inactive	Starts	Inactive³	Inactive³	Inactive	Inactive	Starts	Starts
*DBRDR ⁴	—	—	Inactive²	Inactive²	Inactive²	Inactive²	—	—	Inactive²	Inactive²	Inactive²	Inactive²
*DBAPY	A	Inactive³	Inactive²	Inactive²	Inactive²	Inactive²	Inactive³	Starts ³	Inactive²	Inactive²	Inactive²	Inactive²
Notes: A. Data groups which use cooperative processing should have both database and object processes started to prevent objects and data on the target system from becoming not fully synchronized. B. When the RJ link is already active, database replication becomes operational. C. When the RJ link is already active, database journal entries continue to transfer to the target system over the RJ link D. When the RJ link is already active, database journal entries continue to transfer to the target system over the RJ link, where they will be processed by the DBRDR.

Note:

1- If the access path maintenance (APMNT) policy has been enabled at the installation or data group level, an access path maintenance job is also started.

2- These object replication processes are not available in data groups configured for database-only replication.

3- These database replication processes are not available in data groups configured for object-only replication

4- The database reader (*DBRDR) process is not used by data groups configured for source-send replication.