What objects need to be journaled - 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

A data group can be configured in a variety of ways that involve a user journal in the replication of files, data areas, data queues and IFS objects. Journaling must be started for any object to be replicated through a user journal or to be replicated by cooperative processing between a user journal and the system journal.

Requirements for system journal replication - System journal replication processes use a special journal, the security audit (QAUDJRN) journal. Events are logged in this journal to create a security audit trail. When data group object entries, IFS entries, and DLO entries are configured, each entry specifies an object auditing value that determines the type of activity on the objects to be logged in the journal. Object auditing is automatically set for all objects defined to a data group when the data group is first started, or any time a change is made to the object entries, IFS entries, or DLO entries for the data group. Because security auditing logs the object changes in the system journal, no special action is need.

Requirements for user journal replication - User journal replication processes require that journaling is started for the objects identified by data group file entries, object tracking entries, and IFS tracking entries. Starting journaling ensures that changes to the objects are recorded in the user journal, and are available for MIMIX to replicate.

During initial configuration, the configuration checklists direct you when to start journaling for objects identified by data group file entries, IFS tracking entries, and object tracking entries. The MIMIX commands STRJRNFE, STRJRNIFSE, and STRJRNOBJE simplify the process of starting journaling. If the journal the objects are currently to is different than the journal defined in the data group definition, these MIMIX commands provide a prompt to change journaling to the configured journal. For more information about these commands, see MIMIX commands for starting journaling.

Although MIMIX commands for starting journaling are preferred, you can also use IBM commands (STRJRNPF, STRJRN, STRJRNOBJ) to start journaling if you have the appropriate authority for starting journaling.

Requirements for user journal replication via a journal-centric configuration - When a data group specifies object types to be replicated by a journal-centric configuration, all objects of the indicated types that are journaled to the user journal of the data group are replicated. If an object is not journaled, it cannot be replicated by a journal-centric data group. To start journaling objects that are object types identified by a journal-centric configuration, you must use the IBM commands (STRJRNPF, STRJRN, STRJRNOBJ).

Requirements for implicit starting of journaling - Journaling can be automatically started for newly created database files, data areas, data queues, or IFS objects when certain requirements are met.

The user ID creating the new objects must have the required authority to start journaling and the following requirements must be met:

  • IFS objects - A new IFS object is automatically journaled if the directory in which it is created is journaled as a result of a request that enabled journaling inheritance for new objects. Typically, if MIMIX started journaling on the parent directory, inheritance is enabled. If you manually start journaling on the parent directory using the IBM command STRJRN, specify INHERIT(*YES) and SUBTREE (*ALL). This will cause IFS objects created within the journaled directory to inherit journal options and the journal state of the parent directory and also cause all objects within the directory's subtree to be journaled.

  • Database files created by SQL statements - A new file created by a CREATE TABLE statement is automatically journaled if the library in which it is created contains a journal named QSQJRN or if the library is journaled with appropriate inherit rules.

  • New *FILE, *DTAARA, *DTAQ objects - The default value (*DFT) for the Journal at creation (JRNATCRT) parameter in the data group definition enables MIMIX to automatically start journaling for physical files, data areas, and data queues when they are created. MIMIX uses the support provided by the IBM i command Start Journal Library (STRJRNLIB). Customers are advised not to re-create the QDFTJRN data area.

When configuration requirements are met, MIMIX will start library journaling for the appropriate libraries as well as enable automatic journaling for the configured cooperatively processed object types. When journal at creation configuration requirements are met, all new objects of that type are journaled, not just those which are eligible for replication.

When the data group is started, MIMIX evaluates all data group object entries for each object type. (Entries for *FILE objects are only evaluated when the data group specifies COOPJRN(*USRJRN).) Entries properly configured to allow cooperative processing of the object type determine whether MIMIX will enforce library journaling. MIMIX uses the data group entry with the most specific match to the object type and library that also specifies *ALL for its System 1 object (OBJ1) and Attribute (OBJATR).

Note: MIMIX prevents library journaling from starting in the following libraries: QSYS*, QRECOVERY, QRCY*, QUSR*, QSPL*, QRPL*, QRCL*, QRPL*, QGPL, QTEMP and SYSIB*.

For example, if MIMIX finds only the following data group object entries for library MYLIB, it would use the first entry when determining whether to enforce library journaling because it is the most specific entry that also meets the OBJ1(*ALL) and OBJATR(*ALL) requirements. The second entry is not considered in the determination because its OBJ1 and OBJATR values do not meet these requirements.

LIB1(MYLIB) OBJ1(*ALL) OBJTYPE(*FILE) OBJATR(*ALL) COOPDB(*YES) PRCTYPE(*INCLD)
LIB1(MYLIB) OBJ1(MYAPP) OBJTYPE(*FILE) OBJATR(DSPF) COOPDB(*YES) PRCTYPE(*INCLD)