| 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 variable width portion of this 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 variable width portion of this journal entry. |
| 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 variable width portion of this 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 variable width portion of this 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 variable width portion of this 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 variable width portion of this 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 variable width portion of this 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 variable width portion of this 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 variable width portion of this 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 variable width portion of this journal entry. |
| B | B7 | Created object authority 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 Work with pointers in journal entries. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the variable width portion of this 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 variable width portion of this 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 variable width portion of this 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 variable width portion of this 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 variable width portion of this 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 variable width portion of this 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| B | JA | Change journaled 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| B | OI | Object in use at abnormal end | See the layout for the variable width portion of this journal entry. |
| 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 variable width portion of this 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 variable width portion of this 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 variable width portion of this journal entry. |
| B | WA | Write, after-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 Work with pointers in journal entries. The entry-specific data for these journal entries is laid out in the QSYSINC include file, QP0LJRNL.H. See the layout for the variable width portion of this journal entry. |
| C | BA | Commit in use at abnormal end | See the layout for the variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| C | CN | Rollback ended early | See the layout for the variable width portion of this journal entry. |
| 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 layouts for the Logical Unit of Work journal entry and the following: |
| C | PC | Prepare commit block | |
| C | RB | Set of record changes rolled back (ROLLBACK) | See the layout for the variable width portion of this 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| D | AC | Add referential integrity constraint | See the layout for the variable width portion of this journal entry. |
| D | CG | Change file | See the layout for the variable width portion of this journal entry. |
| D | CT | Create database file | See the layout for the variable width portion of this journal entry. |
| D | DC | Remove referential integrity constraint | See the layout for the variable width portion of this journal entry. |
| D | DD | End of apply or remove | See the layout for the variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| D | DJ | Change journaled object attribute | See the layout for the variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| D | GC | Change constraint | See the layout for the variable width portion of this journal entry. |
| D | GO | Change owner | See the layout for the variable width portion of this journal entry. |
| D | GT | Grant authority | See the layout for the variable width portion of this journal entry. |
| D | ID | File in use | See the layout for the variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| D | MA | Member added to file | |
| D | RV | Revoke authority | See the layout for the variable width portion of this journal entry. |
| D | TC | Add trigger | See the layout for the variable width portion of this journal entry. |
| D | TD | Remove trigger | See the layout for the variable width portion of this journal entry. |
| D | TG | Change trigger | See the layout for the variable width portion of this journal entry. |
| D | TQ | Refresh table | See the layout for the variable width portion of this journal entry. |
| 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 variable width portion of this 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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, QSYJRNL.H. See the layout for the variable width portion of this journal entry. |
| E | 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 variable width portion of this journal entry. |
| E | 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 variable width portion of this journal entry. |
| E | 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 variable width portion of this journal entry. |
| E | ZT | Auditing change | The entry-specific data for these journal entries is laid out in the
QSYSINC include file, QSYJRNL.H. See the layout for the variable width portion of this journal entry. |
| F | AY | Journaled changes applied to a physical file member (APYJRNCHG) | See the layout for the variable width portion of this journal entry. |
| F | CB | Physical file member changed | |
| F | CE | Change end of data for physical file member | See the layout for the variable width portion of this journal entry. |
| F | CH | Change file | As of V5R1M0, the journal entry D CG is also being sent for the change file operations. IBM (TM) 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 variable width portion of this journal entry. |
| F | CR | Physical file member cleared (CLRPFM) | |
| F | C1 | Rollback ended early | See the layout for the variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| F | FI | System-generated journal entry format information | |
| F | IT | Identity value | See the layout for the variable width portion of this journal entry. |
| F | IU | Physical file member in use at the time of abnormal system end | See the layout for the variable width portion of this journal entry. |
| 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 Work with pointers in journal entries. See the layout for the variable width portion of this journal entry. |
| F | JC | Change journaled object attribute | See the layout for the variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| F | MO | Allow use with partial transactions | See the layout for the variable width portion of this 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| F | RC | Journaled changes removed from a physical file member (RMVJRNCHG) | See the layout for the variable width portion of this journal entry. |
| F | RG | Physical file member reorganized (RGZPFM) | See the layout for the variable width portion of this 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 variable width portion of this journal entry. |
| I | DA | Directory in use at abnormal end | See the layout for the variable width portion of this journal entry. |
| 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 | 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 variable width portion of this journal entry. |
| 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 | 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| J | RF | Storage for a journal receiver freed (SAVOBJ, SAVCHGOBJ, or SAVLIB) | See the layout for the variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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. |
| L | LK | License key is not valid | See the layout for the variable width portion of this journal entry. |
| L | LL | Usage limit changed | See the layout for the variable width portion of this journal entry. |
| L | LU | Usage limit exceeded | See the layout for the variable width portion of this 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 | Refer to TCP/IP configuration and reference on the V5R1 Supplemental
Manuals Web site for information about the entry specific data for TCP/IP journal entries. |
| M | TN | IP NAT rules actions | Refer to TCP/IP configuration and reference on the V5R1 Supplemental
Manuals Web site for information about the entry specific data for TCP/IP journal entries. |
| M | TS | Virtual private networking (VPN) information | Refer to TCP/IP configuration and reference on the V5R1 Supplemental
Manuals Web site for information about the entry specific data for TCP/IP journal entries. |
| 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, QLIJRNL.H. See the layout for the variable width portion of this 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, QLIJRNL.H. See the layout for the variable width portion of this journal entry. |
| Q | QC | Data queue cleared, 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. See the layout for the variable width portion of this journal entry. |
| 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 | 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 variable width portion of this journal entry. |
| 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 variable width portion of this 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 Work 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 variable width portion of this 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 variable width portion of this 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 Work with pointers in journal entries. 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. See the layout for the variable width portion of this 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. 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. See the layout for the variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 variable width portion of this 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 variable width portion of this journal entry. |
| Q | ZO | Ownership change | The entry-specific data for these journal entries is laid out in the
QSYSINC include file, QLIJRNL.H. See the layout for the variable width portion of this journal entry. |
| 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 variable width portion of this 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 variable width portion of this journal entry. |
| 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 variable width portion of this journal entry. |
| 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 Work with pointers in journal entries. See the layout for the variable width portion of this journal entry. |
| 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 Work with pointers in journal entries. See the layout for the variable width portion of this journal entry. |
| 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 Work with pointers in journal entries. See the layout for the variable width portion of this journal entry. |
| 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 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. 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 variable width portion of this journal entry. |
| 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 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 variable width portion of this journal entry. |
| 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 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 variable width portion of this journal entry. |
| 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 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 variable width portion of this journal entry. |
| S | AL | SNA alert focal point information | See SNA
Distribution Services on the V5R1 Supplemental Manuals Web site for the layout of the entry specific data for entries generated by SNADS. |
| S | CF | Mail configuration information | See SNA
Distribution Services on the V5R1 Supplemental Manuals Web site for the layout of the entry specific data for entries generated by SNADS. See AnyMail/400 Mail Server Framework
Support |
| S | DX | X.400 (R) process debug entry | |
| S | ER | Mail error information | See SNA
Distribution Services on the V5R1 Supplemental Manuals Web site for the layout of the entry specific data for entries generated by SNADS. See AnyMail/400 Mail Server Framework
Support |
| S | LG | Mail logging table information | See SNA
Distribution Services on the V5R1 Supplemental Manuals Web site for the layout of the entry specific data for entries generated by SNADS. See AnyMail/400 Mail Server Framework
Support |
| S | MX | A change was made to X.400 (R) MTA configuration | |
| S | NX | A change was made to X.400 (R) delivery notification | |
| S | RT | Mail routing information | See SNA
Distribution Services on the V5R1 Supplemental Manuals Web site for the layout of the entry specific data for entries generated by SNADS. See AnyMail/400 Mail Server Framework
Support |
| S | RX | A change was made to X.400 (R) route configuration | |
| S | SY | Mail system information | See SNA
Distribution Services on the V5R1 Supplemental Manuals Web site for the layout of the entry specific data for entries generated by SNADS. See AnyMail/400 Mail Server Framework
Support |
| S | UX | A change was made to X.400 (R) user or probe | |
| S | XE | DSNX error entry | See SNA
Distribution Services on the V5R1 Supplemental Manuals Web site for the layout of the entry specific data for entries generated by SNADS. |
| S | XL | DSNX logging entry | See SNA
Distribution Services on the V5R1 Supplemental Manuals Web site for the layout of the entry specific data for entries generated by SNADS. |
| S | XX | An error was detected by the X.400 (R) process | |
| T | AD | A change was made to the auditing attribute | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | AF | All authority failures | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | AP | A change was made to program adopt | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | AU | Attribute change | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | CA | Changes to object authority (authorization list or object) | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | CD | A change was made to a command string | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | CO | Create object | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | CP | Create, change, restore user profiles | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | CQ | A change was made to a change request descriptor | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | CU | Cluster operation | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | CV | Connection verification | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | CY | Cryptographic configuration | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | DI | Directory services | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | DO | All delete operations on the system | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | DS | DST security officer password reset | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | EV | Environment variable | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | GR | General purpose audit record | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | GS | A descriptor was given | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | IM | Intrusion monitor | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | IP | Inter-process communication event | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | IR | IP rules actions | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | IS | Internet security management | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | JD | Changes to the USER parameter of a job description | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | JS | A change was made to job data | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | KF | Key ring file name | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | LD | A link, unlink, or lookup operation to a directory | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | ML | A change was made to office services mail | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | NA | Changes to network attributes | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | ND | Directory search violations | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | NE | End point violations | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | OM | Object management change | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | OR | Object restored | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | OW | Changes to object ownership | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | O1 | Single optical object access | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | O2 | Dual optical object access | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | O3 | Optical volume access | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | PA | Changes to programs (CHGPGM) that will now adopt the owner's authority | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | PG | Changes to an object's primary group | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | PO | A change was made to printed output | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | PS | Profile swap | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | PW | Passwords used that are not valid | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | RA | Restore of objects when authority changes | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | RJ | Restore of job descriptions that contain user profile names | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | RO | Restore of objects when ownership information changes | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | RP | Restore of programs that adopt their owner's authority | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | RQ | A change request descriptor was restored | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | RU | Restore of authority for user profiles | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | RZ | The primary group for an object was changed during a restore operation | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | SD | A change was made to the system directory | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | SE | Changes to subsystem routing | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | SF | A change was made to a spooled output file | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | SG | Asynchronous signals | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | SK | Secure sockets connection | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | SM | A change was made by system management | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | SO | A change was made by server security | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | ST | A change was made by system tools | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | SV | Changes to system values | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | VA | Changes to access control list | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | VC | Connection started or ended | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | VF | Server files were closed | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | VL | An account limit was exceeded | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | VN | A logon or logoff operation on the network | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | VO | Actions on validation lists | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | VP | A network password error | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | VR | A network resources was accessed | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | VS | A server session started or ended | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | VU | A network profile was changed | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | VV | Service status was changed | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | X0 | Network authentication | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | X1 | Identity token | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | X2 | Reserved for future audit entry | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | X3 | Reserved for future audit entry | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | X4 | Reserved for future audit entry | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | X5 | Reserved for future audit entry | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | X6 | Reserved for future audit entry | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | X7 | Reserved for future audit entry | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | X8 | Reserved for future audit entry | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | X9 | Reserved for future audit entry | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | YC | A change was made to DLO change access | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | YR | A change was made to DLO read access | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| T | ZC | A change was made to object change access | Only one entry per opened file. The member name will not be displayed
in the entry specific data for based on physical files. See iSeries (TM)Security
Reference |
| T | ZR | A change was made to object read access | See iSeries
(TM)Security Reference for the layout of the entry specific data. |
| 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 | The entry is deposited in the journal receiver even if the journal state is *STANDBY, if the user chooses to override the *STANDBY state on the SNDJRNE command or QJOSJRNE API. |