The operating system uses journal codes E and Q to indicate that journal entries are related to operations on data areas and data queues, respectively. When configured for user journal replication, MIMIX recognizes specific E and Q journal entry types as eligible for replication from a user journal.
Table 171 shows the currently supported journal entry types for data areas.
Journal Code |
Type |
Description |
---|---|---|
E |
EA |
Update data area, after image |
E |
EB |
Update data area, before image |
E |
ED |
Data area deleted |
E |
EE |
Create data area |
E |
EG |
Start journal for data area |
E |
EH |
End journal for data area |
E |
EK |
Change journaled object attribute |
E |
EL |
Data area restored |
E |
EM |
Data area moved |
E |
EN |
Data area renamed |
E |
ES |
Data area saved |
E |
EW |
Start of save for data area |
E |
ZA |
Change authority |
E |
ZB |
Change object attribute |
E |
ZO |
Ownership change |
E |
ZP |
Change primary group |
E |
ZT |
Auditing change |
Table 172 shows the currently supported journal entry types for data queues.
Journal Code |
Type |
Description |
---|---|---|
Q |
QA |
Create data queue |
Q |
QB |
Start data queue journaling |
Q |
QC |
Data queue cleared, no key |
Q |
QD |
Data queue deleted |
Q |
QE |
End data queue journaling |
Q |
QG |
Data queue attribute changed |
Q |
QJ |
Data queue cleared, has key |
Q |
QK |
Send data queue entry, has key |
Q |
QL |
Receive data queue entry, has key |
Q |
QM |
Data queue moved |
Q |
QN |
Data queue renamed |
Q |
QR |
Receive data queue entry, no key |
Q |
QS |
Send data queue entry, no key |
Q |
QX |
Start of save for data queue |
Q |
QY |
Data queue saved |
Q |
QZ |
Data queue restored |
Q |
ZA |
Change authority |
Q |
ZB |
Change object attribute |
Q |
ZO |
Ownership change |
Q |
ZP |
Change primary group |
Q |
ZT |
Auditing change |
For more information about journal entries, see Journal Entry Information (Appendix D) in the iSeries Backup and Recovery guide in the IBM eServer iSeries Information Center.