Move/rename operations - journaled replication - assure_mimix - 10.0

Assure MIMIX Administrator Reference
Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Administrator Reference
Copyright
2024
First publish date
1999
Last updated
2024-10-22
Published on
2024-10-22T10:04:43.803975

Table 26 describes how MIMIX processes a move or rename journal entry. MIMIX uses system journal replication processes for DLOs, IFS objects, and library-based objects which are not explicitly identified for user journal replication. Not all object types are capable of being journaled to a user journal. The Original Source Object and New Name or Location columns indicate whether the object is identified within the name space for replication. The Action column indicates the operation that MIMIX will attempt on the target system.

Table 1. Current object move actions

Original Source Object

New Name or Location

MIMIX Action on Target System

Excluded from or not identified for replication

Within name space of objects to be replicated

Create Object 1 

Identified for replication

Excluded from or not identified for replication

Delete Object 2 

Identified for replication

Within name space of objects to be replicated

Move Object

Excluded from or not identified for replication

Excluded from or not identified for replication

None

  1. If the source system object is not defined to MIMIX or if it is defined by an Exclude entry, it is not guaranteed that an object with the same name exists on the backup system or that it is really the same object as on the source system. To ensure the integrity of the target (backup) system, a copy of the source object must be brought over from the source system.

  2. If the target object is not defined to MIMIX or if it is defined by an Exclude entry, there is no guarantee that the target library exists on the target system. Further, the customer is assumed not to care if the target object is replicated, since it is not defined with an Include entry, so deleting the object on the target is the most straight forward approach.