The system uses journal code B to indicate that the journal entry deposited is related to an IFS operation. Table 170 shows the currently supported IFS entry types that MIMIX can replicate for IFS objects configured for user journal replication.
|
Journal Code |
Type |
Description |
Notes |
|---|---|---|---|
|
B |
AA |
Change audit attributes |
|
|
B |
B1 |
Create files, directories, or symbolic links |
|
|
B |
B3 |
Move/rename object |
|
|
B |
B2 |
Add link |
|
|
B |
B5 |
Remove link (unlink) |
|
|
B |
B6 |
Bytes cleared, after-image |
|
|
B |
B7 |
Apply create object authorities |
|
|
B |
BD |
Delete object |
|
|
B |
ET |
End journaling for object |
|
|
B |
FA |
Change object attribute |
|
|
B |
FR |
Restore object |
1 |
|
B |
FS |
Saved IFS object |
1 |
|
B |
FW |
Start of save-while-active |
1 |
|
B |
JA |
Change journal attributes |
|
|
B |
JT |
Start journaling for object |
|
|
B |
OA |
Change object authority |
|
|
B |
OG |
Change primary group |
|
|
B |
OO |
Change object owner |
|
|
B |
RN |
Rename file identifier |
|
|
B |
TR |
Truncated IFS object |
|
|
B |
WA |
Write after-image |
|
|
Note:
|
|||