All journal entries by code and type
| Journal code | Entry type | Description | Notes |
|---|---|---|---|
| A | DP | Direct print information | See Work Management for the layout of the entry specific data. |
| A | JB | Job resource information | See Work Management for the layout of the entry specific data. |
| A | SP | Spooled print information | See Work Management for the layout of the entry specific data. |
| B | AA | Change audit attribute | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system change audit attribute (B AA) journal entry . |
| B | AJ | Start of apply | |
| B | AT | End of apply | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the APYJRNCHG (B AT, D DD, E EQ, F AY, Q QH, Y YH) and RMVJRNCHG (E EX, F RC) journal entries. |
| B | BD | Integrated file system object deleted | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system object deleted (B BD) journal entry . |
| B | B0 | Begin create | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system begin create (B B0) journal entry. |
| B | B1 | Create summary | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system create-summary (B B1) journal entry . |
| B | B2 | Link to existing object | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system link to existing object (B B2) journal entry. |
| B | B3 | Rename, move object | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system rename, move object (B B3) journal entry. |
| B | B4 | Remove link (parent directory) | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system remove link (parent directory) (B B4) journal entry. |
| B | B5 | Remove link (link) | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system remove link (link) (B B5) journal entry. |
| B | B6 | Bytes cleared, after-image | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system bytes cleared, after-image (B B6) journal entry. |
| B | B7 | Created object authority information. | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. This journal entry may have data which can only be accessed by using either the QjoRetrieveJournalEntries API or the RCVJRNE command. For the RCVJRNE command, use the ENTFMT(*TYPEPTR) or ENTFMT(*JRNENTFMT) parameters. In all other interfaces, if the data is not visible, the incomplete data indicator will be on and *POINTER will appear in the Entry Specific Data. For more information, refer to Working with pointers in journal entries See the layout for the Integrated file system created object authority (B B7) journal entry. |
| B | CS | Integrated file system object closed | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system object closed (B CS) journal entry. |
| B | ET | End journaling for object | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system end journaling for object (B ET) journal entry. |
| B | FA | Integrated file system object attribute changed | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system object attribute changed (B FA) journal entry. |
| B | FC | Integrated file system object forced | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system object forced (B FC) journal entry. |
| B | FF | Storage for object freed | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system storage for object freed (B FF) journal entry. |
| B | FR | Integrated file system object restored | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Object restored (B FR, D DZ, E EL, F MR, J RR, Q QZ, Y YZ) and receiver saved (J RS) journal entries. |
| B | FS | Integrated file system object saved | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Object saved (B FS, D DH, E ES, F MS, Q QY, Y YS) journal entries. |
| B | FW | Start of save for save-while-active | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Start of save-while-active (B FW, D DW, E EW, F SS, Q QX, Y YW) journal entries. |
| B | JA | Change journaled object attribute | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H.
|
| B | JT | Start journaling for object | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Start journal (B JT, D JF, E EG, F JM, Q QB) journal entries. |
| B | OA | Change object authority | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system change object authority (B OA) journal entry. |
| B | OF | Integrated file system object opened | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system object opened (B OF) journal entries. |
| B | OG | Change primary group | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system change primary group (B OG) journal entry. |
| B | OI | Object in use at abnormal end | See the layout for the IPL (J IA, J IN) and in-use (B OI, C BA, D ID, E EI, F IU, I DA, J JI, Q QI) journal entries. |
| B | OO | Change object owner | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system change object owner (B OO) journal entry. |
| B | RN | Rename file identifier | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system rename file identifier (B RN) journal entry. |
| B | TR | Integrated file system object truncated | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Integrated file system object truncated (B TR) journal entry. |
| B | WA | Write, after-image | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. This journal entry may have data which can only be accessed by using either the QjoRetrieveJournalEntries API or the RCVJRNE command. For the RCVJRNE command, use the ENTFMT(*TYPEPTR) or ENTFMT(*JRNENTFMT) parameters. In all other interfaces, if the data is not visible, the incomplete data indicator will be on and *POINTER will appear in the Entry Specific Data. For more information, refer to Working with pointers in journal entries See the layout for the Integrated file system write, after-image (B WA) journal entry. |
| C | BA | Commit in use at abnormal end | See the layout for the IPL (J IA, J IN) and in-use (B OI, C BA, D ID, E EI, F IU, I DA, J JI, Q QI) journal entries . |
| C | BC | Start commitment control (STRCMTCTL) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| C | CM | Set of record changes committed (COMMIT) | See the layout for the COMMIT (C CM) journal entry . |
| C | CN | Rollback ended early | See the layout for the Rollback ended early (C CN, F C1) journal entries. |
| C | DB | Internal entry | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| C | EC | End commitment control (ENDCMTCTL) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| C | LW | A logical unit of work (LUW) has ended | See the layout for the Logical unit of work (C LW) journal entry and the
following:
|
| C | PC | Prepare commit block | See the layout for the |
| C | RB | Set of record changes rolled back (ROLLBACK) | See the layout for the ROLLBACK (C RB) journal entry. |
| C | R1 | Rollback started | |
| C | SB | Start of savepoint | This is the start of the savepoint or nested commit cycle where it is written to the journal and occurs when the application creates an SQL SAVEPOINT. The system can also create an internal nested commit cycle to handle a series of database functions as a single operation. The entry-specific data for this journal entry is all internal data. |
| C | SC | Commit transaction started | |
| C | SQ | Release of savepoint | This is the release of the savepoint or commit of nested
commit cycle. Entries are written to the journal when the application
releases an SQL SAVEPOINT or when the system commits an internal nested
commit cycle. See the layout for the Savepoint released (C SQ) and savepoint rolled back (C SU) journal entries. |
| C | SU | Rollback of save point | This is the release of the savepoint or commit of nested
commit cycle. Entries are written to the journal when the application
releases an SQL SAVEPOINT or when the system commits an internal nested
commit cycle. See the layout for the Savepoint released (C SQ) and savepoint rolled back (C SU) journal entries. |
| D | AC | Add referential integrity constraint | See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| D | CG | Change file | See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| D | CT | Create database file | See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| D | DC | Remove referential integrity constraint | See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| D | DD | End of apply or remove | See the layout for the APYJRNCHG (B AT, D DD, E EQ, F AY, Q QH, Y YH) and RMVJRNCHG (E EX, F RC) journal entries. |
| D | DF | File was deleted | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| D | DG | Start of apply or remove | |
| D | DH | File saved | These entries do not indicate that they occurred as the result
of a trigger program, even if a trigger program caused the event.
That information is not available at the time the entry is written
to the journal. See the layout for the Object saved (B FS, D DH, E ES, F MS, Q QY, Y YS) journal entries. |
| D | DJ | Change journaled object attribute |
|
| D | DT | Delete file | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| D | DW | Start of save-while-active save | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. See the layout for the Start of save-while-active (B FW, D DW, E EW, F SS, Q QX, Y YW) journal entries. |
| D | DZ | File restored | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. See the layout for the Object restored (B FR, D DZ, E EL, F MR, J RR, Q QZ, Y YZ) and receiver saved (J RS) journal entries. |
| D | EF | Journaling for a physical file ended (ENDJRNPF) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| D | FM | File moved to a different library (MOVOBJ or RNMOBJ OBJTYPE(*LIB)) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. See the layout for the Moving and renaming objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, J MJ, Q QM, Q QN) journal entries. |
| D | FN | File renamed (RNMOBJ) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. See the layout for the Moving and renaming objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, J MJ, Q QM, Q QN) journal entries. |
| D | GC | Change constraint | See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| D | GO | Change owner | See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| D | GT | Grant authority | See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| D | ID | File in use | See the layout for the IPL (J IA, J IN) and in-use (B OI, C BA, D ID, E EI, F IU, I DA, J JI, Q QI) journal entries. |
| D | JF | Journaling for a physical file started (STRJRNPF (JRNPF)) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. See the layout for the Start journal (B JT, D JF, E EG, F JM, Q QB) journal entries. |
| D | LF | Logical file associated with based on physical file | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the Logical file associated with the library or based on physical file (D LF, Y LF) journal entry. |
| D | MA | Member added to file | |
| D | RV | Revoke authority | See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| D | TC | Add trigger | See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| D | TD | Remove trigger | See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| D | TG | Change trigger | See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| D | TQ | Refresh table | See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| D | ZB | Change object attribute | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the Change object attribute (E ZB, D ZB, J ZB, Q ZB, Y ZB) journal entry. |
| E | EA | Update data area, after image | Neither the before-image nor after-image is deposited into the journal if the after-image is exactly the same as the before-image. This entry may have minimized entry specific data (ESD). It will have minimized ESD if its corresponding object type deposits minimized journal entries through the MINENTDTA parameter for this journal or journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Update data area (E EA, E EB) journal entries. |
| E | EB | Update data area, before image | Neither the before-image nor after-image is deposited into the journal if the after-image is exactly the same as the before-image. This entry may have minimized entry specific data (ESD). It will have minimized ESD if its corresponding object type deposits minimized journal entries through the MINENTDTA parameter for this journal or journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Update data area (E EA, E EB) journal entries. |
| E | ED | Data area deleted | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| E | EE | Create data area | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Create data area (E EE) journal entry. |
| E | EG | Start journal for data area | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. See the layout for the Start journal (B JT, D JF, E EG, F JM, Q QB) journal entries. |
| E | EH | End journal for data area | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| E | EI | Data area in use | |
| E | EK | Change journaled object attribute |
See the layout for the Change journaled object attributes (B JA, D DJ, E EK, F JC, Q QF, Y YK) journal entries. |
| E | EL | Data area restored | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Object restored (B FR, D DZ, E EL, F MR, J RR, Q QZ, Y YZ) and receiver saved (J RS) journal entries. |
| E | EM | Data area moved | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Moving and renaming objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, J MJ, Q QM, Q QN) journal entries. |
| E | EN | Data area renamed | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Moving and renaming objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, J MJ, Q QM, Q QN) journal entries. |
| E | EQ | Data area changes applied | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the APYJRNCHG (B AT, D DD, E EQ, F AY, Q QH, Y YH) and RMVJRNCHG (E EX, F RC) journal entries. |
| E | ES | Data area saved | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Object saved (B FS, D DH, E ES, F MS, Q QY, Y YS) journal entries. |
| E | EU | Remove journaled changes (RMVJRNCHG) command started | |
| E | EW | Start of save for data area | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Start of save-while-active (B FW, D DW, E EW, F SS, Q QX, Y YW) journal entries. |
| E | EX | Data area changes removed | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the APYJRNCHG (B AT, D DD, E EQ, F AY, Q QH, Y YH) and RMVJRNCHG (E EX, F RC) journal entries. |
| E | EY | Apply journaled changes (APYJRNCHG) command started | |
| E | ZA | Change authority | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Change authority (E ZA, J ZA, Q ZA, Y ZA) journal entry. |
| E | ZB | Change object attribute | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Change object attribute (E ZB, D ZB, J ZB, Q ZB, Y ZB) journal entry. |
| E | ZO | Ownership change | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Ownership change (E ZO, J ZO, Q ZO, Y ZO) journal entries. |
| E | ZP | Change primary group | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Change primary group (E ZP, J ZP, Q ZP, Y ZP) journal entry. |
| E | ZT | Auditing change | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Auditing Change (E ZT, J ZT, Q ZT, Y ZT) journal entries. |
| F | AY | Journaled changes applied to a physical file member (APYJRNCHG) | See the layout for the APYJRNCHG (B AT, D DD, E EQ, F AY, Q QH, Y YH) and RMVJRNCHG (E EX, F RC) journal entries. |
| F | CB | Physical file member changed | |
| F | CE | Change end of data for physical file member | See the layout for the Change end of data (F CE) journal entry. |
| F | CH | Change file | As of V5R1M0, the journal entry D CG is also being sent for the change file operations. IBM® strongly recommends that you do your processing based on the D CG entry instead of the F CH entry because the F CH entry may be retired in a future release. |
| F | CL | Physical file member closed (for shared files, a close entry is made for the last close operation of the file) | See the layout for the Database file OPEN (F OP) and database file CLOSE (F CL) journal entries. |
| F | CR | Physical file member cleared (CLRPFM) | |
| F | C1 | Rollback ended early | See the layout for the Rollback ended early (C CN, F C1) journal entries. |
| F | DE | Physical file member deleted record count | |
| F | DM | Delete member | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| F | EJ | Journaling for a physical file member ended (ENDJRNPF) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| F | EP | Journaling access path for a database file member ended (ENDJRNAP) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| F | FD | Physical file member forced (written) to auxiliary storage | See the layout for the Force data to auxiliary storage (F FD) journal entry. |
| F | FI | System-generated journal entry format information | |
| F | IT | Identity value | See the layout for the Identity Value (F IT) journal entries. |
| F | IU | Physical file member in use at the time of abnormal system end | See the layout for the IPL (J IA, J IN) and in-use (B OI, C BA, D ID, E EI, F IU, I DA, J JI, Q QI) journal entries. |
| F | IZ | Physical file member initialized (INZPFM) | This journal entry may have data which can only be accessed
by using either the QjoRetrieveJournalEntries API or the RCVJRNE command.
For the RCVJRNE command, use the ENTFMT(*TYPEPTR) or ENTFMT(*JRNENTFMT)
parameters. In all other interfaces, if the data is not visible, the
incomplete data indicator will be on and *POINTER will appear in the
Entry Specific Data. For more information, refer to Working with pointers in journal entries. See the layout for the INZPFM (F IZ) journal entry. |
| F | JC | Change journaled object attribute |
|
| F | JM | Journaling for a physical file member started (STRJRNPF) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. See the layout for the Start journal (B JT, D JF, E EG, F JM, Q QB) journal entries. |
| F | JP | Journaling access path for a database file member started (STRJRNAP) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| F | MC | Create member | See the layout for the Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries. |
| F | MD | Physical file member deleted. This entry is created when you remove the member (RMVM) or delete the file (DLTF) containing the member. | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| F | MF | Physical file member saved with storage freed (SAVOBJ, SAVCHGOBJ, or SAVLIB) | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. |
| F | MM | Physical file containing the member moved to a different library (MOVOBJ or RNMOBJ OBJTYPE(*LIB)) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. See the layout for the Moving and renaming objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, J MJ, Q QM, Q QN) journal entries. |
| F | MN | Physical file containing the member renamed (RNMM or RNMOBJ) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. See the layout for the Moving and renaming objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, J MJ, Q QM, Q QN) journal entries. |
| F | MO | Allow use with partial transactions | See the layout for the Allow use with partial transactions (F MO) journal entry. |
| F | MR | Physical file member restored (RSTOBJ or RSTLIB) | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. See the layout for the Object restored (B FR, D DZ, E EL, F MR, J RR, Q QZ, Y YZ) and receiver saved (J RS) journal entries. |
| F | MS | Physical file member saved (SAVOBJ, SAVLIB, or SAVCHGOBJ) | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. See the layout for the Object saved (B FS, D DH, E ES, F MS, Q QY, Y YS) journal entries. |
| F | OP | Physical file member opened (for shared files, an open entry is added for the first open operation for the file) | See the layout for the Database file OPEN (F OP) and database file CLOSE (F CL) journal entries. |
| F | PD | Database file member's access path deleted (this entry is created when you remove the member (RMVM) or delete the file (DLTF) containing the member) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The object name for this entry might be misleading. It is the original name the path had when journaling started. The name is not updated if the access path is moved, renamed, or if it is implicitly shared by another logical file. See the layout for the Delete access path (F PD) journal entry. |
| F | PM | The logical owner of a journaled access path was moved (MOVOBJ or RNMOBJ OBJTYPE(*LIB)) | After you have installed V4R2M0 or a later release, this
journal type is no longer generated. See the layout for the Moving and renaming objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, J MJ, Q QM, Q QN) journal entries. |
| F | PN | The logical owner of a journaled access path was renamed (RNMOBJ or RNMM) | After you have installed V4R2M0 or a later release, this
journal type is no longer generated. See the layout for the Moving and renaming objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, J MJ, Q QM, Q QN) journal entries. |
| F | RC | Journaled changes removed from a physical file member (RMVJRNCHG) | See the layout for the APYJRNCHG (B AT, D DD, E EQ, F AY, Q QH, Y YH) and RMVJRNCHG (E EX, F RC) journal entries. |
| F | RG | Physical file member reorganized (RGZPFM) | See the layout for the RGZPFM (F RG) journal entry. |
| F | RM | Member reorganized | |
| F | SA | The point at which the APYJRNCHG command started running | |
| F | SR | The point at which the RMVJRNCHG command started running | |
| F | SS | The start of the save of a physical file member using the save-while-active function | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. See the layout for the Start of save-while-active (B FW, D DW, E EW, F SS, Q QX, Y YW) journal entries. |
| I | DA | Directory in use at abnormal end | See the layout for the IPL (J IA, J IN) and in-use (B OI, C BA, D ID, E EI, F IU, I DA, J JI, Q QI) journal entries. |
| I | DK | Internal entry | |
| I | IB | Internal recovery | |
| I | IC | Access path protection | |
| I | IE | Directory recovery | |
| I | IF | Access path protection | |
| I | IG | Access path restored | |
| I | IH | Access path protection | |
| I | II | Access path in use at abnormal end | |
 I |
