The End Data Group (ENDDG) command will end replication processes for the specified data group.
The ENDDG command can be used interactively or programmatically. This command is invoked by the ENDMMX command and by the ENDAG command running the default END procedure, using values other than default for some parameters.
When an ENDDG request is processed, MIMIX may take a few minutes while it does the following for each specified data group:
The value you specify for the Process (PRC) parameter determines which data group replication processes will end. The default value ends all data group replication processes.
When ending data groups that use a shared object send job, the job is ended by the last data group to end.
When ending data groups configured for multithreaded database apply processing, the multithreaded job is ended if the end request specifies to end the database apply process and specifies to end either all apply sessions or apply session B.
When ending data groups that perform access path maintenance, 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.
The specified replication processes end in the manner specified for the End process (ENDOPT) parameter. The command defaults to processing the end request immediately (*IMMED). When invoked by the ENDMMX command, the default value specified on ENDMMX is *CNTRLD, which takes precedence. When invoked by a procedure specified on the ENDAG command, the procedure determines whether ENDDG is passed parameter values or uses the command defaults.
if a controlled end is requested, it uses the specified Wait time and Timeout options.
If requested, the RJ link is ended. The RJ link is not automatically ended. In most cases, the default value *NO for the End remote journaling (ENDRJLNK) parameter is appropriate. Keeping the RJ link active allows database changes to continue to be sent to the target system even though the data group is not active.
The Enable constraints (ENBCST) parameter determines whether the database apply processes will attempt to enable constraints on target system files that were previously disabled by MIMIX. The default value, *DFT, will enable constraints if appropriate configuration conditions exist and the end request specifies all apply sessions and includes database processes that run on the target system.
If you have used the MIMIX CDP feature to set a recovery point in a data group and then end the data group, the recovery point will be cleared. When the data group is started again, the apply processes will process any available transactions, including those which may have had corruptions. (Recovery points are set with the Set DG Recovery Point (SETDGRCYP) command.) If a recovery window is configured for the data group, its configured duration is not affected by requests to end or start the data group.
The ENDDG command does not end the system manager, journal manager, or other processes that run at the node level. To end those processes, either use the ENDMMX command or use the End MIMIX Managers (ENDMMXMGR) command after replication processes have ended.
If a data group is participating in a virtual switch test when you initiate an end data group request, the data group’s apply processes are already ended and are not affected by the request. The apply processes remain ended and will only be started by the virtual switch procedure during its recovery phase.