Normally, when dealing with objects and database files, you have the ability of seeing the name of the object (filename, library name, and member name) in the journal entries. For IFS objects, it is impractical to put the name of the IFS object in the header of the journal entry due to potentially long path names.
Each IFS object on a system has a unique 16-byte file ID (FID). The FID is used to identify IFS objects in journal entries. The FID is machine-specific, meaning that IFS objects with the same path name may have different FIDs on different systems.
MIMIX tracks the FIDs for all IFS objects and the parent directory of each object configured for replication with advanced journaling via IFS tracking entries. When the data group is switched, the source and target FID associations are reversed, allowing MIMIX to successfully replicate transactions to IFS objects.