IK |
Access path protection |
|
| I | IO | Access path protection | |
| I | IQ | Access path protection | |
| I | IV | Access path protection | |
| I | IW | Access path protection | |
| I | IX | Start of save for access path | |
| I | IY | Access path saved | |
| I | UE | Unknown entry type | |
| J | CI | Journal caching started | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| J | CX | Journal caching ended | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| J | EZ | End journaling for journal receiver | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| J | IA | System IPL after abnormal end | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| J | IN | System IPL after normal end | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| J | JI | Journal receiver in use at abnormal end | See the layout for the IPL (J IA, J IN) and in-use (B OI, C BA, D ID, E EI, F IU, I DA, J JI, Q QI) journal entries. |
| J | JR | Start journaling for journal receiver | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| J | KR | Keep journal receivers for recovery | |
| J | LA | Activate local journal | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| J | LI | Inactivate local journal | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| J | MJ | Journal receiver moved | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QWCJRNL.H. See the layout for the Moving and renaming objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, J MJ, Q QM, Q QN) journal entries. |
| J | NK | Do not keep journal receivers for recovery | |
| J | NR | Identifier for the next journal receiver (the receiver that was attached when the indicated receiver was detached) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. See the layout for the CHGJRN (J NR, J PR) journal entries. |
| J | PR | Identifier for the previous journal receiver (the receiver that was detached when the indicated receiver was attached) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. See the layout for the CHGJRN (J NR, J PR) journal entries. |
| J | RD | Deletion of a journal receiver (DLTJRNRCV) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. See the layout for the Delete receiver (J RD, J RF) journal entries. |
| J | RF | Storage for a journal receiver freed (SAVOBJ, SAVCHGOBJ, or SAVLIB) | See the layout for the Delete receiver (J RD, J RF) journal entries. |
| J | RR | Restore operation for a journal receiver (RSTOBJ or RSTLIB) | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. See the layout for the Object restored (B FR, D DZ, E EL, F MR, J RR, Q QZ, Y YZ) and receiver saved (J RS) journal entries. |
| J | RS | Save operation for a journal receiver (SAVOBJ, SAVCHGOBJ, or SAVLIB) | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. See the layout for the Object restored (B FR, D DZ, E EL, F MR, J RR, Q QZ, Y YZ) and receiver saved (J RS) journal entries. |
| J | SI | Enter journal state (*STANDBY) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| J | SL | Severed link | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. This is the start of the savepoint or nested commit cycle where it is written to the journal and occurs when the application creates an SQL SAVEPOINT. The system can also create an internal nested commit cycle to handle a series of database functions as a single operation. The entry-specific data for this journal entry is all internal data. |
| J | SX | Exit journal state (*STANDBY) | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| J | UA | User independent auxiliary storage pool vary on abnormal | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| J | UN | User independent auxiliary storage pool vary on normal | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| J | XP | Internal entry | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
| J | ZA | Change authority for journal receiver | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QSYJRNL.H. See the layout for the Change authority (E ZA, J ZA, Q ZA, Y ZA) journal entry. |
| J | ZB | Change attribute for journal receiver | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QSYJRNL.H. See the layout for the Change object attribute (E ZB, D ZB, J ZB, Q ZB, Y ZB) journal entry. |
| J | ZO | Change owner for journal receiver | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QSYJRNL.H. See the layout for the Ownership change (E ZO, J ZO, Q ZO, Y ZO) journal entries. |
| J | ZP | Change primary group for journal receiver | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QSYJRNL.H. See the layout for the Change primary group (E ZP, J ZP, Q ZP, Y ZP) journal entry. |
| J | ZT | Change audit attribute for journal receiver | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QSYJRNL.H. See the layout for the Auditing Change (E ZT, J ZT, Q ZT, Y ZT) journal entries. |
| L | LK | License key is not valid | See the layout for the License key not valid (L LK) journal entry. |
| L | LL | Usage limit changed | See the layout for the Usage limit changed (L LL) journal entry. |
| L | LU | Usage limit exceeded | See the layout for the Usage limit exceeded (L LU) journal entry. |
| M | MP | Modification of QoS policies | |
| M | SN | Simple Network Management Protocol (SNMP) information | See Simple
Network Management Protocol (SNMP) Support  for
information about the entry specific data for SNMP journal entries. |
| M | TF | IP filter rules actions | See the layout for the IP Packet Filter (M TF) journal entry. |
| M | TN | IP NAT rules actions | See the layout for the IP NAT rules actions (M TN) journal entry. |
| M | TS | Virtual private networking (VPN) information | |
| P | TP | Performance shared pool change | See Work Management for the layout of the entry specific data. |
| Q | QA | Create data queue | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QMHQJRNL.H. See the layout for the Create data queue (Q QA) journal entry. |
| Q | QB | Start data queue journaling | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QMHQJRNL.H. See the layout for the Start journal (B JT, D JF, E EG, F JM, Q QB) journal entries. |
| Q | QC | Data queue cleared, no key | See the layout for the Database file OPEN (F OP) and database file CLOSE (F CL) journal entries. |
| Q | QD | Data queue deleted | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. There is no entry-specific data for this entry. |
| Q | QE | End data queue journaling | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. There is no entry-specific data for this entry. |
| Q |
QF |
Change journal object attribute |
|
| Q | QG | Data queue attributes changed | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QMHQJRNL.H. See the layout for the Data queue attributes changed (Q QG) journal entry. |
| Q | QH | Data queue changes applied | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QMHQJRNL.H. See the layout for the APYJRNCHG (B AT, D DD, E EQ, F AY, Q QH, Y YH) and RMVJRNCHG (E EX, F RC) journal entries. |
| Q | QI | Queue in use at abnormal end | There is no entry-specific data for this entry. |
| Q | QJ | Data queue cleared, has key | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QMHQJRNL.H. See the layout for the Data queue cleared, has key (Q QJ) journal entry. |
| Q | QK | Send data queue entry, has key | This journal entry may have data which can only be accessed
by using either the QjoRetrieveJournalEntries API or the RCVJRNE command.
For the RCVJRNE command, use the ENTFMT(*TYPEPTR) or ENTFMT(*JRNENTFMT)
parameters. In all other interfaces, if the data is not visible, the
incomplete data indicator will be on and *POINTER will appear in the
Entry Specific Data. For more information, refer to Working with pointers in journal entries. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QMHQJRNL.H. See the layout for the Send data queue, has key (Q QK) journal entry. |
| Q | QL | Receive data queue entry, has key | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QMHQJRNL.H. See the layout for the Received data queue, has key (Q QL) journal entry. |
| Q | QM | Data queue moved | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QMHQJRNL.H. See the layout for the Moving and renaming objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, J MJ, Q QM, Q QN) journal entries. |
| Q | QN | Data queue renamed | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QMHQJRNL.H. See the layout for the Moving and renaming objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, J MJ, Q QM, Q QN) journal entries. |
| Q | QR | Receive data queue entry, no key | This entry only has entry-specific data which the system uses for internal processing. There is no structure for it in the QSYSINC include file, QMHQJRNL.H. |
| Q | QS | Send data queue entry, no key | This journal entry may have data which can only be accessed
by using either the QjoRetrieveJournalEntries API or the RCVJRNE command.
For the RCVJRNE command, use the ENTFMT(*TYPEPTR) or ENTFMT(*JRNENTFMT)
parameters. In all other interfaces, if the data is not visible, the
incomplete data indicator will be on and *POINTER will appear in the
Entry Specific Data. For more information, refer to Working with pointers in journal entries. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QMHQJRNL.H. See the layout for the Send data queue, no key (Q QS) journal entry. |
| Q | QW | Apply journaled changes (APYJRNCHG) command started | The entry specific data for this entry varies, and only represents data required internally by the operation system. Therefore, the entry layout is not documented. |
| Q | QX | Start of save for data queue | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QMHQJRNL.H. See the layout for the Start of save-while-active (B FW, D DW, E EW, F SS, Q QX, Y YW) journal entries. |
| Q | QY | Data queue saved | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QMHQJRNL.H. See the layout for the Object saved (B FS, D DH, E ES, F MS, Q QY, Y YS) journal entries. |
| Q | QZ | Data queue restored | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QMHQJRNL.H. See the layout for the Object restored (B FR, D DZ, E EL, F MR, J RR, Q QZ, Y YZ) and receiver saved (J RS) journal entries. |
| Q | VE | Internal entry | This is an internal entry. No layout of entry-specific data is provided. |
| Q | VQ | Internal entry | This is an internal entry. No layout of entry-specific data is provided. |
| Q | VW | Internal entry | This is an internal entry. No layout of entry-specific data is provided. |
| Q | ZA | Change authority | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QSYJRNL.H. See the layout for the Change authority (E ZA, J ZA, Q ZA, Y ZA) journal entry. |
| Q | ZB | Change object attribute | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the Change object attribute (E ZB, D ZB, J ZB, Q ZB, Y ZB) journal entry. |
| Q | ZO | Ownership change | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QSYJRNL.H. See the layout for the Ownership change (E ZO, J ZO, Q ZO, Y ZO) journal entries. |
| Q | ZP | Change primary group | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QSYJRNL.H. See the layout for the Change primary group (E ZP, J ZP, Q ZP, Y ZP) journal entry. |
| Q | ZT | Auditing change | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the Auditing Change (E ZT, J ZT, Q ZT, Y ZT) journal entries. |
| R | BR | Before-image of record updated for rollback operation | This journal entry may have data which can only be accessed
by using either the QjoRetrieveJournalEntries API or the RCVJRNE command.
For the RCVJRNE command, use the ENTFMT(*TYPEPTR) or ENTFMT(*JRNENTFMT)
parameters. In all other interfaces, if the data is not visible, the
incomplete data indicator will be on and *POINTER will appear in the
Entry Specific Data. For more information, refer to Work with pointers in journal entries. This entry may have minimized entry specific data (ESD). It will have minimized ESD if its corresponding object type deposits minimized journal entries through the MINENTDTA parameter for this journal or journal receiver. See the layout for the Journal code R, all journal entry types except IL. |
| R | DL | Record deleted in the physical file member | This journal entry may have data which can only be accessed
by using either the QjoRetrieveJournalEntries API or the RCVJRNE command.
For the RCVJRNE command, use the ENTFMT(*TYPEPTR) or ENTFMT(*JRNENTFMT)
parameters. In all other interfaces, if the data is not visible, the
incomplete data indicator will be on and *POINTER will appear in the
Entry Specific Data. For more information, refer to Working with pointers in journal entries See the layout for the Journal code R, all journal entry types except IL. |
| R | DR | Record deleted for rollback operation | This journal entry may have data which can only be accessed
by using either the QjoRetrieveJournalEntries API or the RCVJRNE command.
For the RCVJRNE command, use the ENTFMT(*TYPEPTR) or ENTFMT(*JRNENTFMT)
parameters. In all other interfaces, if the data is not visible, the
incomplete data indicator will be on and *POINTER will appear in the
Entry Specific Data. For more information, refer to Working with pointers in journal entries. See the layout for the Journal code R, all journal entry types except IL. |
| R | IL | Increment record limit | These entries have entry-specific data which the system uses for internal processing. |
| R | PT | Record added to a physical file member. If the file is set up to reuse deleted records, then you may receive either a PT or PX journal entry for the change | This journal entry may have data which can only be accessed
by using either the QjoRetrieveJournalEntries API or the RCVJRNE command.
For the RCVJRNE command, use the ENTFMT(*TYPEPTR) or ENTFMT(*JRNENTFMT)
parameters. In all other interfaces, if the data is not visible, the
incomplete data indicator will be on and *POINTER will appear in the
Entry Specific Data. For more information, refer to Working with pointers in journal entries. See the layout for the Journal code R, all journal entry types except IL. |
| R | PX | Record added directly by RRN (relative record number) to a physical file member. If the file is set up to reuse deleted records, then you may receive either a PT or PX journal entry for the change | This journal entry may have data which can only be accessed
by using either the QjoRetrieveJournalEntries API or the RCVJRNE command.
For the RCVJRNE command, use the ENTFMT(*TYPEPTR) or ENTFMT(*JRNENTFMT)
parameters. In all other interfaces, if the data is not visible, the
incomplete data indicator will be on and *POINTER will appear in the
Entry Specific Data. For more information, refer toWorking with pointers in journal entries. This entry may have minimized entry specific data (ESD). It will have minimized ESD if its corresponding object type deposits minimized journal entries through the MINENTDTA parameter for this journal or journal receiver. See the layout for the Journal code R, all journal entry types except IL. |
| R | UB | Before-image of a record that is updated in the physical file member (this entry is present only if IMAGES(*BOTH) is specified on the STRJRNPF command) | Neither the before-image nor after-image is deposited into
the journal if the after-image is exactly the same as the before-image. This journal entry may have data which can only be accessed by using either the QjoRetrieveJournalEntries API or the RCVJRNE command. For the RCVJRNE command, use the ENTFMT(*TYPEPTR) or ENTFMT(*JRNENTFMT) parameters. In all other interfaces, if the data is not visible, the incomplete data indicator will be on and *POINTER will appear in the Entry Specific Data. For more information, refer to Working with pointers in journal entries. This entry may have minimized entry specific data (ESD). It will have minimized ESD if its corresponding object type deposits minimized journal entries through the MINENTDTA parameter for this journal or journal receiver. See the layout for the Journal code R, all journal entry types except IL. |
| R | UP | After-image of a record that is updated in the physical file member | Neither the before-image nor after-image is deposited into
the journal if the after-image is exactly the same as the before-image. This journal entry may have data which can only be accessed by using either the QjoRetrieveJournalEntries API or the RCVJRNE command. For the RCVJRNE command, use the ENTFMT(*TYPEPTR) or ENTFMT(*JRNENTFMT) parameters. In all other interfaces, if the data is not visible, the incomplete data indicator will be on and *POINTER will appear in the Entry Specific Data. For more information, refer to Working with pointers in journal entries. This entry may have minimized entry specific data (ESD). It will have minimized ESD if its corresponding object type deposits minimized journal entries through the MINENTDTA parameter for this journal or journal receiver. See the layout for the Journal code R, all journal entry types except IL. |
| R | UR | After-image of a record that is updated for rollback information | This journal entry may have data which can only be accessed
by using either the QjoRetrieveJournalEntries API or the RCVJRNE command.
For the RCVJRNE command, use the ENTFMT(*TYPEPTR) or ENTFMT(*JRNENTFMT)
parameters. In all other interfaces, if the data is not visible, the
incomplete data indicator will be on and *POINTER will appear in the
Entry Specific Data. For more information, refer to Working with pointers in journal entries . This entry may have minimized entry specific data (ESD). It will have minimized ESD if its corresponding object type deposits minimized journal entries through the MINENTDTA parameter for this journal or journal receiver. See the layout for the Journal code R, all journal entry types except IL. |
| S | AL | SNA alert focal point information | |
| S | CF | Mail configuration information | See the layout for the Change distribution queues (S CF) journal entry. |
| S | DX | X.400 process debug entry | |
| S | ER | Mail error information | See the layout for the Distribution errors (S ER) journal entry. |
| S | LG | Mail logging table information | See the layout for the Completed distributions (S LG) journal entry. |
| S | MX | A change was made to X.400 MTA configuration | |
| S | NX | A change was made to X.400 delivery notification | |
| S | RT | Mail routing information | See the layout for the Change routing table and secondary system name table (S RT) journal entries. |
| S | RX | A change was made to X.400 route configuration | |
| S | SY | Mail system information | See the layout for the Mail server framework system level events (S SY) journal entry. |
| S | UX | A change was made to X.400 (R) user or probe | |
| S | XE | DSNX error entry | See the layout for the Distribution errors (S XE) journal entries. |
| S | XL | DSNX logging entry | See the layout for the DSNX log (S XL) journal entries. |
| S | XX | An error was detected by the X.400 process | |
| T | AD | A change was made to the auditing attribute | See the layout for the Security Reference: Layout of audit journal entries. |
| T | AF | All authority failures | See the layout for the Security Reference: Layout of audit journal entries. |
| T | AP | A change was made to program adopt | See the layout for the Security Reference: Layout of audit journal entries. |
| T | AU | Attribute change | See the layout for the Security Reference: Layout of audit journal entries. |
| T | CA | Changes to object authority (authorization list or object) | See the layout for the Security Reference: Layout of audit journal entries. |
| T | CD | A change was made to a command string | See the layout for the Security Reference: Layout of audit journal entries. |
| T | CO | Create object | See the layout for the Security Reference: Layout of audit journal entries. |
| T | CP | Create, change, restore user profiles | See the layout for the Security Reference: Layout of audit journal entries. |
| T | CQ | A change was made to a change request descriptor | See the layout for the Security Reference: Layout of audit journal entries. |
| T | CU | Cluster operation | See the layout for the Security Reference: Layout of audit journal entries. |
| T | CV | Connection verification | See the layout for the Security Reference: Layout of audit journal entries. |
| T | CY | Cryptographic configuration | See the layout for the Security Reference: Layout of audit journal entries. |
| T | DI | Directory services | See the layout for the Security Reference: Layout of audit journal entries. |
| T | DO | All delete operations on the system | See the layout for the Security Reference: Layout of audit journal entries. |
| T | DS | DST security officer password reset | See the layout for the Security Reference: Layout of audit journal entries. |
| T | EV | Environment variable | See the layout for the Security Reference: Layout of audit journal entries. |
| T | GR | General purpose audit record | See the layout for the Security Reference: Layout of audit journal entries. |
| T | GS | A descriptor was given | See the layout for the Security Reference: Layout of audit journal entries. |
| T | IM | Intrusion monitor | See the layout for the Security Reference: Layout of audit journal entries. |
| T | IP | Inter-process communication event | See the layout for the Security Reference: Layout of audit journal entries. |
| T | IR | IP rules actions | See the layout for the Security Reference: Layout of audit journal entries. |
| T | IS | Internet security management | See the layout for the Security Reference: Layout of audit journal entries. |
| T | JD | Changes to the USER parameter of a job description | See the layout for the Security Reference: Layout of audit journal entries. |
| T | JS | A change was made to job data | See the layout for the Security Reference: Layout of audit journal entries. |
| T | KF | Key ring file name | See the layout for the Security Reference: Layout of audit journal entries. |
| T | LD | A link, unlink, or lookup operation to a directory | See the layout for the Security Reference: Layout of audit journal entries. |
| T | ML | A change was made to office services mail | See the layout for the Security Reference: Layout of audit journal entries. |
| T | NA | Changes to network attributes | See the layout for the Security Reference: Layout of audit journal entries. |
| T | ND | Directory search violations | See the layout for the Security Reference: Layout of audit journal entries. |
| T | NE | End point violations | See the layout for the Security Reference: Layout of audit journal entries. |
| T | OM | Object management change | See the layout for the Security Reference: Layout of audit journal entries. |
| T | OR | Object restored | See the layout for the Security Reference: Layout of audit journal entries. |
| T | OW | Changes to object ownership | See the layout for the Security Reference: Layout of audit journal entries. |
| T | O1 | Single optical object access | See the layout for the Security Reference: Layout of audit journal entries. |
| T | O2 | Dual optical object access | See the layout for the Security Reference: Layout of audit journal entries. |
| T | O3 | Optical volume access | See the layout for the Security Reference: Layout of audit journal entries. |
| T | PA | Changes to programs (CHGPGM) that will now adopt the owner's authority | See the layout for the Security Reference: Layout of audit journal entries. |
| T | PG | Changes to an object's primary group | See the layout for the Security Reference: Layout of audit journal entries. |
| T | PO | A change was made to printed output | See the layout for the Security Reference: Layout of audit journal entries. |
| T | PS | Profile swap | See the layout for the Security Reference: Layout of audit journal entries. |
| T | PW | Passwords used that are not valid | See the layout for the Security Reference: Layout of audit journal entries. |
| T | RA | Restore of objects when authority changes | See the layout for the Security Reference: Layout of audit journal entries. |
| T | RJ | Restore of job descriptions that contain user profile names | See the layout for the Security Reference: Layout of audit journal entries. |
| T | RO | Restore of objects when ownership information changes | See the layout for the Security Reference: Layout of audit journal entries. |
| T | RP | Restore of programs that adopt their owner's authority | See the layout for the Security Reference: Layout of audit journal entries. |
| T | RQ | A change request descriptor was restored | See the layout for the Security Reference: Layout of audit journal entries. |
| T | RU | Restore of authority for user profiles | See the layout for the Security Reference: Layout of audit journal entries. |
| T | RZ | The primary group for an object was changed during a restore operation | See the layout for the Security Reference: Layout of audit journal entries. |
| T | SD | A change was made to the system directory | See the layout for the Security Reference: Layout of audit journal entries. |
| T | SE | Changes to subsystem routing | See the layout for the Security Reference: Layout of audit journal entries. |
| T | SF | A change was made to a spooled output file | See the layout for the Security Reference: Layout of audit journal entries. |
| T | SG | Asynchronous signals | See the layout for the Security Reference: Layout of audit journal entries. |
| T | SK | Secure sockets connection | See the layout for the Security Reference: Layout of audit journal entries. |
| T | SM | A change was made by system management | See the layout for the Security Reference: Layout of audit journal entries. |
| T | SO | A change was made by server security | See the layout for the Security Reference: Layout of audit journal entries. |
| T | ST | A change was made by system tools | See the layout for the Security Reference: Layout of audit journal entries. |
| T | SV | Changes to system values | See the layout for the Security Reference: Layout of audit journal entries. |
| T | VA | Changes to access control list | See the layout for the Security Reference: Layout of audit journal entries. |
| T | VC | Connection started or ended | See the layout for the Security Reference: Layout of audit journal entries. |
| T | VF | Server files were closed | See the layout for the Security Reference: Layout of audit journal entries. |
| T | VL | An account limit was exceeded | See the layout for the Security Reference: Layout of audit journal entries. |
| T | VN | A logon or logoff operation on the network | See the layout for the Security Reference: Layout of audit journal entries. |
| T | VO | Actions on validation lists | See the layout for the Security Reference: Layout of audit journal entries. |
| T | VP | A network password error | See the layout for the Security Reference: Layout of audit journal entries. |
| T | VR | A network resources was accessed | See the layout for the Security Reference: Layout of audit journal entries. |
| T | VS | A server session started or ended | See the layout for the Security Reference: Layout of audit journal entries. |
| T | VU | A network profile was changed | See the layout for the Security Reference: Layout of audit journal entries. |
| T | VV | Service status was changed | See the layout for the Security Reference: Layout of audit journal entries. |
| T | XD | Extension of the directory services entry | See the layout for the Security Reference: Layout of audit journal entries. |
| T | X0 | Network authentication | See the layout for the Security Reference: Layout of audit journal entries. |
| T | X1 | Identity token | See the layout for the Security Reference: Layout of audit journal entries. |
| T | X2 | Reserved for future audit entry | See the layout for the Security Reference: Layout of audit journal entries. |
| T | X3 | Reserved for future audit entry | See the layout for the Security Reference: Layout of audit journal entries. |
| T | X4 | Reserved for future audit entry | See the layout for the Security Reference: Layout of audit journal entries. |
| T | X5 | Reserved for future audit entry | See the layout for the Security Reference: Layout of audit journal entries. |
| T | X6 | Reserved for future audit entry | See the layout for the Security Reference: Layout of audit journal entries. |
| T | X7 | Reserved for future audit entry | See the layout for the Security Reference: Layout of audit journal entries. |
| T | X8 | Reserved for future audit entry | See the layout for the Security Reference: Layout of audit journal entries. |
| T | X9 | Reserved for future audit entry | See the layout for the Security Reference: Layout of audit journal entries. |
| T | YC | A change was made to DLO change access | See the layout for the Security Reference: Layout of audit journal entries. |
| T | YR | A change was made to DLO read access | See the layout for the Security Reference: Layout of audit journal entries. |
| T | ZC | A change was made to object change access | See the layout for the Security Reference: Layout of audit journal entries. |
| T | ZR | A change was made to object read access | See the layout for the Security Reference: Layout of audit journal entries. |
| U | User-specified. The Entry-specific data is the value specified on the ENTDTA parameter of the SNDJRNE command or with the entry data parameter for the QJOSJRNE API | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. |
|
| Y | LF | Logical file associated with the library | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the Logical file associated with the library or based on physical file (D LF, Y LF) journal entry. |
| Y | YA | Change library attributes | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the Change library attributes (Y YA) journal entry. |
| Y | YB | Journaling for library started | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the Journaling for library started (Y YB) journal entry. |
| Y | YD | Library deleted | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. There is no entry-specific data for this entry. |
| Y | YE | Journaling for library ended | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. There is no entry-specific data for this entry. |
| Y | YH | Library changes applied | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the APYJRNCHG (B AT, D DD, E EQ, F AY, Q QH, Y YH) and RMVJRNCHG (E EX, F RC) journal entries. |
| Y | YI | Library in use at abnormal end | There is no entry-specific data for this entry. |
| Y | YK | Change journaled object attribute | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the Change journaled object attributes (B JA, D DJ, E EK, F JC, Q QF, Y YK) journal entries. |
| Y | YN | Library renamed | Even if this journal has a journal state of *STANDBY, this entry type will still be deposited in the journal receiver. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the Library renamed (Y YN) journal entry. |
| Y | YO | Object added to library | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the Object added to library (Y YO) journal entry. |
| Y | YS | Library saved | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the Object saved (B FS, D DH, E ES, F MS, Q QY, Y YS) journal entries. |
| Y | YW | Start of save for library | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the Start of save-while-active (B FW, D DW, E EW, F SS, Q QX, Y YW) journal entries. |
| Y | YY | Apyjrnchg command started | |
| Y | YZ | Library restored | These entries do not indicate that they occurred as the result of a trigger program, even if a trigger program caused the event. That information is not available at the time the entry is written to the journal. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the Object restored (B FR, D DZ, E EL, F MR, J RR, Q QZ, Y YZ) and receiver saved (J RS) journal entries. |
| Y | ZA | Change authority | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QSYJRNL.H. See the layout for the Object restored (B FR, D DZ, E EL, F MR, J RR, Q QZ, Y YZ) and receiver saved (J RS) journal entries. |
| Y | ZB | Object attribute change | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QLIJRNL.H. See the layout for the Change object attribute (E ZB, D ZB, J ZB, Q ZB, Y ZB) journal entry. |
| Y | ZO | Change owner | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QSYJRNL.H. See the layout for the Ownership change (E ZO, J ZO, Q ZO, Y ZO) journal entries. |
| Y | ZP | Change primary group | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QSYJRNL.H. See the layout for the Change primary group (E ZP, J ZP, Q ZP, Y ZP) journal entry. |
| Y | ZT | Change audit attribute | The entry-specific data for these journal entries is laid out in the QSYSINC include file, QSYJRNL.H. See the layout for the Auditing Change (E ZT, J ZT, Q ZT, Y ZT) journal entries. |