Move/rename operations - user journaled data areas, data queues, IFS objects - 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
2023
First publish date
1999
ft:lastEdition
2024-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

IFS, data area, and data queue objects replicated by user journal replication processes can be moved or renamed while maintaining the integrity of the data. If the new location or new name on the source system remains within the set of objects identified as eligible for replication, MIMIX will perform the move or rename operation on the object on the target system.

When a move or rename operation starts with or results in an object that is not within the name space for user journal replication, MIMIX may need to perform additional operations in order to replicate the operation. MIMIX may use a create or delete operation and may need to add or remove tracking entries.

Each row in Table 27 summarizes a move/rename scenario and identifies the action taken by MIMIX.

Table 1. MIMIX actions when processing moves or renames of objects when user journal replication pro­cesses are involved

Source object

New name or loca­tion

MIMIX action

Identified for replication with user journal processing

Within name space of objects to be replicated with user journal processing

Moves or renames the object on the target system and renames the associated tracking entry. See example 1.

Not identified for replication

Not identified for replication

None. See example 2.

Identified for replication with user journal processing

Not identified for replication

Deletes the target object and deletes the associated tracking entry. The object will no longer be replicated. See example 3.

Identified for replication with user journal processing

Within name space of objects to be replicated with system journal processing

Moves or renames the object using system journal processes and removes the associated tracking entry. See example 4.

Identified for replication with system journal processing

Within name space of objects to be replicated with user journal processing

Creates tracking entry for the object using the new name or location and moves or renames the object using user journal processes. If the object is a library or directory, MIMIX creates tracking entries for those objects within the library or directory that are also within name space for user journal replication and synchronizes those objects. See example 5.

Not identified for replication

Within name space of objects to be replicated with user journal processing

Creates tracking entry for the object using the new name or location. If the object is a library or directory, MIMIX creates tracking entries for those objects within the library or directory that are also within name space for user journal replication. Synchronizes all of the objects identified by these new tracking entries. See example 6.

The following examples use IFS objects and directories to illustrate the MIMIX operations in move/rename scenarios that involve user journal replication (advanced journaling). The MIMIX behavior described is the same as that for data areas and data queues that are within the configured name space for advanced journaling. Table 28 identifies the initial set of source system objects, data group IFS entries, and IFS tracking entries before the move/rename operation occurs.

Table 2. Initial data group IFS entries, IFS tracking entries, and source IFS objects for examples

ConfigurationSupports

Data GroupIFS Entries

Source System IFS Objects in Name Space

Associated Data Group IFS Tracking Entries

user journal replication

/TEST/STMF*

/TEST/stmf1

/TEST/stmf1

user journal replication

/TEST/DIR*

/TEST/dir1/doc1

/TEST/dir1

 

/TEST/dir1/doc1

system journal replication

/TEST/NOTAJ*

/TEST/notajstmf1

 
    /TEST/notajdir1/doc1  

Example 1, moves/renames within advanced journaling name space: The most common move and rename operations occur within advanced journaling name space. For example, MIMIX encounters user journal entries indicating that the source system IFS directory /TEST/dir1 was renamed to /TEST/dir2, and that the IFS stream file /TEST/stmf1 was renamed to /TEST/stmf2. In both cases, the old and new names fall within advanced journaling name space, as indicated in Table 27. The rename operations are replicated and names are changed on the target system objects. The tracking entries for these objects are also renamed. The resulting changes on the target system objects and MIMIX configuration are shown in Table 29.

Table 3. Results of move/rename operations within name space for advanced journaling

Resulting Target IFS objects

Resulting data group IFS tracking entries

/TEST/stmf2

/TEST/stmf2

/TEST/dir2/doc1

/TEST/dir2

 

/TEST/dir2/doc1

Example 2, moves/renames outside name space: When MIMIX encounters a journal entry for a source system object outside of the name space that has been renamed or moved to another location also outside of the name space, MIMIX ignores the transaction. The object is not eligible for replication.

Example 3, moves/renames from advanced journaling name space to outside name space: In this example, MIMIX encounters user journal entries indicating that the source system IFS directory /TEST/dir1 was renamed to /TEST/xdir1 and IFS stream file /TEST/stmf1 was renamed to /TEST/xstmf1. MIMIX is aware of only the original names, as indicated in Table 27. Thus, the old name is eligible for replication, but the new name is not. MIMIX treats this as a delete operation during replication processing. MIMIX deletes the IFS directory and IFS stream file from the target system. MIMIX also deletes the associated IFS tracking entries.

Example 4, moves/renames from advanced journaling to system journal name space: In this example, MIMIX encounters user journal entries indicating that the source system IFS directory /TEST/dir1 was renamed to /TEST/notajdir1 and that IFS stream file /TEST/stmf1 was renamed to /TEST/notajstmf1. MIMIX is aware that both the old names and new names are eligible for replication as indicated in Table 27. However, the new names fall within the name space for replication through the system journal. As a result, MIMIX removes the tracking entries associated with the original names and performs the rename operation for the objects on the target system. Table 30 shows these results.

Table 4. Results of move/rename operations from advanced journaling to system journal name space

Resulting target IFS objects

Resulting data group IFS tracking entries

/TEST/notajstmf1

(removed)

/TEST/notajdir1/doc1

(removed)

Example 5, moves/renames from system journal to advanced journaling name space: In this example, MIMIX encounters journal entries indicating that source system IFS directory from /TEST/notajdir1 was renamed to /TEST/dir1 and that IFS stream file /TEST/notajstmf1 was renamed to /TEST/stmf1. MIMIX is aware that the old names are within the system journal name space and that the new names are within the advanced journaling name space. MIMIX creates tracking entries for the names and then performs the rename operation on the target system using advanced journaling.

MIMIX also creates tracking entries for any objects that reside within the moved or renamed IFS directory (or library in the case of data areas or data queues). The objects identified by these tracking entries are individually synchronized from the source to the target system. Table 31 illustrates the results on the target system.

Table 5. Results of move/rename operations from system journal to advanced journaling name space

Resulting target IFS objects

Resulting data group IFS tracking entries

/TEST/stmf1

/TEST/stmf1

/TEST/dir1/doc1

/TEST/dir1

  /TEST/dir1/doc1

Example 6, moves/renames from outside to within advanced journaling name space: In this example MIMIX encounters journal entries indicating that the source system IFS directory /TEST/xdir1 was renamed to /TEST/dir1 and that IFS stream file /TEST/xstmf1 was renamed to /TEST/stmf1. The original names are outside of the name space and are not eligible for replication. However, the new names are within the name space for advanced journaling as indicated in Table 27. Because the objects were not previously replicated, MIMIX processes the operations as creates during replication. See Newly created objects in a cooperative processing environment.

MIMIX also creates tracking entries for any objects that reside within the moved or renamed IFS directory (or library in the case of data areas or data queues). The objects identified by these tracking entries are individually synchronized from the source to the target system. Table 32 illustrates the results.

Table 6. Results of move/rename operations from outside to within advanced journaling name space

Resulting target IFS objects

Resulting data group IFS tracking entries

/TEST/stmf1

/TEST/stmf1

/TEST/dir1/doc1

/TEST/dir1

 

/TEST/dir1/doc1