Use this topic to determine layouts for the fixed-length portion of journal entries.
These fields are shown when you request *TYPE1 for the output file format or the entry type format. The uppercase field names shown in parentheses are used in the system-supplied output file QSYS/QADSPJRN. The field names that are in italics are the variable names for these fields in the QjoRetrieveJournalEntries API header file. These variables are under the type definition for the RJNE0100 format. The QjoRetrieveJournalEntries API header is in the QJOURNAL.H file of the QSYSINC library.
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Entry length (JOENTL) | Zoned (5,0) | Specifies the length of the journal entry including the entry length
field, all subsequent positions of the journal entry, and any portion of the
journal entry that was truncated if the length of the output record is less
than the length of the record created for the journal entry. If the journal entry has the incomplete data indicator on, then this length does not include that additional data which could be pointed to. This length includes the length of the data that is actually returned, which includes entry specific data of up to 32 766 bytes. |
6 | Sequence number (JOSEQN, Seq_Number) | Zoned (10,0) | Assigned by the system to each journal entry. It is initially set to
1 for each new or restored journal and is incremented until you request that
it be reset when you attach a new receiver. There are occasional gaps in the
sequence numbers because the system uses internal journal entries for control
purposes. These gaps occur if you use commitment control, journal physical
files, or journal access paths. This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the sequence number is larger than 9 999 999 999. |
16 | Journal code (JOCODE, Jrn_Code) | Char (1) | Identifies the primary category of the journal entry:
The journal codes are described in more detail in Journal code descriptions. |
17 | Entry type (JOENTT, Entry_Type) | Char (2) | Further identifies the type of user-created or system-created entry. See the Journal code finder for descriptions of the entry types. |
19 | Date stamp (JODATE) | Char (6) | Specifies the system date when the entry was added and is in the format of the job attribute DATFMT. The system cannot assure that the date stamp is always in ascending order for sequential journal entries because you can change the value of the system date. |
25 | Time stamp (JOTIME) | Zoned (6,0) | Corresponds to the system time (in the format hhmmss) when the entry was added. The system cannot assure that the time stamp is always in ascending order for sequential journal entries because you can change the value of the system time. |
31 | Job name (JOJOB, Job_Name) | Char (10) | Specifies the name of the job that added the entry. Notes:
|
41 | User name (JOUSER, User_Name) | Char (10) | Specifies the user profile name of the user that started the job. Note: If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then blanks are written for the user name.
|
51 | Job number (JONBR, Job_Number) | Zoned (6,0) | Specifies the job number of the user that started the job. Note: If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then zeroes are written for the job number.
|
57 | Program name (JOPGM, Program_Name) | Char (10) | Specifies the name of the program that added the entry. If an application
or CL program did not add the entry, the field contains the name of a system-supplied
program such as QCMD or QPGMMENU. If the program name is the special value
*NONE, then one of the following is true:
For example, the program name is not available if the program was destroyed. Notes:
|
67 | Object name (JOOBJ, Object) | Char (10) | Specifies the name of the object for which the journal entry was added.1 This
is blank for some entries. If the journaled object is an integrated file system object, then this field is the first 10 bytes of the file identifier. |
77 | Library name (JOLIB) | Char (10) | Specifies the name of the library containing the object1. If the journaled object is an integrated file system object, then the first 6 characters of this field are the last 6 bytes of the file identifier. |
87 | Member name (JOMBR) | Char (10) | Specifies the name of the physical file member or is blank if the object is not a physical file1. |
97 | Count/relative record number (JOCTRR, Count_Rel_Rec_Num) | Zoned (10,0) | Contains either the relative record number (RRN) of the record that
caused the journal entry or a count that is pertinent to the specific type
of journal entry. The following tables show specific values for this field,
if applicable:
This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the count or relative record number is larger than 9 999 999 999. |
107 | Indicator flag (JOFLAG, Indicator_Flag) | Char (1) | Contains an indicator for the operation. The following tables show specific values for this field, if applicable: |
108 | Commit cycle identifier (JOCCID, Commit_Cycle_Id) | Zoned (10,0) | Contains a number that identifies the commit cycle. A commit cycle
is from one commit or rollback operation to another. The commit cycle identifier is found in every journal entry that is associated with a commitment transaction. If the journal entry was not made as part of a commitment transaction, this field is zero. This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the commit cycle identifier is larger than 9 999 999 999. |
118 | Incomplete data (JOINCDAT, Incomplete_Data) | Char (1) | Indicates whether this entry has data that is not being retrieved for
one of the following reasons:
The possible values are:
Any data which is marked as incomplete, can only be viewed by using either the QjoRetrieveJournalEntries API, or the command RCVJRNE with any of the following parameters:
|
119 | Minimized entry specific data (JOMINESD, Min_ESD) | Char (1) | Indicates whether this entry has minimized entry specific data. The possible values are:
|
120 | Reserved field (JORES) | Char (6) | Always contains zeros. Contains hexadecimal zeros in the output file. |
Note:
1If the journal receiver was attached prior to installing V4R2M0 on your system, then the following items are true:
If the journal receiver was attached while V4R2M0 or a later release was running on the system, the fully qualified name is the name of the object at the time the journal entry was deposited. |
These fields are shown when you request *TYPE2 for the output file format or the entry type format. The uppercase field names shown in parentheses are used in the system-supplied output file QSYS/QADSPJR2. The field names that are in italics are the variable names for these fields in the QjoRetrieveJournalEntries API header file. These variables are under the type definition for the RJNE0100 format. The QjoRetrieveJournalEntries API header is in the QJOURNAL.H file of the QSYSINC library.
Offset | Field | Format | Description |
---|---|---|---|
1 | Entry length (JOENTL) | Zoned (5,0) | Specifies the length of the journal entry including the entry length
field, all subsequent positions of the journal entry, and any portion of the
journal entry that was truncated if the length of the output record is less
than the length of the record created for the journal entry. If the journal entry has the incomplete data indicator on, then this length does not include that additional data which could be pointed to. This length includes the length of the data that is actually returned, which includes entry specific data of up to 32 766 bytes. |
6 | Sequence number (JOSEQN, Seq_Number) | Zoned (10,0) | Assigned by the system to each journal entry. It is initially set to
1 for each new or restored journal and is incremented until you request that
it be reset when you attach a new receiver. There are occasional gaps in the
sequence numbers because the system uses internal journal entries for control
purposes. These gaps occur if you use commitment control, journal physical
files, or journal access paths. This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the sequence number is larger than 9 999 999 999. |
16 | Journal code (JOCODE, Jrn_Code) | Char (1) | Identifies the primary category of the journal entry:
The journal codes are described in more detail in Journal code descriptions. |
17 | Entry type (JOENTT, Entry_Type) | Char (2) | Further identifies the type of user-created or system-created entry. See the Journal code finder for descriptions of the entry types. |
19 | Date stamp (JODATE) | Char (6) | Specifies the system date when the entry was added and is in the format of the job attribute DATFMT. The system cannot assure that the date stamp is always in ascending order for sequential journal entries because you can change the value of the system date. |
25 | Time stamp (JOTIME) | Zoned (6,0) | Corresponds to the system time (in the format hhmmss) when the entry was added. The system cannot assure that the time stamp is always in ascending order for sequential journal entries because you can change the value of the system time. |
31 | Job name (JOJOB, Job_Name) | Char (10) | Specifies the name of the job that added the entry. Notes:
|
41 | User name (JOUSER, User_Name) | Char (10) | Specifies the user profile name of the user that started the job. Note: If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then blanks are written for the user name.
|
51 | Job number (JONBR, Job_Number) | Zoned (6,0) | Specifies the job number of the user that started the job. Note: If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then zeroes are written for the job number.
|
57 | Program name (JOPGM, Program_Name) | Char (10) | Specifies the name of the program that added the entry. If an application
or CL program did not add the entry, the field contains the name of a system-supplied
program such as QCMD or QPGMMENU. If the program name is the special value
*NONE, then one of the following is true:
For example, the program name is not available if the program was destroyed. Notes:
|
67 | Object name (JOOBJ, Object) | Char (10) | Specifies the name of the object for which the journal entry was added.1 This
is blank for some entries. If the journaled object is an integrated file system object, then this field is the first 10 bytes of the file identifier. |
77 | Library name (JOLIB) | Char (10) | Specifies the name of the library containing the object1. If the journaled object is an integrated file system object, then the first 6 characters of this field are the last 6 bytes of the file identifier. |
87 | Member name (JOMBR) | Char (10) | Specifies the name of the physical file member or is blank if the object is not a physical file1. |
97 | Count/relative record number (JOCTRR, Count_Rel_Rec_Num) | Zoned (10,0) | Contains either the relative record number (RRN) of the record that
caused the journal entry or a count that is pertinent to the specific type
of journal entry. The following tables show specific values for this field,
if applicable:
This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the count or relative record number is larger than 9 999 999 999. |
107 | Indicator flag (JOFLAG, Indicator_Flag) | Char (1) | Contains an indicator for the operation. The following tables show specific values for this field, if applicable: |
108 | Commit cycle identifier (JOCCID, Commit_Cycle_Id) | Zoned (10,0) | Contains a number that identifies the commit cycle. A commit cycle
is from one commit or rollback operation to another. The commit cycle identifier is found in every journal entry that is associated with a commitment transaction. If the journal entry was not made as part of a commitment transaction, this field is zero. This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the commit cycle identifier is larger than 9 999 999 999. |
118 | User profile (JOUSPF, User_Profile) | Char (10) | Specifies the name of the user profile under which the job was running
when the entry was created. Note: If a RCVSIZOPT or a FIXLENDTA option was
specified that omitted the collection of this information, then *OMITTED is
given for the user profile.
|
128 | System name (JOSYNM, System_Name) | Char (8) | Specifies the name of the system on which the entry is being displayed, printed, retrieved, or received if the journal receiver was attached prior to installing V4R2M0 on the system. If the journal receiver was attached while the system was running V4R2M0 or a later release, the system name is the system where the journal entry was actually deposited. |
136 | Incomplete data (JOINCDAT, Incomplete_Data) | Char (1) | Indicates whether this entry has data that is not being retrieved for
one of the following reasons:
The possible values are:
Any data which is marked as incomplete, can only be viewed by using either the QjoRetrieveJournalEntries API, or the command RCVJRNE with any of the following parameters:
|
137 | Minimized entry specific data (JOMINESD, Min_ESD) | Char (1) | Indicates whether this entry has minimized entry specific data. The possible values are:
|
138 | Reserved field (JORES) | Char (18) | Always contains zeros. Contains hexadecimal zeros in the output file. |
Note:
1 If the journal receiver was attached prior to installing V4R2M0 on your system, then the following items are true:
If the journal receiver was attached while V4R2M0 or a later release was running on the system, the fully qualified name is the name of the object at the time the journal entry was deposited. |
These fields are shown when you request *TYPE3 for the output file format or the entry type format. The uppercase field names shown in parentheses are used in the system-supplied output file QSYS/QADSPJR3. The field names that are in italics are the variable names for these fields in the QjoRetrieveJournalEntries API header file. These variables are under the type definition for the RJNE0100 format. The QjoRetrieveJournalEntries API header is in the QJOURNAL.H file of the QSYSINC library.
Offset | Field | Format | Description |
---|---|---|---|
1 | Entry length (JOENTL) | Zoned (5,0) | Specifies the length of the journal entry including the entry length
field, all subsequent positions of the journal entry, and any portion of the
journal entry that was truncated if the length of the output record is less
than the length of the record created for the journal entry. If the journal entry has the incomplete data indicator on, then this length does not include that additional data which could be pointed to. This length includes the length of the data that is actually returned, which includes entry specific data of up to 32 766 bytes. |
6 | Sequence number (JOSEQN, Seq_Number) | Zoned decimal (10,0) | Assigned by the system to each journal entry. It is initially set to
1 for each new or restored journal and is incremented until you request that
it be reset when you attach a new receiver. There are occasional gaps in the
sequence numbers because the system uses internal journal entries for control
purposes. These gaps occur if you use commitment control, journal physical
files, or journal access paths. This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the sequence number is larger than 9 999 999 999. |
16 | Journal code (JOCODE, Jrn_Code) | Char (1) | Identifies the primary category of the journal entry:
The journal codes are described in more detail in Journal code descriptions. |
17 | Entry type (JOENTT, Entry_Type) | Char (2) | Further identifies the type of user-created or system-created entry. See the Journal code finder for descriptions of the entry types. |
19 | Time stamp (JOTMST, Time_Stamp) | Char (26) | Corresponds to the system date and time when the journal entry was added in the journal receiver. The time stamp is in SAA® format. The system cannot assure that the time stamp is always in ascending order for sequential journal entries because you can change the value of the system time. |
45 | Job name (JOJOB, Job_Name) 1 | Char (10) | Specifies the name of the job that added the entry. Notes:
|
55 | User name (JOUSER, User_Name) | Char (10) | Specifies the user profile name of the user that started the job. Note: If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then blanks are written for the user name.
|
65 | Job number (JONBR, Job_Number) | Zoned (6,0) | Specifies the job number of the user that started the job. Note: If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then zeroes are written for the job number.
|
71 | Program name (JOPGM, Program_Name) | Char (10) | Specifies the name of the program that added the entry. If an application
or CL program did not add the entry, the field contains the name of a system-supplied
program such as QCMD or QPGMMENU. If the program name is the special value
*NONE, then one of the following is true:
For example, the program name is not available if the program was destroyed. Notes:
|
81 | Object name (JOOBJ, Object) | Char (10) | Specifies the name of the object for which the journal entry was added.1 This
is blank for some entries. If the journaled object is an integrated file system object, then this field is the first 10 bytes of the file identifier. |
91 | Library name (JOLIB) | Char (10) | Specifies the name of the library containing the object1. If the journaled object is an integrated file system object, then the first 6 characters of this field are the last 6 bytes of the file identifier. |
101 | Member name (JOMBR) | Char (10) | Specifies the name of the physical file member or is blank if the object is not a physical file1. |
111 | Count/relative record number (JOCTRR, Count_Rel_Rec_Num) | Zoned (10,0) | Contains either the relative record number (RRN) of the record that
caused the journal entry or a count that is pertinent to the specific type
of journal entry.
This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the count or relative record number is larger than 9 999 999 999. |
121 | Indicator flag (JOFLAG, Indicator_Flag) | Char (1) | Contains an indicator for the operation. The following tables show specific values for this field, if applicable: |
122 | Commit cycle identifier (JOCCID, Commit_Cycle_Id) | Zoned (10,0) | Contains a number that identifies the commit cycle. A commit cycle
is from one commit or rollback operation to another. The commit cycle identifier is found in every journal entry that is associated with a commitment transaction. If the journal entry was not made as part of a commitment transaction, this field is zero. This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the commit cycle identifier is larger than 9 999 999 999. |
132 | User profile (JOUSPF, User_Profile) | Char (10) | Specifies the name of the user profile under which the job was running
when the entry was created. Note: If a RCVSIZOPT or a FIXLENDTA option was
specified that omitted the collection of this information, then *OMITTED is
given for the user profile.
|
142 | System name (JOSYNM, System_Name) | Char (8) | Specifies the name of the system on which the entry is being displayed, printed, retrieved, or received if the journal receiver was attached prior to installing V4R2M0 on the system. If the journal receiver was attached while the system was running V4R2M0 or a later release, the system name is the system where the journal entry was actually deposited. |
150 | Incomplete data (JOINCDAT, Incomplete_Data) | Char (1) | Indicates whether this entry has data that is not being
retrieved for one of the following reasons:
The possible values are:
Any data which is marked as incomplete, can only be viewed by using either the QjoRetrieveJournalEntries API, or the command RCVJRNE with any of the following parameters:
|
151 | Minimized entry specific data (JOMINESD, Min_ESD) | Char (1) | Indicates whether this entry has minimized entry specific
data. The possible values are:
|
152 | Reserved field (JORES) | Char (18) | Always contains zeros. Contains hexadecimal zeros in the output file. |
Note:
1If the journal receiver was attached prior to installing V4R2M0 on your system, then the following items are true:
If the journal receiver was attached while V4R2M0 or a later release was running on the system, the fully qualified name is the name of the object at the time the journal entry was deposited. |
These fields are shown when you request *TYPE4 for the output file format or the entry type format. The uppercase field names shown in parentheses are used in the system-supplied output file QSYS/QADSPJR4. The field names which are in italics are the variable names for these fields in the QjoRetrieveJournalEntries API header file. These variables are under the type definition for the RJNE0100 format. The QjoRetrieveJournalEntries API header is in the QJOURNAL.H file of the QSYSINC library.
Offset | Field | Format | Description |
---|---|---|---|
1 | Entry length (JOENTL) | Zoned (5,0) | Specifies the length of the journal entry including the entry length
field, all subsequent positions of the journal entry, and any portion of the
journal entry that was truncated if the length of the output record is less
than the length of the record created for the journal entry. If the journal entry has the incomplete data indicator on, then this length does not include that additional data which could be pointed to. This length includes the length of the data that is actually returned, which includes entry specific data of up to 32 766 bytes. |
6 | Sequence number (JOSEQN, Seq_Number) | Zoned decimal (10,0) | Assigned by the system to each journal entry. It is initially set to
1 for each new or restored journal and is incremented until you request that
it be reset when you attach a new receiver. There are occasional gaps in the
sequence numbers because the system uses internal journal entries for control
purposes. These gaps occur if you use commitment control, journal physical
files, or journal access paths. This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the sequence number is larger than 9 999 999 999. |
16 | Journal code (JOCODE, Jrn_Code) | Char (1) | Identifies the primary category of the journal entry:
The journal codes are described in more detail in Journal code descriptions. |
17 | Entry type (JOENTT, Entry_Type) | Char (2) | Further identifies the type of user-created or system-created entry. See the Journal code finder for descriptions of the entry types. |
19 | Time stamp (JOTMST, Time_Stamp) | Char (26) | Corresponds to the system date and time when the journal entry was added in the journal receiver. The time stamp is in SAA format. The system cannot assure that the time stamp is always in ascending order for sequential journal entries because you can change the value of the system time. |
45 | Job name (JOJOB, Job_Name) 1 | Char (10) | Specifies the name of the job that added the entry. Notes:
|
55 | User name (JOUSER, User_Name) | Char (10) | Specifies the user profile name of the user that started the job. Note: If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then blanks are written for the user name.
|
65 | Job number (JONBR, Job_Number) | Zoned (6,0) | Specifies the job number of the user that started the job. Note: If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then zeroes are written for the job number.
|
71 | Program name (JOPGM, Program_Name) | Char (10) | Specifies the name of the program that added the entry. If an application
or CL program did not add the entry, the field contains the name of a system-supplied
program such as QCMD or QPGMMENU. If the program name is the special value
*NONE, then one of the following is true:
For example, the program name is not available if the program was destroyed. Notes:
|
81 | Object name (JOOBJ, Object) | Char (10) | Specifies the name of the object for which the journal entry was added.1 This
is blank for some entries. If the journaled object is an integrated file system object, then this field is the first 10 bytes of the file identifier. |
91 | Library name (JOLIB) | Char (10) | Specifies the name of the library containing the object1. If the journaled object is an integrated file system object, then the first 6 characters of this field are the last 6 bytes of the file identifier. |
101 | Member name (JOMBR) | Char (10) | Specifies the name of the physical file member or is blank if the object is not a physical file1. |
111 | Count/relative record number (JOCTRR, Count_Rel_Rec_Num) | Zoned (10,0) | Contains either the relative record number (RRN) of the record that
caused the journal entry or a count that is pertinent to the specific type
of journal entry.
This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the count or relative record number is larger than 9 999 999 999. |
121 | Indicator flag (JOFLAG, Indicator_Flag) | Char (1) | Contains an indicator for the operation. The following tables show specific values for this field, if applicable: |
122 | Commit cycle identifier (JOCCID, Commit_Cycle_Id) | Zoned (10,0) | Contains a number that identifies the commit cycle. A commit cycle
is from one commit or rollback operation to another. The commit cycle identifier is found in every journal entry that is associated with a commitment transaction. If the journal entry was not made as part of a commitment transaction, this field is zero. This field can contain a -1 if receiver-size option RCVSIZOPT(*MAXOPT3) is selected and the actual value of the commit cycle identifier is larger than 9 999 999 999. |
132 | User profile (JOUSPF, User_Profile) | Char (10) | Specifies the name of the user profile under which the job was running
when the entry was created. Note: If a RCVSIZOPT or a FIXLENDTA option was
specified that omitted the collection of this information, then *OMITTED is
given for the user profile.
|
142 | System name (JOSYNM, System_Name) | Char (8) | Specifies the name of the system on which the entry is being displayed, printed, retrieved, or received if the journal receiver was attached prior to installing V4R2M0 on the system. If the journal receiver was attached while the system was running V4R2M0 or a later release, the system name is the system where the journal entry was actually deposited. |
150 | Journal identifier (JOJID, Jid) | Char(10) | Specifies the journal identifier (JID) for the object. When journaling
is started for an object, the system assigns a unique JID to that object.
The JID remains constant even if the object is renamed or moved. However,
if journaling is stopped, there is no guarantee that the JID will be the same
if journaling is started again for the same object. If no JID is associated with the entry, this field has hexadecimal zeros. |
160 | Referential constraint (JORCST, Referential_Constraint) | Char(1) | Indicates whether this entry was recorded for actions that occurred
on records that are part of a referential constraint. The possible values are:
|
161 | Trigger (JOTGR, Trigger) | Char(1) | Indicates whether this entry was created as result of a trigger program. The possible values are:
|
162 | Incomplete data (JOINCDAT, Incomplete_Data) | Char (1) | Indicates whether this entry has data that is not being retrieved for
one of the following reasons:
The possible values are:
Any data which is marked as incomplete, can only be viewed by using either the QjoRetrieveJournalEntries API, or the command RCVJRNE with any of the following parameters:
|
163 | Ignored by APYJRNCHG or RMVJRNCHG (JOIGNAPY, Ignore_during_APYRMV) | Char (1) | Indicates whether this journal entry will be ignored by the execution
of the APYJRNCHG or RMVJRNCHG commands,
even though normally this journal entry type has an effect during those command
invocations. The possible values are:
|
164 | Minimized entry specific data (JOMINESD, Min_ESD) | Char (1) | Indicates whether this entry has minimized entry specific data. The possible values are:
|
165 | Reserved area (JORES) | Char (5) | Always contains zeros. Contains hexadecimal zeros in the output file. |
Note: 1If the journal receiver
was attached prior to installing V4R2M0 on your system, then the following
items are true:
If the journal receiver was attached while V4R2M0 or a later release was running on the system, the fully qualified name is the name of the object at the time the journal entry was deposited. |
These fields are shown when you request *TYPE5 for the output file format or the entry type format. The uppercase field names shown in parentheses are used in the system-supplied output file QSYS/QADSPJR5. The field names that are italics are the variable names for these fields in the QjoRetrieveJournalEntries API header file. These variables are under the type definition for the RJNE0200 format. The QjoRetrieveJournalEntries API header is in the QJOURNAL.H file of the QSYSINC library.
Offset | Field | Format | Description |
---|---|---|---|
1 | Entry length (JOENTL) | Zoned (5,0) | Specifies the length of the journal entry including the entry length
field, all subsequent positions of the journal entry, and any portion of the
journal entry that was truncated if the length of the output record is less
than the length of the record created for the journal entry. If the journal entry has the incomplete data indicator on, then this length does not include that additional data which could be pointed to. This length includes the length of the data that is actually returned, which includes entry specific data of up to 32 766 bytes. |
6 | Sequence number (JOSEQN, Seq_Number) | Char (20) | Assigned by the system to each journal entry. It is initially set to 1 for each new or restored journal and is incremented until you request that it be reset when you attach a new receiver. There are occasional gaps in the sequence numbers because the system uses internal journal entries for control purposes. These gaps occur if you use commitment control, journal physical files, or journal access paths. |
26 | Journal code (JOCODE, Jrn_Code) | Char (1) | Identifies the primary category of the journal entry:
The journal codes are described in more detail in Journal code descriptions. |
27 | Journal entry type (JOENTT, Entry_Type) | Char (2) | Further identifies the type of user-created or system-created entry. See the Journal code finder for descriptions of the entry types. |
29 | Time stamp (JOTSTP) | Char (26) | Corresponds to the system date and time when the journal entry was added in the journal receiver. The time stamp is in SAA format. The system cannot assure that the time stamp is always in ascending order for sequential journal entries because you can change the value of the system time. |
55 | Job name (JOJOB, Job_Name) | Char (10) | Specifies the name of the job that added the entry. Notes:
|
65 | User name (JOUSER, User_Name) | Char (10) | Specifies the user profile name of the user that started the job. Note: If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then blanks are written for the user name.
|
75 | Job number (JONBR, Job_Number) | Zoned (6, 0) | Specifies the job number of the user that started the job. Note: If
a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then zeroes are written for the job number.
|
81 | Program name (JOPGM, Program_Name) | Char (10) | Specifies the name of the program that added the entry. If an application
or CL program did not add the entry, the field contains the name of a system-supplied
program such as QCMD or QPGMMENU. If the program name is the special value
*NONE, then one of the following is true:
For example, the program name is not available if the program was destroyed. Notes:
|
91 | Program library name (JOPGMLIB, Program_Library_Name) | Char (10) | The name of the library that contains the program that added the library.
If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection
of this information, then *OMITTED will be returned for the program library
name. IF *NONE is returned for Program name, then *NONE is also returned for the program library name. |
101 | Program library ASP device name (JOPGMDEV, Program_ASP_Device_Name) | Char (10) | The name of the ASP device that contains the program. If a RCVSIZOPT
or a FIXLENDTA option was specified that omitted the collection of this information,
then *OMITTED will be returned for the program library ASP device name. IF *NONE is returned for Program name, then *NONE is also returned for the program library ASP device name. |
111 | Program library ASP number (JOPGMASP, Program_ASP) | Zoned (5,0) | The number for the auxiliary storage pool that contains the program that added the journal entry. If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection of this information, then hexadecimal 0 will be returned for the program library ASP number. |
116 | Object name (JOOBJ, Object) | Char (10) | Specifies the name of the object for which the journal entry was added.1 This
is blank for some entries. If the journaled object is an integrated file system object, then this field is the first 10 bytes of the file identifier. |
126 | Object library (JOLIB) | Char (10) | Specifies the name of the library containing the object1. If the journaled object is an integrated file system object, then the first 6 characters of this field are the last 6 bytes of the file identifier. |
136 | Member name (JOMBR) | Char (10) | Specifies the name of the physical file member or is blank if the object is not a physical file1. |
146 | Count or relative record number (JOCTRR, Count_Rel_Rec_Num) | Char (20) | Contains either the relative record number (RRN) of the record that caused the journal entry or a count that is pertinent to type of journal entry. |
166 | Indicator flag (JOFLAG, Indicator_Flag) | Char (1) | Contains an indicator for the operation. The following tables show specific values for this field, if applicable: |
167 | Commit control ID (JOCCID, Commit_Cycle_Identifier ) | Char (20) | Contains a number that identifies the commit cycle. A commit cycle
is from one commit or rollback operation to another. The commit cycle identifier is found in every journal entry that is associated with a commitment transaction. If the journal entry was not made as part of a commitment transaction, this field is zero. |
187 | User profile (JOUSPF, User_profile) | Char (10) | Specifies the name of the user profile under which the job was running
when the entry was created. Note: If a RCVSIZOPT or a FIXLENDTA option was
specified that omitted the collection of this information, then *OMITTED is
given for the user profile.
|
197 | System name (JOSYNM, System_Name) | Char (8) | Specifies the name of the system on which the entry is being displayed, printed, retrieved, or received if the journal receiver was attached prior to installing V4R2M0 on the system. If the journal eceiver was attached while the system was running V4R2M0 or a later release, the system name is the system where the journal entry was actually deposited. |
205 | Journal identifier (JOJID, Jid) | Char (10) | Specifies the journal identifier (JID) for the object. When journaling
is started for an object, the system assigns a unique JID to that object.
The JID remains constant even if the object is renamed or moved. However,
if journaling is stopped, there is no guarantee that the JID will be the same
if journaling is started again for the same object. If no JID is associated with the entry, this field has hexadecimal zeros. |
215 | Referential constraint (JORCST, Referential_Constraint) | Char (1) | Indicates whether this entry was recorded for actions that occurred
on records that are part of a referential constraint. The possible values are:
|
216 | Trigger (JOTGR, Trigger) | Char (1) | Indicates whether this entry was created as result of a trigger program. The possible values are:
|
217 | Incomplete data (JOINCDAT, Incomplete_Data) | Char (1) | Indicates whether this entry has data that is not being retrieved for
one of the following reasons:
The possible values are:
Any data which is marked as incomplete, can only be viewed by using either the QjoRetrieveJournalEntries API, or the command RCVJRNE with any of the following parameters:
|
218 | Ignored by APYJRNCHG or RMVJRNCHG (JOIGNAPY, Ignore_during_APYRMV) | Char (1) | Indicates whether this journal entry will be ignored by the execution
of the APYJRNCHG or RMVJRNCHG commands, even though normally this journal
entry type has an effect during those command invocations. The possible values are:
|
219 | Minimized entry-specific data (JOMINESD, Min_ESD) | Char (1) | Indicates whether this entry has minimized entry specific data. The possible values are:
|
220 | Object indicator (JOOBJIND, Object_Name_Indicator) | Char (1) | An indicator with respect to the information in the object field2.
The valid values are:
|
221 | System sequence number (JOSYSSEQ, System_Sequence_Number) | Char (20) | The system sequence number indicates the relative sequence of when this journal entry was deposited into the journal. You can use the sequence number to sequentially order journal entries that are in separate journal receivers. If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection of this information, then hexadecimal 0 will be returned for the system sequence number. |
241 | Receiver name (JORCV) | Char (10) | The name assigned to the journal receiver |
251 | Receiver library name (JORCVLIB) | Char (10) | The name of the library in which the journal receiver resides. |
261 | Receiver library ASP device name (JORCVDEV) | Char (10) | The name of the ASP device for journal receivers that reside on an independent disk pool |
271 | Receiver library ASP number (JORCVASP) | Zoned (5,0) | The number of the ASP on which the journal receiver resides. |
276 | Arm number (JOARM, Arm_Number) | Zoned (5,0) | The number of the disk arm that contains the journal entry. |
281 | Thread identifier (JOTHDX, Thread_ID) | Hexadecimal (8) | Identifies the thread within the process that added the journal entry. If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection of this information, then hexadecimal 0 will be returned for the thread identifier. |
289 | Thread identifier formatted (JOTHD) | Char (16) | See Thread identifier. |
305 | Address family (JOADF, Address_Family) | Char (1) | The address family identifies the format of the remote address for
this journal entry. If a RCVSIZOPT or a FIXLENDTA option was specified that
omitted the collection of this information, then 0 will be returned for the
address family. The possible values are:
|
306 | Remote port (JORPORT) | Zoned (5, 0) | The remote port of a the journal entries. If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection of this information, then hexadecimal 0 will be returned for the remote port. |
311 | Remote address (JORADR) | Char (46) | The remote address of a the journal entries. If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection of this information, then hexadecimal 0 will be returned for the remote address. |
357 | Logical unit of work (JOLUW) | Char (39) | The logical unit of work identifies entries to be associated with a given unit of work, usually within a commit cycle. If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection of this information, then blanks will be returned for the logical unit of work. |
396 | Transaction identifier (JOXID) | Char (140) | See the QSYSINC/H.XA header file for the layout of this data. If a RCVSIZOPT or a FIXLENDTA option was specified that omitted the collection of this information, then the displacement to the transaction identifier is 0 and no transaction identifier is returned. |
536 | Object type (JOOBJTYP) | Char (7) | The type of object associated with this entry. (*FILE, *DTAARA, etc) |
543 | File type indicator (JOFILTYP) | Char (1) | The type of object associated with this entry. ('0' is physical, '1' is logical) |
544 | Nested commit level (JOCMTLVL) | Char (7) | The nested transaction level at which this entry was deposited. |
551 | Reserved | Char (5) | Reserved area. It always contains hexadecimal zeros. |
Notes:
1If the journal receiver was attached prior to installing V4R2M0 on your system, then the following items are true:
If the journal receiver was attached while V4R2M0 or a later release was running on the system, the fully qualified name is the name of the object at the time the journal entry was deposited. 2This value will be returned only when retrieving journal entries from a remote journal and the remote journal is currently being caught up from its source journal. A remote journal is being caught up from its source journal when the Change Remote Journal (CHGRMTJRN) command or Change Journal State (QjoChangeJournalState) API is called and is currently replicating journal entries to the remote journal. After the call to the CHGRMTJRN command or QjoChangeJournalState API returns, the remote journal is maintained with a synchronous or asynchronous delivery mode, and the remote journal is no longer being caught up. |