MIMIX supports t several ways of enabling constraints on target node files that were previously disabled by MIMIX.
Default shipped procedures for switching application groups automatically enable MIMIX-disabled constraints before performing the requested switch. However, you may need to enable constraints outside the scope of a switch procedure, such as before manually switching a data group with the Switch Data Group command or before performing other operations for which you would want constraints enabled on the target node. Even when target constraint management is not configured, you may need to enable any remaining constraints that failed to be enabled on the target node.
You can manually request MIMIX to enable constraints in these ways:
When ending an application group, the shipped procedures END and ENDTGT include disabled steps MXECSTB and MXECSTR. When enabled, these steps enable constraints previously disabled by MIMIX. To allow these steps to be performed by either procedure, you must take action to enable the steps from within the procedure. Enabling steps must be performed from the native user interface.
When ending replication processes for a specific data group using the Stop Data Group dialog from the Assure Unified Interface or the End Data Group (ENDDG) command from the native user interface. Constraint processing can only occur when the end request specifies all required values and other configuration requirements are met.
For an ended data group. When replication processes have already been ended by a controlled end request and there are no open commit cycles for the data group, you can enable constraints using the ENDDG command in the native user interface or the Enable Constraints action for a data group from the Assure Unified Interface.
When the following conditions exist and these values are specified on an end data group request, MIMIX will enable constraints on the target node files after the specified replication processes end and before the requested command completes:
Process (PRC) must specify processes that run on the target node (*ALL, *ALLTGT, *DBALL, *DBTGT, or *DBAPY)
Configuration requirements for the specified End process (ENDOPT) must be met.
-
When specifying *IMMED for an immediate end, or when specifying *CNTRLD for a controlled end and a wait time (WAIT) value of *SBMRQS, database apply processes must have already been ended by a previous controlled end request.
-
When specifying *CNTRLD for a controlled end and a number for wait time (WAIT), the data group must be configured for target constraint management and its replication processes must end within the specified wait time and have no open commit cycles.
-
Apply sessions (APYSSN) must specify *ALL.
Enable constraints (ENBCST) must specify or resolve to *YES. The shipped default value, *DFT, resolves to *YES when all other conditions are met.
If the requirements are not met, the constraints are not enabled and no error message is issued.
MIMIX-disabled constraints that failed to be enabled may still exist on the target node after the end data group request completes or after the configuration is changed to no longer allow target constraint management.
When target constraint management is configured, specifying the value *NO for ENBCST allows any MIMIX-disabled constraints to remain disabled, improving performance of this end operation and the next start operation.