System values
Some system values must be the same on both the source and the target nodes in order for replication to function properly in a Db2® Mirror environment. Other system values are specific to a partition and will never be replicated.
The RCL is primed with a system defined rule to include all system values in replication by default. There are additional system defined rules to include or exclude specific system values; these rules cannot be changed or removed. A user rule to exclude a system value can be defined for any system value that is not explicitly included by a system rule.
To view the system defined rules look in the RCL. See System defined rules for details.
System values that are always replicated
Some system values are always replicated. For example, date and time system values, and certain security and language related system values must be the same on both nodes.
The following system values are always replicated. Each of these system values has a system defined rule set to include.
|
QALWOBJRST QCCSID QCENTURY QCHRID QCHRIDCTL QCNTRYID QCRTAUT QCRTOBJAUD |
QCURSYM QDATE QDATETIME QDATFMT QDATSEP QDAY QDECFMT QFRCCVNRST |
QHOUR QIGCCDEFNT QIGCFNTSIZ QKBDTYPE QLANGID QMINUTE QMONTH QPWDLVL |
QSECOND QSECURITY QSRTSEQ QTIME QTIMSEP QTIMZON QVFYOBJRST QYEAR |
System values that are never replicated
Some system values will never be replicated because they are specific to the node, they are read only, or they are obsolete. The following system values are not eligible for replication. Each of these system values has a system defined rule set to exclude.
|
QABNORMSW QADLSPLA QALWJOBITP QAUTOSPRPT QBASACTLVL QBASPOOL QBOOKPATH QCMNARB |
QCONSOLE QDAYOFWEEK QDBFSTCCOL QDYNPTYADJ QDYNPTYSCD QIGC QIPLDATTIM QIPLSTS |
QIPLTYPE QJOBMSGQSZ QJOBMSGQTL QJOBSPLA QLEAPADJ QMAXACTLVL QMCHPOOL QMODEL |
QPRCFEAT QPWRRSTIPL QRMTIPL QSRLNBR QSTRPRTWTR QSVRAUTITV QTIMADJ QUTCOFFSET |
System values that can be excluded from replication
Any system value not listed in #db2mobjsysval__sysrules_include or #db2mobjsysval__sysrules_exclude is replicated by default. This set of system values can have a user rule defined to exclude that system value from replication. You need to define a user rule for each system value that you want to exclude.
When changing a system value that references other objects such as programs or libraries, you must either ensure that those objects exist on both nodes before making the change or exclude the system value from replication. QSYSLIBL, QUSRLIBL, QATNPGM, QALWUSRDMN, QCTLSBSD, QSTRUPPGM, QCFGMSGQ, and QUPSMSGQ are examples of system values that include the name of an object. If the object is not found on the target node, the system value will be changed on the source node only, and an error entry will be added to the Object Tracking List (OTL), requiring manual intervention to resolve the conflict.
Removing user rules for system values
If you want to remove a user defined exclusion rule for a system value, you might need to manually change the system value on one of the nodes first so the value is same on both nodes. When the values are the same, you can remove the exclusion entry. This extra step is needed because once the user defined exclusion rule is removed, the default rule to include all system values will apply to this system value. The default rule requires the values to match.
When removing a user defined rule for a system value using the Db2 Mirror GUI, use the filter columns to find the system value rule, then click on the trash can icon in the Action column to delete the active rule. System defined rules have a padlock icon next to them in the Status column and cannot be removed.
System value lock down
Certain security related system values are not allowed to be changed if an option in Start Service Tools (STRSST) has been used to prevent them from being changed. If you attempt to change a system value that has been locked using this function, the change will not be allowed. See Lock function of security-related system values for more information on which system values can be locked.
If you plan to make a change through SST to lock down a replicated system value, you should lock down the system value on both the source and target nodes. Otherwise, changes made to the system value on the node that is not locked down will fail replication to the target node, since it is locked from all changes.