Your production environment is dynamic. New objects continue to be created after MIMIX is configured and running. When properly configured, MIMIX automatically recognizes entries in the user journal that identify new create operations and replicates any that are eligible for replication. Optionally, MIMIX can also notify you of newly created objects not eligible for replication so that you can choose whether to add them to the configuration.
Configurations that replicate files, data areas, data queues, or IFS objects from user journal entries require journaling to be started on the objects before replication can occur. When a configuration enables journaling to be implicitly started on new objects, a newly created object is already journaled. When the journaled object falls within the group of objects identified for replication by a data group, MIMIX replicates the create operation. Processing variations exist based on how the data group and the data group entry with the most specific match to the object are configured. These variations are described in the following subtopics.
The MMNFYNEWE monitor is a shipped journal monitor that watches the security audit journal (QAUDJRN) for newly created libraries, folders, or directories that are not already included or excluded for replication by a data group and sends warning notifications when its conditions are met. This monitor is shipped disabled. User action is required to enable this monitor on the source system within your MIMIX environment. Once enabled, the monitor will automatically start with the master monitor. For more information about the conditions that are checked, see topic ‘Notifications for newly created objects’ in the Assure MIMIX Operations book.
For more information about requirements and restrictions for implicit starting of journaling as well as examples of how MIMIX determines whether to replicate a new object, see What objects need to be journaled.