MIMIX support of IBM’s high availability performance enhancements has a unique set of restrictions and high availability considerations. Make sure that you are aware of these restrictions before using journal standby state or journal caching in your MIMIX environment.
Journal standby state is not supported in data groups that use multithreaded database apply processing.
When using journal standby state or journal caching, be aware of the following restrictions documented by IBM:
-
Do not use these high availability performance enhancements in conjunction with commitment control. For journals in standby mode, commitment control entries are not sent to or deposited in the journal.
-
Do not use these high availability performance enhancements in conjunction with referential constraints, with the exception of referential constraint types of *RESTRICT.
Also be aware of the following additional restrictions:
-
Do not change journal standby state or journal caching on IBM-supplied journals. These journal names begin with “Q” and reside in libraries which names also begin with “Q” (not QGPL). Attempting to change these journals results in an error message.
-
Do not place a remote journal in journal standby state. Journal caching is also not allowed on remote journals.
-
Do not use MIMIX support of IBM’s high availability performance enhancements in a cascading environment.