What replication processes are ended by the ENDDG command - assure_mimix

What replication processes are ended by the ENDDG command - assure_mimix - 10.0

Assure MIMIX Operations Guide

Product type

Software

Portfolio

Integrate

Product family

Assure

Product

Assure MIMIX™ Software

Version

10.0

ft:locale

en-US

Product name

Assure MIMIX

ft:title

Assure MIMIX Operations Guide

2023

First publish date

1999

ft:lastEdition

2025-02-05

ft:lastPublication

2025-02-05T16:54:28.225000

MIMIX determines how each data group is configured and ends the appropriate replication processes based on the value you specify for the Process (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 ended by each value for PRC when MIMIX RJ support is used for database replication. 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.

The communications defined by the RJ link remains active and is not affected by any value for PRC. In most cases, leaving the RJ link active is preferable. If necessary, you can end the RJ link by changing value for End remote journaling (ENDRJLNK parameter). Before ending replication describes when you need to end the RJ link.

Table 1. Processes ended by data groups configured for MIMIX Remote Journal support. This assumes that all replication processes are active when the ENDDG request is made and that the request does not specify to end the RJ link.
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		Active¹	Ends	Ends	Ends	Ends	Ends	Ends	Ends	Ends	Ends	Ends
*ALLSRC	A	Active¹	Ends	Ends	Ends	Active	Active	Active	Ends	Ends	Active	Active
*ALLTGT	—	Active¹	Active	Active	Active	Ends	Ends	Ends	Active	Active	Ends	Ends
*DBALL	B	Active¹	Active ³	Active ³	Active ³	Active ³	Ends	Ends	Active ³	Active ³	Active ³	Active ³
*OBJALL	A,B	Active ¹	Ends	Ends	Ends	Ends	Active ⁴	Active ⁴	Ends	Ends	Ends	Ends
*DBSRC	A,B	Active¹	Active ³	Active ³	Active ³	Active ³	Active	Active	Active ³	Active ³	Active ³	Active ³
*DBTGT	B	Active¹	Active ³	Active ³	Active ³	Active ³	Ends	Ends	Active ³	Active ³	Active ³	Active ³
*OBJSRC	A,B	Active¹	Ends	Ends	Ends	Active	Active ⁴	Active ⁴	Ends	Ends	Active	Active
*OBJTGT	A,B	Active¹	Active	Active	Active	Ends	Active ⁴	Active ⁴	Active	Active	Ends	Ends
*DBRDR	B,C	Active¹	Active³	Active³	Active³	Active³	Ends	Active	Active ³	Active ³	Active ³	Active ³
*DBAPY	B,D	Active¹	Active³	Active ³	Active³	Active ³	Active	Ends	Active ³	Active ³	Active ³	Active ³
Notes: A. Has no effect on database-only replication. New database journal entries continue to transfer to the target system over the RJ link, where they will be processed. B. Data groups that use cooperative processing may be affected by the result of this value. Ending database processes while object processes remain active may result in object activity entries being placed on hold. Similarly, ending object processes while database processes remain active may result in files being placed on hold due to error. C. New database journal entries continue to transfer to the target system over the RJ link. Existing entries stored in the log space on the target system before the end request was processed will be applied. D. New database journal entries continue to transfer to the target system over the RJ link, where they will be processed by the DBRDR.

Note:

1- The RJ link is not ended by the End options (PRC) parameter. New database journal entries continue to transfer to the target system over the RJ link. See the Notes column for additional details.

2- For data groups configured for multithreaded database apply processing, ending the database apply process also ends the threaded jobs. If access path maintenance is enabled and the data group is configured for single-threaded database apply processing, the database apply process signals the access path maintenance job and then ends. The access path maintenance job uses additional jobs, if needed, to change the access path maintenance attribute to immediate on all files that MIMIX had previously changed to delayed. Any files that could not be changed are identified as having an access path maintenance error before the maintenance jobs end.

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 ended by each value for End options when source-send technology is used for database replication. The MIMIX database send (DBSND) process and database receive (DBRCV) process are replaced by the IBM i remote journal function and the DBRDR process, respectively.

Table 2. Processes ended by data groups configured for Source Send replication This assumes that all replication processes are active when the ENDDG 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	—	Ends	Ends	Ends	Ends	Ends	Ends	Ends	Ends	Ends	Ends	Ends
*ALLSRC	—	Ends	Ends	Ends	Ends	Active	Ends	Active	Ends	Ends	Active	Active
*ALLTGT	—	Active	Active	Active	Active	Ends	Active	Ends	Active	Active	Ends	Ends
*DBALL	A	Ends	Active²	Active ¹	Active ¹	Active ¹	Ends	Ends	Active ¹	Active ¹	Active ¹	Active ¹
*OBJALL	A	Active³	Ends	Ends	Ends	Ends	Active ²	Active ²	Ends	Ends	Ends	Ends
*DBSRC	A	Ends	Active ¹	Active ¹	Active ¹	Active ¹	Ends	Active	Active ¹	Active ¹	Active ¹	Active ¹
*DBTGT	A	Active	Active ¹	Active ¹	Active ¹	Active ¹	Active	Ends	Active ¹	Active ¹	Active ¹	Active ¹
*OBJSRC	A	Active²	Ends	Ends	Ends	Active	Active ²	Active ²	Ends	Ends	Active	Active
*OBJTGT	A	Active ²	Active	Active	Active	Ends	Active ²	Active ²	Active	Active	Ends	Ends
*DBRDR ⁴	—	—	Active ¹	Active ¹	Active ¹	Active ¹	—	—	Active ¹	Active ¹	Active ¹	Active ¹
*DBAPY	A	Active ²	Active ¹	Active ¹	Active ¹	Active ¹	Active ²	Ends ²	Active ¹	Active ¹	Active ¹	Active ¹
Notes: A. Data groups that use cooperative processing may be affected by the result of this value. Ending database processes while object processes remain active may result in object activity entries being placed on hold. Similarly, ending object processes while database processes remain active may result in files being placed on hold due to error.

Note:

1-If access path maintenance is enabled, the database apply process signals the access path maintenance job and then ends. The access path maintenance job uses additional jobs, if needed, to change the access path maintenance attribute to immediate on all files that MIMIX had previously changed to delayed. Any files that could not be changed are identified as having an access path maintenance error before the maintenance jobs end.

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.