Omitting object content from system journal 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
2023
First publish date
1999
ft:lastEdition
2024-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

Shipped default values will result in cooperative processing of *DTAARA, *DTAQ, and *FILE objects identified for replication. When data areas, data queues, logical files, and physical files are configured for replication solely through the system journal (QAUDJRN), you can optionally prevent replication of predetermined sets of T-ZC journal entries associated with changes to object attributes or object content.

Omitting such T-ZC content is useful when an object or file member’s data does not need to be replicated. For example, when replicating work files and temporary files, it may be desirable to replicate the file layout but not the file members or data. Omitting content can also help you reduce the number of transactions that require substantial processing time to replicate, such as T-ZC journal entries with access type 30 (Open).

Default T-ZC processing by system journal replication:.*DTAARA, *DTAQ, and *FILE objects that have an object auditing value of *CHANGE or *ALL will generate T-ZC journal entries in the system journal whenever changes to the object attributes or contents occur. The access type field within the T-ZC journal entry indicates what type of change operation occurred.

When these logical files, physical files, data areas, and data queues are identified for system journal replication, the default behavior of MIMIX is to replicate file or object attributes and object or file member data for all of their generated T-ZC entries.

While MIMIX recreates attribute changes on the target system, member additions and data changes require MIMIX to replicate the entire object using save, send, and restore processes. This can cause unnecessary replication of data and can impact processing time, especially in environments where the replication of data transactions is not necessary.

Omitting T-ZC entries: Through the Omit content (OMTDTA) parameter on data group object entry commands, you can specify one or more values that identify predetermined sets of access types to be omitted from system journal replication. T-ZC journal entries with access types within the specified set for the specified value are omitted from replication processing by MIMIX. The default value for OMTDTA is *NONE, which does not omit any operations from replication.

The T-ZC entries and access types omitted for each possible value are shown in Table 53.

T-ZC entries and access types omitted from system journal replication

Specified OMTDTA Value

Omitted T-ZC Access Types

Operations that Generate T-ZC Access Type

Data area changes (*DTAARA)

Data area changes (*DTAARA)

Operations that change the content (data) or the text description of a *DTAARA object area are omitted from replication.

Note: When this value is specified, MIMIX skips all T-ZC journal entries for data areas selected by the rule. Also MIMIX will not change the object auditing value of those data areas to *CHANGE or *ALL during replication, during a start request, or as the result of the using SETDGAUD command.
7 Change
Note: All T-ZC entries are omitted.

Change data area (CHGDTAARA), Change Object

Description (CHGOBJD

Data queue changes (*DTAQ)

Operations that change the content (data) of a *DTAQ object are omitted from replication. Operations that affect only data queue attributes, such as changing the text description, are replicated.

10

Clear

Clear data queue (via QCLRDTAQ API)

34

Receive

Receive data queue (via QRCVDTAQ API)

51

Send

Send data queue (via QSNDDTAQ API)

Data and member changes (*FILE)

Operations that change the content (data) of a database file (*FILE object) or its members are omitted from replication. For example, operations that add, remove, or rename a member or that open a file for writing, or that clear, initialize, or reorganize data records are omitted. Operations that affect only file attributes, such as changing a file text description, changing the maximum number of members, or adding a constraint, are replicated.
Omitted member data operations: 

10

Clear

Clear member for physical files (CLRPFM)

25

Initialize

Initialize member for physical files (INZPFM)

29

Merge

30

Open

Opening member for write for physical files

36

Reorganize

Reorganize member for physical files (RGZPFM)

Omitted member operations: 
 

1

Add

Add member for physical files and logical files (ADDPFM)

7

Change1 

Change Physical File (CHGPF), Change Logical File (CHGLF), Change Physical File Member (CHGPFM), Change Logical File Member (CHGLFM), Change Object Description (CHGOBJD)

38

Remove

Remove member for physical files and logical files (RMVM)

39

Rename

Rename member for physical files and logical files (RNMM)

Data changes (*MBR) Operations that change the content (data) of a file member are omitted from replication. For example, operations that open, clear, initialize, or reorganize a member are omitted. Operations that affect only member attributes, such as changing a member text description or adding a member, are replicated

10

Clear

Clear member for physical files (CLRPFM)

25

Initialize

Initialize member for physical files (INZPFM)

29

Merge

30

Open

Opening member for write for physical files

36

Reorganize

Reorganize member for physical files (RGZPFM)

1These T-ZC journal entries may or may not have a member name associated with them. If a member name is associated with the journal entry, the T-ZC is a member operation and is omitted when *FILE is specified for OMTDTA. If no member name is associated with the journal entry, the T-ZC is assumed to be a file operation.