Replication and auditing details for journal-centric configurations - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
ft:locale
en-US
Product name
Assure MIMIX
ft:title
Assure MIMIX Administrator Reference
Copyright
2025
First publish date
1999
ft:lastEdition
2026-03-10
ft:lastPublication
2026-03-10T14:48:05.710000
L1_Product_Gateway
Integrate
L2_Product_Segment
IBM Infrastructure
L3_Product_Brand
Precisely Assure
L4_Investment_Segment
IBM i HA
L5_Product_Group
IBM i HA
L6_Product_Name
Assure MIMIX

For library objects replicated by a journal-centric data group, the inherit rules for journaling as specified in the INHRULES parameter on the STRJRNLIB command are replicated. Audits of the journal-centric data group compare these journaling attributes of the library as part of the Type Specific Indicator (*TYPSPFIND) attribute.

When journal-capable objects that are identified for journal-centric replication are compared by Compare commands or by audits, these journaling attributes are included in the compared attributes: *JOURNALED, *JRN, *JRNLIB, *JRNIMG and *JRNOMIT.

The value Not journal-centric (*NOTJRNCTR) can be reported in the Source or Target Indicator columns of audit details of audit results for the Libraries (#OBJATR), Directories (#IFSATR), and File attributes (#FILATR) audits. This value indicates that the object was not included in the compare phase because it is replicated by a journal-centric configuration and the object was either not found or is not journaled on one of the systems in the data group. This can also indicate that the object is not journaled on the source system of a journal-centric data group and a selection rule exists that specifies an object type of *STRJRN to start journaling of journal-capable objects.