System defined rules
When the default inclusion state is set for SYSBAS or for an IASP, Db2® Mirror adds some system defined rules to the RCL. System defined rules define a set of objects that are always replicated, a set of objects that are never replicated, and some libraries whose contents are not replicated by default. System defined rules cannot be removed. Some system defined rules can be overridden with a user rule for a specific object. System defined RCL rules have a rule source of SYSTEM; user defined RCL rules have a rule source of USER.
To see the system defined rules, click on the gray Show System Rules button in the upper right of the rules table. System rules can be identified by the small padlock icon in the Status column. The figure below shows the system rule that replicates all user profile objects and system rules that exclude all objects in several system supplied libraries.
A closed padlock icon in the Status column is shown for all the system defined object rules. This indicates that no additional rules can be defined to change the replication status for any object governed by this rule. If the padlock icon is open, additional rules can be added to change the replication status. In this example, the closed padlock on the QSYS2 row indicates that there are no replicated objects within the QSYS2 library and no user rule can be added to modify the system rule.

SELECT LIBRARY_NAME, OBJECT_NAME, OBJECT_TYPE, INCLUSION_STATE
FROM QSYS2.REPLICATION_CRITERIA_INFO
WHERE RULE_SOURCE = 'SYSTEM';Some output queues in system libraries are always excluded from replication. You can see the list through the Db2 Mirror GUI by filtering the object type by *OUTQ.
SELECT LIBRARY_NAME, OBJECT_NAME, INCLUSION_STATE
FROM QSYS2.REPLICATION_CRITERIA_INFO
WHERE RULE_SOURCE = 'SYSTEM' AND OBJECT_TYPE = '*OUTQ';