Layouts for variable-length portion of journal entries

 

The following tables contain the variable-length portion of the layouts for journal entries.

 

Allow use with partial transactions (F MO) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Reason code	Char (1)	01 = Partial transactions exist due to restore. 02 = Partial transactions exist because a rollback was ended early.
2	Reserved	Char (3)	Reserved. Set to zeros.
5	Number commit IDs	Bin (32)	The number of commit identifiers.
9	Reserved	Char (72)	Reserved. Set to zeros.
81	Commit IDs	Bin (64) [*]	The array of commit cycle identifiers for partial transactions that remain in the object.

APYJRNCHG (B AT, D DD, E EQ, F AY, Q QH) and RMVJRNCHG (E EX, F RC) journal entries

Relative offset	Field	Format	Description
Specific values for this entry type:
	Count or Relative Record Number (JOCTRR)	Zoned (10,0)	Contains the number of journal entries applied or removed. For *TYPE5 output files, the format of this field is Char (20).
	Flag (JOFLAG)	Char (1)	The results of the apply or remove operation: 0 = Command completed normally. 1 = Command completed abnormally.
Entry-specific data. This data appears as one field in the standard output formats:
1	First entry applied or removed	Zoned (10,0)	The sequence number of the first entry actually applied or removed. This field is set to -1 if the actual value is larger than 9 999 999 999. See the First entry applied or removed--large field for the actual value.
11	Last entry applied or removed.	Zoned (10,0)	The sequence number of the last entry actually applied or removed. This field is set to -1 if the actual value is larger than 9 999 999 999. See the Last entry applied or removed--large field for the actual value.
21	Starting receiver name	Char (10)	The name of the first receiver from which entries were applied or removed.
31	Library name	Char (10)	The name of the library for the starting journal receiver.
41	Ending receiver name	Char (10)	The name of the last or ending receiver from which entries were applied or removed.
51	Library name	Char (10)	The library for the ending journal receiver.
61	Starting sequence number	Char (10)	The specified starting sequence number for the apply or remove operation. This field is set to -1 if the actual value is larger than 9 999 999 999. See the Starting sequence number--large field for the actual value.
71	Ending sequence number	Char (10)	The specified ending sequence number for the apply or remove operation. This field is set to -1 if the actual value is larger than 9 999 999 999. See the Ending sequence number--large field for the actual value.
81	Incomplete commit transaction not applied or removed	Char (1)	0 = Indicates that either CMTBDY(*NO) was specified or CMTBDY(*YES) was specified and no partial commitment control transactions were found in the range specified by the starting and ending sequence numbers 1 = Indicates that CMTBDY(*YES) was specified and one or more partial commitment control transactions were found in the range specified by the starting and ending sequence numbers
82	First entry applied or removed--large	Char (20)	The sequence number of the first entry actually applied or removed. This field always contains a sequence number.
102	Last entry applied or removed--large	Char (20)	The sequence number of the last entry actually applied or removed. This field always contains a sequence number.
122	Starting sequence number--large	Char (20)	The specified starting sequence number for the apply or remove operation. This field always contains a sequence number.
142	Ending sequence number--large	Char (20)	The specified ending sequence number for the apply or remove operation. This field always contains a sequence number.
162	Number of entries	Char (20)	The number of entries that were applied or removed.
182	Partial transaction starting sequence number	Char (20)	Starting sequence number for any partial transactions that were removed. For integrated file system objects and data areas, this field is always zero.
202	Partial transaction ending sequence number	Char (20)	Ending sequence number for any partial transactions that were removed. For integrated file system objects and data areas, this field is always zero.
222	Number of partial transaction removed	Char (20)	Count of number of entries removed for partial transactions. For integrated file system objects and data areas, this number is always zero.
242	Object deleted	Char (1)	Indicates that the object was deleted during the apply or remove operation. Y = Yes N = No
243	Object created	Char (1)	Indicates that the object was created during the apply operation. Y = Yes N = No
244	Early end	Char (1)	Indicates if the apply or remove operation ended early for this object. Y = Yes N = No
245	Change not made	Char (1)	Indicates that a change was found for this object after an early end to the apply operation. Y = Yes N = No
246	End reason code	Char (1)	Reason code for early end. See message MCH4801 for the possible values.
247	End message ID	Char (7)	The message identifier associated with an early end to the apply operation.
254	Error condition	Bin (31)	The error condition code associated with an early end to the apply operation.
258	Partial transactions remain	Char (1)	Indicates that partial transactions remain for this object. Y = Yes N = No
259	Partial transactions removed	Char (1)	Indicates that at least some partial transactions were removed during the apply operation. Y = Yes N = No

 

Auditing Change (E ZT, Q ZT) journal entries

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Audit value	Char (10)	Object audit value

Change authority (E ZA, Q ZA) journal entry

Relative offset	Field	Format	Description
Specific values for this entry type:
1	User	Char (10)	The user profile or REFUSER on GRTUSRAUT command.
11	Authorization list	Char (10)	The name of the authorization list name.
21	Object existence authority	Char (1)	Y = User has *OBJEXIST authority to the object. blank = User does not have *OBJEXIST authority to the object.
22	Object management authority	Char (1)	Y = User has *OBJMGT authority to the object. blank = User does not have *OBJMGT authority to the object.
23	Object operational authority	Char (1)	Y = User has *OBJOPR authority to the object. blank = User does not have *OBJOPR authority to the object.
24	Authorization list management authority	Char (1)	Blank if user does not have authorization list management authority to the object.
25	Authorization list *PUBLIC authority	Char (1)	Y = User has *PUBLIC authority to the object. blank = User does not have *PUBLIC authority to the object.
26	Read authority	Char (1)	Y = User has *READ authority to the object. blank = User does not have *READ authority to the object.
27	Add authority	Char (1)	Y = User has *ADD authority to the object. blank = User does not have *ADD authority to the object.
28	Update authority	Char (1)	Y = User has *UPD authority to the object. blank = User does not have *UPD authority to the object.
29	Delete authority	Char (1)	Y = User has *DLT authority to the object. blank = User does not have *DLT authority to the object.
30	Exclude authority	Char (1)	Y = User has *EXCLUDE authority to the object. blank = User does not have *EXCLUDE authority to the object.
31	Execute authority	Char (1)	Y = User has *EXECUTE authority to the object. blank = User does not have *EXECUTE authority to the object.
32	Object alter authority	Char (1)	Y = User has *OBJALTER authority to the object. blank = User does not have *OBJALTER authority to the object.
33	Object reference authority	Char (1)	Y = User has *OBJREF authority to the object. blank = User does not have *OBJREF authority to the object.
34	Reserved	Char (4)	Reserved.
38	Operation type	Char (3)	Possible values are: GRT = Grant. RPL = Grant with replace. RVK = Revoke.

Change end of data (F CE) journal entry

Relative offset	Field	Format	Description
Specific values for this entry type:
	Count or relative record number (JOCTRR)	Zoned (10,0)	The relative record number of the last record kept in the physical file member.

Change journaled object attributes (B JA, D DJ, E EK, F JC) journal entries

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Attribute changed	Char (1)	Identifies which journal attribute was changed: 1 = IMAGES 2 = OMTJRNE 3 = INHERIT
2	New attributes value	Char (10)	The new value for the attribute that changed. The valid values for each attribute are as follows: IMAGES(*BOTH) IMAGES(*AFTER) OMTJRNE(*NONE) OMTJRNE(*OPNCLOSYN) INHERIT(*YES) INHERIT(*NO) Only the characters in the parenthesis appear in this field.

 

Change object attribute (E ZB, D ZB, Q ZB) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Number of records	Bin (4)	The number of variable length records that follow.
5	Key	Bin (4)	The field of an object attribute to change. See Change Object Description (QLICOBJD) API.
9	Length of data	Bin (4)	The length of the data used to change a specific field of an object attribute.
13	Data	Char (*)	The data used to change a specific field of an object attribute.

 

Change primary group (E ZP, Q ZP) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Old group	Char (10)	The name of the old primary group.
11	New group	Char (10)	The name of the new primary group.
21	Object existence authority	Char (1)	Y = *PUBLIC has *OBJEXIST authority to the object. blank = *PUBLIC does not have *OBJEXIST authority to the object. This field is only used when Authorization list *PUBLIC is blank.
22	Object management authority	Char (1)	Y = *PUBLIC has *OBJMGT authority to the object. blank = *PUBLIC does not have *OBJMGT authority to the object. This field is only used when Authorization list *PUBLIC is blank.
23	Object operational authority	Char (1)	Y = *PUBLIC has *OBJOPR authority to the object. blank = *PUBLIC does not have *OBJOPR authority to the object. This field is only used when Authorization list *PUBLIC is blank.
24	Object alter authority	Char (1)	Y = *PUBLIC has *OBJALTER authority to the object. blank = *PUBLIC does not have *OBJALTER authority to the object. This field is only used when Authorization list *PUBLIC is blank.
25	Object reference authority	Char (1)	Y = *PUBLIC has *OBJREF authority to the object. blank = *PUBLIC does not have *OBJREF authority to the object. This field is only used when Authorization list *PUBLIC is blank.
26	Reserved	Char (10)	Reserved. Set to blank.
36	Authorization list management	Char (1)	Blank if user does not have authorization list management authority to the object.
37	Read authority	Char (1)	Y = *PUBLIC has *READ authority to the object. blank = *PUBLIC does not have *READ authority to the object. This field is only used when Authorization list *PUBLIC is blank.
38	Add authority	Char (1)	Y = *PUBLIC has *ADD authority to the object. blank = *PUBLIC does not have *ADD authority to the object. This field is only used when Authorization list *PUBLIC is blank.
39	Update authority	Char (1)	Y = *PUBLIC has *UPD authority to the object. blank = *PUBLIC does not have *UPD authority to the object. This field is only used when Authorization list *PUBLIC is blank.
40	Delete authority	Char (1)	Y = *PUBLIC has *DLT authority to the object. blank = *PUBLIC does not have *DLT authority to the object. This field is only used when Authorization list *PUBLIC is blank.
41	Execute authority	Char (1)	Y = *PUBLIC has *EXECUTE authority to the object. blank = *PUBLIC does not have *EXECUTE authority to the object. This field is only used when Authorization list *PUBLIC is blank.
42	Reserved	Char (10)	Reserved. Set to blank.
52	Exclude authority	Char (1)	Y = *PUBLIC has *EXCLUDE authority to the object. blank = *PUBLIC does not have *EXCLUDE authority to the object. This field is only used when Authorization list *PUBLIC is blank.
53	Revoke	Char (1)	Y = The previous primary group authority to the object was revoked. blank = The previous primary group authority to the object was not revoked.

 

CHGJRN (J NR, J PR) journal entries

Relative offset	Field	Format	Description
Specific values for this entry type:
	Count or relative record number (JOCTRR)	Zoned (10,0)	Contains the number of receivers attached or detached.
Entry-specific data. This data appears as one field in the standard output formats:
1	First receiver name	Char (10)	The name of the first receiver that is attached or detached.
11	First receiver library name	Char (10)	The name of the library for the first receiver that is attached or detached.
21	Dual receiver name	Char (10)	The name of the dual receiver that is attached or detached. Blank if only one receiver is used for the journal.
31	Dual receiver library name	Char (10)	The name of the library for the dual receiver that is attached or detached. Blank if only one receiver is used for the journal.

 

COMMIT (C CM) journal entry

Relative offset	Field	Format	Description
Specific values for this entry type:
	Count or relative record number (JOCTRR)	Zoned (10,0)	Contains the length of the commit identification.
	Flag (JOFLAG)	Char (1)	Whether the commit operation was initiated by the system or the user: 0 = All record-level changes were committed for a commit operation initiated by a user. 2 = All record-level changes were committed for a commit operation initiated by the operating system.
Entry-specific data. This data appears as one field in the standard output formats:
1	Commit ID	Char (*)	Contains the commit identification specified by the operation. The Count field specifies the length of this field.

Create data area (E EE) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Create time of day and date	Char (8)	The date and timestamp when the data area was created.
9	Data area name	Char (10)	The data area name.
19	Data area library name	Char (10)	The data area library name.
29	Data area type	Char (5)	The created data area type. The valid types are: *CHAR - character *DEC - decimal *LOG - logical
34	Reserved	Char (3)	The filler to maintain alignment.
37	Number of elements	Bin (32)	The number of elements. If the type is *CHAR, only Length will contain a value. If the type is *DEC, both Length and Fraction length will contain values.
41	Length	Bin (32)	The declared length.
45	Fraction length	Bin (32)	The decimal positions.
49	Actual value length	Bin (32)	The length of entered data as seen by the user.
53	Value	Char (2000)	The data or value.
2053	Public authority	Char (10)	The public authority. The valid authorities are: *LIBCRTAUT *CHANGE *ALL *EXCLUDE *NAME
2063	Text description	Text (50)	The description or text.
2113	Owner	Char (10)	Object owner.
2123	Object existence authority	Char (1)	Y = *PUBLIC has *OBJEXIST authority to the object. blank = *PUBLIC does not have *OBJEXIST authority to the object.
2124	Object management authority	Char (1)	Y = *PUBLIC has *OBJMGT authority to the object. blank = *PUBLIC does not have *OBJMGT authority to the object.
2125	Object operational authority	Char (1)	Y = *PUBLIC has *OBJOPR authority to the object. blank = *PUBLIC does not have *OBJOPR authority to the object.
2126	Reserved	Char (4)	Reserved. Set to blank.
2130	Authorization list management	Char (1)	Y = Object is secured by an authorization list. The authorization list name can be found in the Resulting authority field later in this journal entry. blank = Object is not secured by an authorization list.
2131	Read authority	Char (1)	Y = *PUBLIC has *READ authority to the object. blank = *PUBLIC does not have *READ authority to the object.
2132	Add authority	Char (1)	Y = *PUBLIC has *ADD authority to the object. blank = *PUBLIC does not have *ADD authority to the object.
2133	Update authority	Char (1)	Y = *PUBLIC has *UPD authority to the object. blank = *PUBLIC does not have *UPD authority to the object.
2134	Delete authority	Char (1)	Y = *PUBLIC has *DLT authority to the object. blank = *PUBLIC does not have *DLT authority to the object.
2135	Exclude authority	Char (1)	Y = *PUBLIC has no authority to the object. blank = *PUBLIC has authority to the object.
2136	Execute authority	Char (1)	Y = *PUBLIC has *EXECUTE authority to the object. blank = *PUBLIC does not have *EXECUTE authority to the object.
2137	Object alter authority	Char (1)	Y = *PUBLIC has *OBJALTER authority to the object. blank = *PUBLIC does not have *OBJALTER authority to the object.
2138	Object reference authority	Char (1)	Y = *PUBLIC has *OBJREF authority to the object. blank = *PUBLIC does not have *OBJREF authority to the object.
2139	Resulting authority	Char (10)	The public authority resulting from the processing of the Create Data Area (CRTDTAARA) command. The value can be *CHANGE, *ALL, *USE, *EXCLUDE, or an authorization list name if the Authorization list management field in this journal entry is Y. For example, if *LIBCRTAUT was specified for the AUTHORITY keyword on the CRTDTAARA command, the value *LIBCRTAUT would be in the Public authority field and a value such as *USE could be found in this Resulting authority field. And the *USE value in this field could be specified for the AUTHORITY keyword on a subsequent CRTDTAARA command. If an error occurred, this field could be blank or a value that could not be specified for the AUTHORITY keyword on the CRTDTAARA command.

 

Create data queue (Q QA) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Create time of day and date	Char (8)	The date and timestamp when the data queue was created.
9	Data queue name	Char (10)	The data queue name.
19	Data queue library	Char (10)	The library containing the data queue.
29	Maximum entry length	Bin (32)	Maximum entry length. Possible values are 1 through 64512.
33	Force auxiliary storage	Char (1)	Force queue to auxiliary storage on send and receive: N = Force is not done Y = Force is done
34	Reserved	Char (8)	Reserved.
42	Sequence	Char (1)	Sequence in which entries are received from the data queue: F = FIFO queue K = Keyed queue L = LIFO queue
43	Key length	Bin (16)	Key length of a keyed queue. Possible values are 1 through 256.
45	Include sender ID	Char (1)	Attach a sender ID to each entry sent to the queue: N = Do not include ID Y = Include ID
46	Queue type	Char (1)	Type of data queue: S = Standard data queue DDM data queues cannot be journaled
47	Reserved	Bin (32)	Reserved. This field is set to zero.
51	Queue size maximum entries	Bin (32)	The maximum number of entries to allow: -1 = *MAX16MB -2 = *MAX2GB
55	Queue size initial entries	Bin (32)	Initial number of entries to allocate. The default on the CRTDTAQ command is 16.
59	Automatic reclaim	Char (1)	The settings for this field are: 0 = no storage released 1 = storage is released
60	Reserved	Char (481)	Reserved. This field is set to zero.
541	Public authority	Char (10)	The public authority to the data queue.
551	Text	Char (50)	Text description.
601	Owner	Char (10)	Object owner.
611	Object existence authority	Char (1)	Y = *PUBLIC has *OBJEXIST authority to the object. blank = *PUBLIC does not have *OBJEXIST authority to the object.
612	Object management authority	Char (1)	Y = *PUBLIC has *OBJMGT authority to the object. blank = *PUBLIC does not have *OBJMGT authority to the object.
613	Object operational authority	Char (1)	Y = *PUBLIC has *OBJOPR authority to the object. blank = *PUBLIC does not have *OBJOPR authority to the object.
614	Reserved	Char (4)	Reserved. Set to blank.
618	Authorization list management	Char (1)	Y = Object is secured by an authorization list. The authorization list name can be found in the Resulting authority field later in this journal entry. blank = Object is not secured by an authorization list.
619	Read authority	Char (1)	Y = *PUBLIC has *READ authority to the object. blank = *PUBLIC does not have *READ authority to the object.
620	Add authority	Char (1)	Y = *PUBLIC has *ADD authority to the object. blank = *PUBLIC does not have *ADD authority to the object.
621	Update authority	Char (1)	Y = *PUBLIC has *UPD authority to the object. blank = *PUBLIC does not have *UPD authority to the object.
622	Delete authority	Char (1)	Y = *PUBLIC has *DLT authority to the object. blank = *PUBLIC does not have *DLT authority to the object.
623	Exclude authority	Char (1)	Y = *PUBLIC has no authority to the object. blank = *PUBLIC has authority to the object.
624	Execute authority	Char (1)	Y = *PUBLIC has *EXECUTE authority to the object. blank = *PUBLIC does not have *EXECUTE authority to the object.
625	Object alter authority	Char (1)	Y = *PUBLIC has *OBJALTER authority to the object. blank = *PUBLIC does not have *OBJALTER authority to the object.
626	Object reference authority	Char (1)	Y = *PUBLIC has *OBJREF authority to the object. blank = *PUBLIC does not have *OBJREF authority to the object.
627	Resulting authority	Char (10)	The public authority resulting from the processing of the Create Data Queue (CRTDTAQ) command. The value can be *CHANGE, *ALL, *USE, *EXCLUDE, or an authorization list name if the Authorization list management field in this journal entry is Y. For example, if *LIBCRTAUT was specified for the AUTHORITY keyword on the CRTDTAQ command, the value *LIBCRTAUT would be in the Public authority field and a value such as *USE could be found in this Resulting authority field. And the *USE value in this field could be specified for the AUTHORITY keyword on a subsequent CRTDTAQ command. If an error occurred, this field could be blank or a value that could not be specified for the AUTHORITY keyword on the CRTDTAQ command.

 

Data queue cleared, has key (Q QJ) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Reserved	Char (2)	Reserved for future use.
3	Key length	Bin (16)	The number of characters in the key.
5	Key order	Char (2)	The Key order is as follows: GT = Greater than LT = Less than NE = Not equal EQ = Equal GE = Greater than or equal LE = Less than or equal
7	Key	Char (*)	The data to be used to remove a message from the data queue.

Delete access path (F PD) journal entry

Relative offset	Field	Format	Description
Specific values for this entry type:
	Journal identifier (JOJID)	Char (10)	The JID is not provided with the *TYPE1, *TYPE2, and *TYPE3 formats. It can be used with the QJORJIDI API.

 

Delete receiver (J RD, J RF) journal entries

Relative offset	Field	Format	Description
Specific values for this entry type:
	Journal identifier (JOJID)	Char (10)	The JID is not provided with the *TYPE1, *TYPE2, and *TYPE3 formats. It can be used with the QJORJIDI API.

 

Database file OPEN (F OP) and database file CLOSE (F CL) journal entries

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats.
1	File name	Char (10)	The name of the file that was opened or closed. If a physical file is opened, this field and the JOOBJ field are the same. If a logical file is opened, this field contains the name of the logical file. JOOBJ field contains the name of the physical file.
11	Library name	Char (10)	The library containing the file.
21	Member name	Char (10)	The file member that was opened of closed.
31	Open options	Char (4)	Only used for file open (entry type OP). Values of the bytes follow:
31	Input	Char (1)	Whether the file was opened for input: I = File opened for input blank = Input not specified
32	Output	Char (1)	Whether the file was opened for output: O = File opened for output blank = Output not specified
33	Update	Char (1)	Whether the file was opened for update: U = File opened for update blank = Update not specified
34	Delete	Char (1)	Indicates if the file was opened for delete: D = File opened for delete blank = Delete not specified

Force data to auxiliary storage (F FD) journal entry

Relative offset	Field	Format	Description
Specific values for this entry type:
	Job name (JOJOB)	Char (10)	Blank if the entry is written during IPL or vary on of an independent disk pool.
	Job number (JONBR)	Zoned (6,0)	Zero if entry is written during IPL or vary on of an independent disk pool.
	Program name (JOPGM)	Char (10)	Blank if the entry is written during IPL or vary on of an independent disk pool.

Integrated file system begin create (B B0) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object name offset	Bin (32)	The offset from the beginning of the entry-specific data to the beginning of the Object name field.
5	Object type	Char (7)	The object type that was created.
12	Start journaling indicator	Char (1)	Indicates whether journaling will be started. Y = Journaling will be started blank = Journaling will not be started
13	Reserved	Bin (32)	Reserved. This field is set to zero.
17	Object name	Char (*)	See the Object name table for the layout of this field.

Integrated file system bytes cleared, after-image (B B6) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object FID	Char (16)	The file identifier of the object.
17	Data length	Bin (64)	The length of the data.
25	Offset	Bin (64)	The offset to begin write of hex zeros (clear).
33	Reserved	Char (16)	Reserved. Set to zeros.

Integrated file system change audit attribute (B AA) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Entry type	Char (1)	The type of entry is as follows: D = Changed DLO authority O = Changed object authority
2	Object name	Char (10)	The name of the object for which the auditing attributes were changed. *N if the object is not in a library.
12	Library name	Char (10)	The name of the library for the object. *N if the object is not in a library.
22	Object type	Char (8)	The type of object.
30	Auditing value	Char (10)	The new value specified on the Change Auditing Value CHGAUD command.
40	Reserved	Char (135)	Reserved. This field is set to blanks.
175	Object name CCSID	Bin (31)	The coded character set identifier (CCSID) for the object name.
179	Reserved	Char (8)	Reserved. This field is set to blanks.
187	Parent FID	Char (16)	The file identifier of the parent directory.
203	Object FID	Char (16)	The file identifier of the object.

 

Integrated file system change object authority (B OA) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Entry type	Char (1)	The type of entry. A = Change authorization.
2	Object name	Char (10)	The object name. *N if the object is not in a library.
12	Library name	Char (10)	The library name. *N if the object is not in a library.
22	Object type	Char (8)	The type of object.
30	User name	Char (10)	The name of the user profile whose authorization is being granted or revoked.
40	Authorization list name	Char (10)	The name of the authorization list.
50	Object existence authority	Char (1)	Y = User has *OBJEXIST authority to the object. blank = User does not have *OBJEXIST authority to the object.
51	Object management authority	Char (1)	Y = User has *OBJMGT authority to the object. blank = User does not have *OBJMGT authority to the object.
52	Object operational authority	Char (1)	Y = User has *OBJOPR authority to the object. blank = User does not have *OBJOPR authority to the object.
53	Authorization list management	Char (1)	Blank if user does not authorization list management to the object.
54	Authorization list *PUBLIC authority	Char (1)	Y = User has *PUBLIC authority to the object. blank = User does not have *PUBLIC authority to the object.
55	Read authority	Char (1)	Y = User has *READ authority to the object. blank = User does not have *READ authority to the object.
56	Add authority	Char (1)	Y = User has *ADD authority to the object. blank = User does not have *ADD authority to the object.
57	Update authority	Char (1)	Y = User has *UPD authority to the object. blank = User does not have *UPD authority to the object.
58	Delete authority	Char (1)	Y = User has *DLT authority to the object. blank = User does not have *DLT authority to the object.
59	Exclude authority	Char (1)	Y = User has *EXCLUDE authority to the object. blank = User does not have *EXCLUDE authority to the object.
60	Execute authority	Char (1)	Y = User has *EXECUTE authority to the object. blank = User does not have *EXECUTE authority to the object.
61	Object alter authority	Char (1)	Y = User has *OBJALTER authority to the object. blank = User does not have *OBJALTER authority to the object.
62	Object reference	Char (1)	Y = User has *OBJREF authority to the object. blank = User does not have *OBJREF authority to the object.
63	Reserved	Char (4)	Reserved. Set to blanks.
67	Operation type	Char (3)	Possible values are: GRT = Grant RPL = Grant with replace RVK = Revoke
70	Reserved	Char (149)	Reserved. Set to blanks.
19	Object name CCSID	Bin (31)	The coded character set identifier (CCSID) for the object name.
223	Reserved	Char (8)	Reserved. Set to blanks.
231	Parent FID	Char (16)	The file identifier of the parent directory. This field is not set or used.
247	Object FID	Char (16)	The file identifier of the object.

Integrated file system change object owner (B OO) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Entry type	Char (1)	The type of entry. A = Change owner
2	Object name	Char (10)	The object name. *N if object is not in a library.
12	Library name	Char (10)	The library name. *N if object is not in a library.
22	Object type	Char (8)	The object type.
30	Old owner	Char (10)	The old owner.
40	New owner	Char (10)	The new owner.
50	Reserved	Char (143)	Reserved. Set to blanks.
193	Object name CCSID	Bin (31)	The coded character set identifier (CCSID) for the object name.
197	Reserved	Char (8)	Reserved. Set to blanks.
205	Parent FID	Char (16)	The file identifier of the parent directory.
221	Object FID	Char (16)	The file identifier of the object.

Integrated file system change primary group (B OG) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Entry type	Char (1)	Type of entry A = Change primary group profile
2	Object name	Char (10)	The object name. *N if object is not in a library.
12	Library name	Char (10)	The library name. *N if object is not in a library.
22	Object type	Char (8)	The type of object.
30	Old primary group	Char (10)	The old primary group.
40	New primary group	Char (10)	The new primary group.
50	Object existence authority	Char (1)	Y = New primary group has *OBJEXIST authority to the object. blank = New primary group does not have *OBJEXIST authority to the object.
51	Object management authority	Char (1)	Y = New primary group has *OBJMGT authority to the object. blank = New primary group does not have *OBJMGT authority to the object.
52	Object operational authority	Char (1)	Y = New primary group has *OBJOPR authority to the object. blank = New primary group does not have *OBJOPR authority to the object.
53	Object alter authority	Char (1)	Y = New primary group has *OBJALTER authority to the object. blank = New primary group does not have *OBJALTER authority to the object.
54	Object reference authority	Char (1)	Y = New primary group has *OBJREF authority to the object. blank = New primary group does not have *OBJREF authority to the object.
55	Reserved	Char (10)	Reserved. Set to blanks.
65	Authorization list management	Char (1)	Blank if new primary group does not authorization list management to the object.
66	Read authority	Char (1)	Y = New primary group has *READ authority to the object. blank = New primary group does not have *READ authority to the object.
67	Add authority	Char (1)	Y = New primary group has *ADD authority to the object. blank = New primary group does not have *ADD authority to the object.
68	Update authority	Char (1)	Y = New primary group has *UPD authority to the object. blank = New primary group does not have *UPD authority to the object.
69	Delete authority	Char (1)	Y = New primary group has *DLT authority to the object. blank = New primary group does not have *DLT authority to the object.
70	Execute authority	Char (1)	Y = New primary group has *EXECUTE authority to the object. blank = New primary group does not have *EXECUTE authority to the object.
71	Reserved	Char (10)	Reserved. Set to blanks.
81	Exclude authority	Char (1)	Y = New primary group has *EXCLUDE authority to the object. blank = New primary group does not have *EXCLUDE authority to the object.
82	Revoke previous primary group authority	Char (1)	Y = The previous primary group authority to the object was revoked. blank = The previous primary group authority to the object was not revoked.
83	Reserved	Char 143	Reserved. Set to blanks.
226	Object name CCSID	Bin (31)	The coded character set identifier (CCSID) for the object name.
230	Reserved	Char (8)	Reserved. Set to blanks.
238	Parent FID	Char (16)	The file identifier of the parent directory.
254	Object FID	Char (16)	The file identifier of the object.

Integrated file system created object authority (B B7) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object FID	Char (16)	The file identifier of the created object.
17	Number of authorities	Bin (32)	The number of private authorities in this entry.
21	Offset to object name	Bin (32)	The offset from the beginning of the entry-specific data to the beginning of the Object name field.
25	Offset to path name	Bin (32)	The offset from the beginning of the entry-specific data to the beginning of the Path name field.
29	Offset to authority information	Bin (32)	The offset from the beginning of the entry-specific data to the beginning of the Authority information field.
33	Format indicator	Char (1)	The format indicator is set to the following: 0 = The original layout of this journal entry (FORMAT1)
34	Reserved	Char (15)	Reserved. Set to zeros.
*	Object name	Char (*)	See the Object name table for the layout of this field.
*	Path name	Char (*)	See the Path name table for the layout of this field.
*	Authority information	Char (*)	The array of private authority information that has been set for the created object. See the Private authority table for the layout of one array element in this field. If the incomplete data indicator is off, the information is a character string. Otherwise, it is a pointer to the actual data. See Working with pointers in journal entries for more information.

 

Integrated file system create-summary (B B1) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Offset to name	Bin (32)	The offset from the beginning of the entry-specific data to the beginning of the Object name field.
5	Offset to path name	Bin (32)	The offset from the beginning of the entry-specific data to the beginning of the Path name field.
9	Offset to symbolic link contents field.	Bin (32)	The offset from the beginning of the entry-specific data to the beginning of the Symbolic link contents field.
13	Object type	Char (7)	The object type that was created.
20	Scan attribute	Char (1)	If the new object is a stream file (*STMF), this field is the scan (QP0L_ATTR_SCAN) attribute as described in the Set Attributes (Qp0lSetAttr()) API. If the new object is a directory (*DIR), this field is the create object scanning (QP0L_ATTR_CRTOBJSCAN) attribute of the Qp0lSetAttr()) API.
21	File ID of object	Char (16)	The new object file identifier.
37	Owner name	Char (10)	The user profile name of the owner.
47	Group name	Char (10)	The primary group profile name.
57	Auditing value	Char (10)	The auditing value of the new object.
67	Object CCSID	Bin (16)	The coded character set identifier (CCSID) for the object.
69	Owner private authority	Char (12)	Private authorities assigned to the owner. See the Private authority information table.
81	Primary group private authority	Char (12)	Private authorities assigned to the primary group. See the Private authorities for specified profile table.
93	*PUBLIC private authority	Char (12)	Private authorities assigned to the *PUBLIC. See the Private authorities for specified profile table..
105	Authorization list name	Char (10)	The authorization list name for the new object.
115	Authorization list *PUBLIC	Char (1)	The authorization List *PUBLIC authority. Possible values are Y or blank.
116	Format indicator	Char (1)	The format indicator is set to one of the following values: 0 = The original layout of this journal entry (FORMAT1) 1 = The layout of FORMAT1 plus the Device id field is set appropriately (FORMAT2) 2 = The layout for all of FORMAT2 plus the following fields are set appropriately (FORMAT3) Scan attribute Create object auditing S_ISVTX value S_ISUID value S_ISGID valuemy first point For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API.
117	PC read-only	Char (1)	The PC read Only flag. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API.
118	PC hidden	Char (1)	The PC hidden flag. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API.
119	PC system	Char (1)	The PC System file flag. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API.
120	PC changed	Char (1)	The PC changed flag. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API..
121	Journal information	Char (36)	The journaling information for the new object. This field indicates if journaling is now active on the new object. If so, it also contains the information the information used to start journaling. See the Journal information table for the layout of this field.
157	Device ID	Bin (64)	This field is only valid when the object type is *CHRSF.
165	Create object auditing	Char (10)	The create object auditing value. This value only applies to directories (*DIR).
175	S_ISVTX value	Char (1)	The restricted rename and unlink (S_ISVTX) mode bit. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API.
176	S_ISUID value	Char (1)	The S_ISUID mode bit. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API.
177	S_ISGID value	Char (1)	The S_ISGID mode bit. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API.
178	Object name	Char (*)	See the Object name table for the layout of this field.
*	Path name	Char (*)	See the Path name table for the layout of this field.
*	Symbolic link contents	Char (*)	See the Symbolic link contents table for the layout of this field.

 

Integrated file system end journaling for object (B ET) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object FID	Char (16)	The file identifier of the object.

Integrated file system link to existing object (B B2) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object FID	Char (16)	The file identifier of the existing object.
17	Link offset	Bin (32)	The offset from beginning of this entry-specific data to the beginning of the Link name field.
21	Path offset	Bin (32)	The offset from beginning of this entry-specific data to the beginning of the Path name field.
25	Start journaling	Char (1)	The start journaling indicator. Y = Journaling starts on the existing object as a result of this operation. The Journal information field has start journaling information. blank = Journaling is not started on the existing object as a result of this operation. The Journal information field contains all hex zeros.
26	Summary	Char (1)	The summary record indicator. Y = This journal entry was deposited after the actual operation was completed. If the Start journaling field is Y, then the Journal information field contains the actual information related to starting journaling on the target object. If the Start journaling field is blank, then the Journal information field contains all hex zeros. blank = This journal entry was deposited before the actual operation was attempted. If the Start journaling field is Y, then the Journal information field contains the journal information inherited from its new parent. This information is used to attempt a start journaling operation. If the Start journaling field is blank, then the Journal information field contains all hex zeros.
27	Reserved	Char (2)	Reserved. Set to zero.
29	Journal information	Char (36)	The journaling information for the new object. This field is defined in the Journal information table.
65	Link name	Char (*)	The name of the new link to the object. See the Object name table for the layout of this field.
*	Path name	Char (*)	The existing object path name. If this B2 journal entry was deposited as a result of a rollback of a B5 entry, then this will actually be the path to the parent directory to which the link is being added. See the Path name table for the layout of this field.

 

Integrated file system object attribute changed (B FA) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object FID	Char (16)	The file identifier of the object.
17	Parent FID	Char (16)	The file identifier of the parent directory.
33	Object type	Char (7)	The type of object.
40	Reserved	Char (9)	Reserved. This field is set to hex zeros.
49	Next attribute offset	Bin (32)	The offset to the next attribute. All of the offsets 49, 53, 57, 61, and 65 will repeat for each attribute set for this entry.
53	Attribute identifier	Bin (32)	The attribute identifier. See the Set Attributes (Qp0lSetAttr()) API for information about the structure and content of this field. All of the offsets 49, 53, 57, 61, and 65 will repeat for each attribute set for this entry.
57	Attribute data size	Char (32)	Size of attribute data in bytes. All of the offsets 49, 53, 57, 61, and 65 will repeat for each attribute set for this entry.
61	Reserved	Char (4)	Reserved. All of the offsets 49, 53, 57, 61, and 65 will repeat for each attribute set for this entry.
65	Changed data	Char (*)	The data that was changed. All of the offsets 49, 53, 57, 61, and 65 will repeat for each attribute set for this entry.

 

Integrated file system object closed (B CS) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Open flags	Bin (31)	Open flags. See the Open API for a description of these flags.

 

Integrated file system object deleted (B BD) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object FID	Char (16)	The file identifier of the object.

 

Integrated file system object forced (B FC) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object FID	Char (16)	The file identifier of the object.

 

Integrated file system object opened (B OF) journal entries

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Open flags	Bin (31)	Open flags. See the Open API for a description of these flags.

 

Integrated file system object truncated (B TR) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object FID	Char (16)	The file identifier of the object.
17	Old size	Bin (64)	The size of the object in bytes before it was truncated.
25	New size	Bin (64)	The size of the object in bytes after it was truncated.

 

Integrated file system remove link (link) (B B5) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object FID	Char (16)	The file identifier of the existing object.
17	Parent FID	Char (16)	The file identifier of the object parent directory.
33	Link offset	Bin (32)	The offset from beginning of this entry-specific data to the beginning of the Link name field.
37	Parent path offset	Bin (32)	The offset from beginning of this entry-specific data to the beginning of the Parent path field.
41	Parent directory JID	Char (10)	The journal identifier of parent directory.
51	Object type	Char (7)	The type of the object.
58	Reserved	Char (3)	Reserved. Set to zero.
61	Internal data offset	Bin (32)	The offset from beginning of this field to the beginning of Internal data field.
65	Link name	Char (*)	The name of link. See the Object name layout of this field.
*	Parent path	Char (*)	The path to the parent that used to contain this link. See the Path name layout of this field.
*	Internal data	Char (*)	Internal data.

 

Integrated file system remove link (parent directory) (B B4) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object FID	Char (16)	The file identifier of the existing object.
17	Parent FID	Char (16)	The parent directory of the link file identifier.
33	Link offset	Bin (32)	The offset from beginning of this entry-specific data to the beginning of the Link name field.
37	Object JID	Char (10)	The journal identifier of the object.
47	Object type	Char (7)	The type of the object.
54	Reserved	Char (7)	Reserved. Set to zero.
61	System offset	Bin (32)	The offset from beginning of this entry-specific data to the beginning of Internal data.
65	Link name	Char (*)	The name of link. See the Object name layout of this field.
*	Internal data	Char (*)	Internal data.

 

Integrated file system rename file identifier (B RN) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Old FID	Char (16)	The file identifier of the object before the rename operation.
17	Reserved	Char (14)	Reserved. Set to blanks.
31	New FID	Char (16)	The file identifier of the object after the rename operation.
47	Reserved	Char (14)	Reserved. Set to blanks.

Integrated file system rename, move object (B B3) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object FID	Char (16)	The file identifier of the object for the renamed link.
17	Source parent FID	Char (16)	The file identifier of the source object directory.
33	Target parent FID	Char (16)	The file identifier of the target object directory.
49	Replaced object FID	Char (16)	The file identifier of the object that was replaced by this operation. This field contains all hex zeros if no object was replaced.
65	Source offset	Bin (32)	The offset from beginning of this entry-specific data to the beginning of the Source name field.
69	Target offset	Bin (32)	The offset from beginning of this entry-specific data to the beginning of the Target name field.
73	Source parent offset	Bin (32)	The offset from beginning of this entry-specific data to the beginning of the Source parent path field.
77	Target parent offset	Bin (32)	The offset from beginning of this entry-specific data to the beginning of the Target parent path field.
81	Start journaling	Char (1)	The start journaling indicator: Y = Journaling starts on the existing object as a result of this operation. The Journal information field contains the information used to start journaling. blank = Journaling does not start on the existing object as a result of this operation. The Journal information field contains all hex zeros.
82	Summary	Char (1)	The summary record indicator: Y = This journal entry was deposited after the actual operation was completed. If the Start journaling field is also Y, then the Journal information field contains the actual information related to starting journaling on the target object. If the Start journaling field is blank, then the Journal information record will contain all hex zeros. blank = This journal entry was deposited before the actual operation was attempted. If Start journaling is Y, then the Journal information field contains the journal information inherited from its new parent. That information is used to attempt a start journaling operation. If the Start journaling field is blank, then the Journal information field contains all hex zeros.
83	Replace	Char (1)	The replace indicator. Indicates if the target was replaced as a result of this operation. Y = Indicates that the target was replaced. blank = Indicates that the target did not exist before this operation.
84	Journal entry flags	Bin (32)	The fields for journal entry flags are as follows: Both journaled Bit(0)--1 = Indicates that this entry is one of a pair of B3 entries sent for this move operation. This occurs when both the source and target parent directories are journaled at the time of the move operation. Source entry Bit(1)--1 = Indicates that this entry was deposited because the source parent was journaled. Reserved Bits(2-7)--Reserved. Set to zero.
88	Reserved	Char (4)	Reserved field.
92	Journal information	Char (37)	The journaling information for the new object. This field is defined in Journal information.
129	System offset	Bin (32)	The offset from beginning of this entry-specific data to the beginning of Internal data field.
133	Source name	Char (*)	The name of object being renamed or moved. See the Object name layout of this field.
*	Target name	Char (*)	The new name of object after being renamed or moved. See the Object name layout.
*	Source parent path	Char (*)	The path to the parent directory from which the object previously belonged. See Path name for the layout of this field.
*	Target parent path	Char (*)	The path to the parent directory to which the object now belongs. See Path name for the layout of this field.
*	Internal data	Char (*)	Internal data.

 

Integrated file system storage for object freed (B FF) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object FID	Char (16)	The file identifier of the object.
17	Old size	Bin (64)	The old size of the object.

Integrated file system write, after-image (B WA) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object FID	Char (16)	The file identifier of the object.
17	Data length	Bin (64)	Length of the data.
25	Offset	Bin (64)	The offset to begin write.
33	Reserved	Char (16)	Reserved.
49	Data	Char (*)	The actual data that was written. If the incomplete data indicator is off, the information is a character string. Otherwise, it is a pointer to the actual data. See Work with pointers in journal entries for more information.

 

Identity Value (F IT) journal entries

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Version	Bin(15)	Version number
3	Identity Value	DECIMAL(31,0)	The last identity value allocated in the current CACHE

INZPFM (F IZ) journal entry

Relative offset	Field	Format	Description
Specific values for this entry type:
	Count or relative record number (JOCTRR)	Zoned (10,0)	Contains the number of records specified on the TOTRCDS parameter of the Initialize Physical File Member (INZPFM) command.
	Flag (JOFLAG)	Char (1)	Indicates the type of record initialization that was done: 0 = *DFT (default) 1 = *DLT (delete)
Entry-specific data. This data appears as one field in the standard output formats:
1	Entry-specific data		If the member is initialized with default records, this field contains the default record image.

IPL (J IA, J IN) and in-use (B OI, C BA, D ID, E EI, F IU, I DA, J JI, Q QI) journal entries

Relative offset	Field	Format	Description
Specific values for this entry type:
	Time stamp (JOTIME)	Zoned (6,0)	The timestamp created at IPL is read from the battery-powered clock. If the battery-powered clock cannot be read, the time is that of the system power down, not the time of the IPL, because the system time has not yet been updated at the time the journal entry is written.
	Flag (JOFLAG)	Char (1)	For in-use entries, indicates whether the object was synchronized with the journal: 0 = Object was synchronized with journal 1 = Object was not synchronized with journal

 

Journal code R, all journal entry types except IL

Relative offset	Field	Format	Description
Specific values for this entry type:
	Flag (JOFLAG)	Char (1)	Whether a before-image is present1: 0 = Before-image is not present. If before-images are being journaled, this indicates that an update operation or delete operation is being requested for a record that has already been deleted. 1 = Before-image is present.
	Journal identifier (JOJID)	Char (10)	The JID is not provided with the *TYPE1, *TYPE2, and *TYPE3 formats. It can be used with the QJORJIDI API.
Entry-specific data. This data appears as one field in the standard output formats:
1	Entry-specific data	Char (*)	After-image of the record for entry types PT, PX, UP, or UR. Before-image of the record for entry types UB, DL, BR, or DR if before-images are being journaled and the record was not previously deleted.
1The flag does not apply to these entry types: PT, PX, UP, and UR.

 

Removed anchor point TBLENTLKLicense key not valid (L LK) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Product ID	Char (7)	The ID of the product whose license key was not valid.
8	License term	Char (6)	The term of the license.
14	Feature	Char (4)	The product feature code.
18	Usage limit	Zoned (6,0)	The usage limit for the product.
24	License key	Char (18)	The license key for the product.
42	Expiration date	Char (7)	The expiration date for the license key.
49	Vendor data	Char (8)	Data placed in the entry by the product vendor.
57	Processor group	Char (3)	The processor group for the license key.

Logical unit of work (C LW) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	LUW header portion	416	The header portion of the entry-specific data contains general information about the logical unit of work (LUW). The layout for the Logical unit of work (C LW) journal entry-header record describes the contents of the header portion.
After the header portion	LUW local portion	80	Information about local resources that participated in the LUW. The entry might have 0 to n records for local locations. Each local record is 48 characters long. The layout for the Logical unit of work (C LW) journal entry - local record describes the local record.
After the local portion	LUW API portion	112	Information about API resources that participated in the LUW. The entry might have 0 to n records for API resources. Each API resource record is 80 characters long. The layout for the 0 Logical unit of work (C LW) journal entry - API record describes the API record.
After the API portion	LUW DDL portion	96	Information about DDL resources that participated in the LUW. The entry might have 0 to n records for DDL resources. Each DDL resource record is 80 characters long. The layout for the Logical unit of work (C LW) journal entry - DDL record describes the DDL record.
After the DDL portion	LUW remote portion	128	Information about remote locations that participated in the LUW. The entry might have 0 to n records for remote locations. Each remote location record is 128 characters long. The layout for the Logical unit of work (C LW) journal entry - RMT record describes the remote record.
After the remote portion	LUW DDM portion	96	Information about DDM resources that participated in the LUW. The entry might have 0 to n records for DDM resources. Each DDM resource record is 96 characters long. The layout for the Logical unit of work (C LW) journal entry - DDM record describes the DDM record.

Logical unit of work (C LW) journal entry - API record

Relative offset	Field	Format	Description
1	Record type	Char (4)	Type of record: API = API Commitment resource record
5	Record length	Bin (15)	Length of record. Currently 80 for API record.
7	Record position	(4) 1	This identifies the position in the LUW journal entry where this record starts. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains this record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains this record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where this record starts within this journal entry. This is the number of bytes past the beginning of the entry where this record starts. For example, 0 means the first byte in the entry.
11	Resource location position	(4)1	This identifies the position in the LUW journal entry where the LCL record starts for this API resource's location. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains the record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains the record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where the record starts within this journal entry. This is the number of bytes past the beginning of the entry where the record starts. For example, 0 means the first byte in the entry.
15	Next resource position	(4)1	This identifies the position in the LUW journal entry where the next API or DDL record starts for this API resource's location. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains the record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains the record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where the record starts within this journal entry. This is the number of bytes past the beginning of the entry where the record starts. For example, 0 means the first byte in the entry. Position 0 0 indicates that this is the last resource for this API resource's location.
19	API resource	Char (10)	Name of API resource.
29	API program	Char (20)	Name of the exit program for the API resource: Char (10): exit program name Char (10): exit program library
49	Journal	Char (20)	Journal related to the location for this resource: Char (10): Journal name (blank if this resource belongs to the location with no journal) Char (10): Journal library (blank if this resource belongs to the location with no journal)
69	Commit cycle ID	Bin (31)	The commit cycle identifier for the journal. This is 0 if this resource belongs to the location with no journal. This is -1 if the actual commit cycle identifier value is larger than 2 147 483 647. The Commit cycle ID Long field always contains the correct value.
73	Commit protocol	Char (1)	The commit protocol for this resource: 2 = This is a two-phase resource (API resources are always two-phase resources).
74	Resource usage	Char (2)	The currently allowed access for this resource. The allowed access for some resources can change from one LUW to another depending on whether one-phase resources are registered: RO = This resource is currently read-only. Updates were not made during the LUW. UP = This resource is currently able to be updated. Updates might or might not have been made during the LUW.
76	API state	Char (2)	Indicates whether the API resource was committed or rolled back successfully: CS = This resource was committed successfully. RS = This resource was rolled back successfully. CF = An attempt to commit this resource failed. RF = An attempt to rollback this resource failed.
78	API last agent flag	Char (1)	Whether this resource is to be selected as the last agent during all commit requests: Y = This resource is to be selected as the last agent. N = This resource is not to be selected as the last agent.
79	Allow remote resources	Char (1)	Whether remote resources are allowed to participate in a LUW with this resource: Y = Remote resources are allowed with this resource. N = Remote resources are not allowed with this resource.
80	Save while active flag	Char (1)	Whether this resource will hold out a save-while-active request until a commitment boundary is reached: Y = This resource will hold save-while-active requests. N = This resource will not hold save-while-active requests.
81	Commit cycle ID long	Zoned (20,0)	The commit cycle identifier for the journal. This is 0 if this resource belongs to the location with no journal.
101	Reserved	Char (12)	Reserved for future use.
1The format for this field is in the description.

 

Logical unit of work (C LW) journal entry - DDL record

Relative offset	Field	Format	Description
1	Record type	Char (4)	Type of record: DDL = SQL Object Change record.
5	Record length	Bin (15)	Length of record. Currently 624 for DDL record.
7	Record position	(4)1	This identifies the position in the LUW journal entry where this record starts. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains this record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains this record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where this record starts within this journal entry. This is the number of bytes past the beginning of the entry where this record starts. For example, 0 means the first byte in the entry.
11	Resource location position	(4)1	This identifies the position in the LUW journal entry where the LCL record starts for this DDL resource's location. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains the record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains the record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where the record starts within this journal entry. This is the number of bytes past the beginning of the entry where the record starts. For example, 0 means the first byte in the entry.
15	Next resource position	(4)1	This identifies the position in the LUW journal entry where the next API or DDL record starts for this DDL resource's location. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains the record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains the record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where the record starts within this journal entry. This is the number of bytes past the beginning of the entry where the record starts. For example, 0 means the first byte in the entry. Position 0 0 indicates that this is the last resource for this DDL resource's location.
19	DDL resource information	Char (29)	Object identification and operation performed on object: Char (10): First 10 characters of object name. The object name field always contains the full object name. Char (10): Object library name Char (7): Object type (*FILE, *LIB or *SQLPKG) Char (2): Object operation The possible object operations and their meanings are the following: AC = Add PF Constraint CC = Create Collection CF = Create File CG = Create Program CM = Create Member CP = Create SQL Package CS = Create Service Program CT = Create User Defined Type DC = Delete Collection DF = Delete File DG = Drop Program DP = Delete SQL Package DS = Drop Service Program DT = Drop User Defined Type FC = Change File FR = Rename File GF = Grant Files GG = Grant Program GP = Grant to SQL Package GR = Grant Java™ Routine GS = Grant Service Program GT = Grant User Defined Type OP = COMMENT ON SQL Package OT = COMMENT User Defined Type RC = Remove PF Constraint RG = Revoke Program RF = Revoke Files RP = Revoke from SQL Package RR = Revoke Java Routine RS = Revoke Service Program RT = Revoke User Defined Type TA = Add PF Trigger TR = Remove PF Trigger UL = Unlink Datalink XF = Transfer Files
48	Reserved	Char (1)	Reserved for future use.
49	Journal	Char (20)	Journal related to the location for this resource: Char (10): Journal name (blank if this resource belongs to the location with no journal) Char (10): Journal library (blank if this resource belongs to the location with no journal)
69	Commit cycle ID	Bin (31)	The commit cycle identifier for the journal. This is 0 if this resource belongs to the location with no journal. This is -1 if the actual commit cycle identifier value is larger than 2 147 483 647. The Commit cycle ID Long field always contains the correct value.
73	Commit protocol	Char (1)	The commit protocol for this resource: 2 = This is a two-phase resource (DDL resources are always two-phase resources).
74	DDL state	Char (2)	Indicates whether the DDL resource was committed or rolled back successfully: CS = This resource was committed successfully. RS = This resource was rolled back successfully. CF = An attempt to commit this resource failed. RF = An attempt to rollback this resource failed.
76	Commit cycle ID long	Zoned (20,0)	The commit cycle identifier for the journal. This is 0 if this resource belongs to the location with no journal.
96	Object name	Char (288)	The full object name.
384	Reserved	Char (1)	Reserved for future use.
1The format for this field is in the description.

 

Logical unit of work (C LW) journal entry - DDM record

Relative offset	Field	Format	Description
1	Record type	Char (4)	Type of record: DDM = Remote Database file record.
5	Record length	Bin (15)	Length of record. Currently 96 for DDM record.
7	Record position	(4) 1	This identifies the position in the LUW journal entry where this record starts. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains this record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains this record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where this record starts within this journal entry. This is the number of bytes past the beginning of the entry where this record starts. For example, 0 means the first byte in the entry.
11	Resource location position	(4) 1	This identifies the position in the LUW journal entry where the RMT record starts for this DDM file's location. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains the record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains the record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where the record starts within this journal entry. This is the number of bytes past the beginning of the entry where the record starts. For example, 0 means the first byte in the entry.
15	Next resource position	(4)1	This identifies the position in the LUW journal entry where the next DDM record starts for this DDM file's location. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains the record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains the record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where the record starts within this journal entry. This is the number of bytes past the beginning of the entry where the record starts. For example, 0 means the first byte in the entry. Position 0 0 indicates that this is the last resource for this DDM file's location.
19	DDM file	Char (20)	Name of the DDM file and library for the open remote file: Char (10): DDM file name Char (10): DDM file library name
29	Remote position information	Char (54)	Identification of the remote location and communication information for this resource's location: Char (10): Remote position name Char (10): Device name Char (10): Mode Char (8): Remote network ID Char (8): Conversation correlator network ID Char (8): Transaction program name
93	Open flag	Char (1)	Whether the DDM file was open or closed when this LUW ended: O = The DDM file was open. C = The DDM file was closed.
94	Commit protocol	Char (1)	The commit protocol for this resource: 1 = This is a one-phase resource. 2 = This is a two-phase resource.
95	Resource usage	Char (2)	The currently allowed access for this resource. The allowed access for some resources can change from one LUW to another depending on whether one-phase resources are registered: RO = This resource is currently read-only. Updates were not made during the LUW. UP = This resource is currently able to be updated. Updates might or might not have been made during the LUW. This does not indicate whether updates were actually made during the LUW. It only indicates whether updates are allowed, given the other resources currently registered.
1The format for this field is in the description.

 

Logical unit of work (C LW) journal entry-header record

Relative offset	Field	Format	Description
1	Record type	Char (4)	Type of record: HDR = Header record.
5	Record length	Bin (15)	Length of record. Currently 400 for HDR record.
7	Record position	(4)1	This identifies the position in the LUW journal entry where this record starts. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains this record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains this record (1 for the first, 2 for the second, and so forth). Note that this is not the actual journal entry sequence number. Bin (15): The offset where this record starts within this journal entry. This is the number of bytes past the beginning of the entry where this record starts. For example, 0 means the first byte in the entry. Because they always start at the beginning of the journal entry, this offset is always 0 for HDR records.
11	Number of journal entries	Bin (15)	The number of actual journal entries sent for this LUW journal entry. This is 1 unless the LUW journal entry is greater than 32K-1 bytes.
13	position with no journal position	(4) 1	This identifies the position in the LUW journal entry where the LCL record starts for the local location with no journal. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains the record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains the record (1 for the first, 2 for the second, and so forth). Note that this is not the actual journal entry sequence number. Bin (15): The offset where the record starts within this journal entry. This is the number of bytes past the beginning of the entry where the record starts. For example, 0 means the first byte in the entry. Position 0 0 means that there is no local location that does not have a journal.
17	First location with journal position	(4)1	This identifies the position in the LUW journal entry where the LCL record starts for the first local location with a journal. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains the record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains the record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where the record starts within this journal entry. This is the number of bytes past the beginning of the entry where the record starts. For example, 0 means the first byte in the entry. Position 0 0 means that there are no local locations with a journal.
21	First remote location position	(4)1	This identifies the position in the LUW journal entry where the RMT record starts for the first remote location. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains the record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains the record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where the record starts within this journal entry. This is the number of bytes past the beginning of the entry where the record starts. For example, 0 means the first byte in the entry. Position 0 0 means there are no remote locations.
25	LUW operation	Char (2)	The operation that was performed to end this LUW: CM = A commit operation was performed. This does not necessarily mean that the resources were committed. In some cases a commit operation is changed to a rollback operation with respect to two-phase commit rules. RB = A rollback operation was performed. An attempt was made to roll back all resources.
27	Protected logical unit of work identifier (LUWID)	Char (41)	The format for the LUWID is: Bin (15): The total length of the LUWID not including this field Char (0 to 8): The network ID Char (1): The separator character . Char (0 to 8): The local location name Char (3): The separator characters .X' Char (12): The hex value of the instance number converted to character Char (2): The separator characters '. Char (5): The hex value of the sequence number converted to decimal
68	Unprotected logical unit of work identifier	Char (41)	The format for the LUWID for unprotected conversations is the same as for protected conversations.
109	Default journal commit cycle ID	Bin (31)	The commit cycle identifier for the default journal for this LUW. This is 0 if no commit cycle was started for this journal during this LUW. This is -1 if the actual commit cycle identifier value is larger than 2 147 483 647. The Default Journal Commit cycle ID Long field always contains the correct value.
113	Commitment definition name	Char (10)	The name of the commitment definition for which this LUW took place.
123	Commitment definition identifier	Char (10)	The commitment definition identifier of the commitment definition. This is not useful to the user.
133	Qualified job name	Char (26)	The job that created the commitment definition.
159	Reserved	Char (1)	Reserved for future use. Currently always blank.
160	Commitment definition scope	Char (1)	The scope of the commitment definition: A = Activation group level commitment definition. E = Explicitly named commitment definition. J = JOB commitment definition.
161	Activation group mark	Bin (31)	The activation group mark for the commitment definition: 0 = This is the *JOB or an explicitly named commitment definition. 2 = This is the *DFTACTGRP commitment definition. # = The number of the activation group for this activation group level commitment definition.
165	Notify object	Char (37)	The notify object for the commitment definition: Char (10) - Object name Char (10) - Object library Char (10) - Object member (blank if object is not a file) Char (7) - Object type (*MSGQ, *DTAARA or *FILE)
202	Default journal	Char (20)	The default journal for the commitment definition: Char (10): Journal name Char (10): Journal library
222	Initiation type	Char (1)	Whether this commit or rollback operation was initiated by the user or by the system: E = Explicit commit or rollback operation initiated by the user. I = Implicit commit or rollback operation due to activation group end, job end, or system end. If the LUW was finished after a system end, this is set to I, even if an explicit commit or rollback operation was running at the time the system ended.
223	LUW end status	Char (1)	Indication of when this LUW ended with respect to the job that created the commitment definition for which this LUW took place: N = The LUW ended while the job was running normally. E = The LUW ended during job end. This means that the LUW was still pending when a request was made to end the job. If the requested operation is CM, then a commit request had started before the request to end the job and was finished during the job-end phase. I = The LUW ended during the IPL following a system end. If the requested operation is CM, then a commit request was started before the system end and was finished during the IPL. P = The LUW ended after the IPL following a system end. In this case, the requested operation is CM and the LUW was prepared pending the commit/rollback decision from the initiator or last agent when the system ended. During the IPL, local resources were brought back to a prepared state in a system database server job. After resynchronization was performed to learn the commit/rollback decision, the LUW ended by committing or rolling back the local resources in that same system database server job.
224	Sync-point role	Char (1)	The sync-point role played by this location during a commit operation: I = Initiator: the root of the sync-point tree. C = Cascaded initiator: an intermediate location in the sync-point tree. A = Agent: a leaf location in the sync-point tree.C tree. blank = This LUW ended in a rollback request.
225	Partner role	Char (1)	The partner role played by this location during a commit: I = Initiator: the root of the sync-point tree. N = Not-last agent: a prepare request was sent to this location during the prepare wave. L = Last agent: a prepare request was not sent to this location during the prepare wave. Instead, a request was made to this location during the committed wave to attempt a full commit operation before reporting results back to its initiator. blank = This LUW ended in a rollback request
226	LUW disposition	Char (2)	The overall disposition of the LUW: RO = This location and all downstream locations voted read-only. These resources were not committed or rolled back because they were not changed during the LUW. It is not known whether the other locations in the sync-point tree committed or rolled back. CM = All resources committed. No errors have been detected to this point. If the Resync In Progress indicator field is N, the LUW has completely committed. Otherwise, resynchronization is still going on to assure this location that other locations committed completely. CF = An attempt was made to commit all resources, but one or more errors have occurred. The job log, QHST, and QSYSOPR *MSGQ can be checked to determine the errors. RB = All resources rolled back successfully. RF = An attempt was made to roll back all resources, but one or more errors have occurred. The job log, QHST, and QSYSOPR *MSGQ can be checked to determine the errors. HD = Heuristic damage has occurred. This means one of two things: Some of the resources at this location or downstream locations committed while others rolled back because an operator performed a heuristic commit operation or rollback operation. An unexpected error occurred while committing or rolling back resources at this location or downstream locations due to a hardware or software problem. When heuristic damage occurs, the following LUW journal entry records can be checked to learn the status of the changes made during the LUW to individual resources: LCL = The Record I/O State field indicates the status of the record I/O performed on files journaled to the journal related to that location. API = The API State field indicates the status of that API Commitment resource. DDL = The DDL State field indicates the status of that SQL Object Change. RMT = The Resource State field indicates the status of the resources at the remote location.
228	Heuristic operation indicator	Char (1)	Whether a heuristic commit or rollback operation occurred at this location while a commit request was being performed for this LUW: blank = No heuristic operation occurred. C = A heuristic commit operation occurred. R = A heuristic rollback operation occurred. A heuristic commit operation or rollback operation means that the operator took explicit action (while this location was waiting for the commit or rollback decision from the initiator or the last agent) to commit or to roll back the resources at this location and all prepared downstream locations. Heuristic operations can result in some resources committing while others roll back. The LUW Disposition field can be checked to see if this has happened (it would be HD). The Resync In Progress indicator field can also be checked. If it is O, heuristic damage might have occurred or it might still occur because the state of the resources at the locations where resynchronization is still going on is unknown. Messages are written to the history log and to the system database server job logs when the resynchronization processes complete to indicate whether damage occurred. If damage occurs, messages are also sent to the system operator when it is detected.
229	Resync in progress indicator	Char (1)	Whether resync to one or more remote locations was still ongoing when the LUW ended: N = Either no resynchronization was required during this LUW, or it was required and completed before the LUW ended. O = Resynchronization was going on with one or more of the locations. This can occur only if the WAIT_FOR_OUTCOME synchronization point option is NO, or if the LUW was interrupted by job or system end.
230	Wait for outcome	Char (1)	The value of the Wait for outcome commitment option. This indicates whether to wait for resynchronization to complete if a communication or system failure occurs during a commit or rollback. Y = Wait for outcome. L = Wait for outcome during commits initiated by this commitment definition or during commits initiated at a system that does not support presumed abort. Inherit the initiator's wait for outcome value during commits initiated at a system that supports presumed abort. N = Do not wait for outcome. U = Do not wait for outcome during commits initiated by this commitment definition or during commits initiated at a system that does not support presumed abort. Inherit the initiator's wait for outcome value during commits initiated at a system that supports presumed abort.
231	Action if problems	Char (1)	The value of the Action if problems commitment option. This indicates whether to commit or rollback when problems occur during a two-phase commit. R = Rollback if problems occur. C = Commit if problems occur.
232	Vote read-only permitted	Char (1)	The value of the Vote read-only permitted commitment option. This indicates whether this commitment definition is allowed to return a read-only vote to a remote initiator during a two-phase commit. N = Do not allow a read-only vote. Y = Allow a read-only vote.
233	Action if ENDJOB	Char (1)	The value of the Action if ENDJOB commitment option. This indicates the action to take for changes associated with the LUW when the job the LUW is a part of is ended. W = Wait to allow normal processing of the LUW to complete. R = Rollback during ENDJOB. C = Commit during ENDJOB.
234	OK to leave out	Char (1)	The value of the OK to leave out commitment option. This indicates whether this location is allowed to be left out during the next commit/rollback if no activity occurred to this location during the LUW. N = Do not leave this location out of the next commit or rollback operation. Y = It is OK to leave this location out of the next commit or rollback operation.
235	Last agent permitted	Char (1)	The value of the Last agent permitted commitment option. This indicates whether last agent optimization may be used. S = The system is allowed to select a last agent. N = The system is not allowed to select a last agent.
236	Accept vote reliable	Char (1)	The value of the Accept vote reliable commitment option. This indicates whether the vote reliable indicator received from agents during a commit operation is accepted by this location. If an agent votes reliable, and this location accepts it, control is returned to the application before the committed wave is completed for that agent. If this location does not accept vote reliable, control is returned to the application only after the LUW is completely committed or rolled back. Y = Accept the vote reliable indicator from agents during commit operations. N = Do not accept the vote reliable indicator from agents during commit operations.
237	Resolved wait for outcome value	Char (1)	This indicates the actual wait for outcome value that was used during the commit or rollback of this LUW. If the Wait for outcome commitment option is L or U, this value might have been inherited from this location's initiator. Y = Wait for outcome of resynchronization. N = Do not wait for outcome of resynchronization.
238	XA transaction manager	Char (10)	If this was an X/Open transaction, this is the name of the XA Transaction Manager that was specified on the db2xa_open API. This field will be hex zeros if this was not an XA transaction.
248	XID	Char (140)	If this was an X/Open Transaction, this is the X/Open Transaction Identifier associated with this transaction. This field will be hex zeros if this was not an X/Open transaction, or if it was an X/Open local transaction. The format of this field is as follows: Bin(31) format identifier Bin(31) global transaction identifier length Bin(31) branch qualifier length Char (128) XID value
388	Default journal commit cycle ID long	Zoned (20,0)	The commit cycle identifier for the default journal for this LUW. This is 0 if no commit cycle was started for this journal during this LUW.
408	Reserved	Char (9)	Reserved for future use.
1The format for this field is in the description.

 

Logical unit of work (C LW) journal entry - local record

Relative offset	Field	Format	Description
1	Record type	Char (4)	Type of record: LCL = Local location record.
5	Record length	Bin (15)	Length of record. Currently 48 for LCL record.
7	Record position	(4)1	This identifies the position in the LUW journal entry where this record starts. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains this record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains this record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where this record starts within this journal entry. This is the number of bytes past the beginning of the entry where this record starts. For example, 0 means the first byte in the entry.
11	Next local location position	(4) 1	This identifies the position in the LUW journal entry where the next LCL record starts. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains the record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains the record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where the record starts within this journal entry. This is the number of bytes past the beginning of the entry where the record starts. For example, 0 means the first byte in the entry. Position 0 0 indicates that this is the last local location.
15	First resource position	(4)1	This identifies the position in the LUW journal entry where the first API or DDL record starts for this location. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains the record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains the record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where the record starts within this journal entry. This is the number of bytes past the beginning of the entry where the record starts. For example, 0 means the first byte in the entry.
19	Record I/O state	Char (2)	Indicates whether the record I/O performed during this LUW for files journaled to the journal related to this location was committed or rolled back successfully: CS Record I/O for this location was committed successfully. RS = Record I/O for this location was rolled back successfully. CF = An attempt to commit record I/O for this location failed. RF = An attempt to rollback record I/O for this location failed. blank = This is the location with no journal so there is no record I/O associated with it.
21	Journal	Char (20)	Journal related to this location: Char (10): Journal name (blank if this is the location with no journal) Char (10): Journal library (blank if this is the location with no journal)
41	Commit cycle ID	Bin (31)	The commit cycle identifier for the journal. This is 0 for the location with no journal. It might be 0 for the location related to the default journal if there were no resources for that location during this LUW. This is -1 if the actual commit cycle identifier value is larger than 2 147 483 647. The Default Journal Commit cycle ID Long field always contains the correct value.
45	Default journal flag	Char (1)	Indicates whether the journal related to this location is the default journal: Y = It is the default journal. N = It is not the default journal.
46	Commit cycle ID Long	Zoned (20,0)	The commit cycle identifier for the journal. This is 0 for the location with no journal. It might be 0 for the location related to the default journal if there were no resources for that location during this LUW.
66	Reserved	Char (15)	Reserved for future use.
1The format for this field is in the description.

 

Logical unit of work (C LW) journal entry - RMT record

Relative offset	Field	Format	Description
1	Record type	Char (4)	Remote position (RMT) record.
5	Record length	Bin (15)	RMT record is currently 128.
7	Record position	(4)1	This identifies the position in the LUW journal entry where this record starts. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains this record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains this record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where this record starts within this journal entry. This is the number of bytes past the beginning of the entry where this record starts. For example, 0 means the first byte in the entry.
11	Next Rrmote location position	(4)1	This identifies the position in the LUW journal entry where the next RMT record starts. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains the record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains the record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where the record starts within this journal entry. This is the number of bytes past the beginning of the entry where the record starts. For example, 0 means the first byte in the entry. Position 0 0 indicates that this is the last remote location.
15	First resource position	(4) 1	This identifies the position in the LUW journal entry where the first DDM record starts for this location. It is made up of two numbers: Bin (15): The relative number of the journal entry that contains the record. If the LUW journal entry is greater than 32K-1 bytes, multiple entries are actually sent to the journal. This number represents which of these actual journal entries contains the record (1 for the first, 2 for the second, and so on). Note that this is not the actual journal entry sequence number. Bin (15): The offset where the record starts within this journal entry. This is the number of bytes past the beginning of the entry where the record starts. For example, 0 means the first byte in the entry. Position 0 0 indicates that there are no DDM records for this location.
19	Remote position information	Char (54)	Identification of the remote location and communication information for this location: Char (10): Remote position name Char (10): Device name Char (10): Mode Char (8): Remote network ID Char (8): Conversation correlator network ID Char (8): Transaction program name
73	Relational database name	Char (18)	The name of the relational database opened at this remote location (blank if no relational database has been opened).
91	Conversation deallocation flag	Char (1)	Whether the conversation was deallocated because of this LUW: N = This conversation is still active. Y = This conversation was deallocated because the LUW committed, the system ended, a resource failed, or an unbind was performed.
92	Commit protocol	Char (1)	The commit protocol for the resources at this location: 1 = The resources are one-phase. 2 = The resources are two-phase.
93	Resource usage	Char (2)	The currently allowed access for this resource. The allowed access for some resources can change from one LUW to another depending on whether one-phase resources are registered: RO = This resource is currently read-only. Updates were not made during the LUW. UP = This resource is currently able to be updated. Updates might or might not have been made during the LUW. This does not indicate whether updates were actually made during the LUW. It indicates only whether updates are allowed, given the other resources currently registered.
95	Resource state	Char (2)	The state of the resources at this location: CS = The resources were committed successfully. CF = An attempt to commit the resources failed. This value is only used for one-phase locations. RS = The resources were rolled back successfully. RF = An attempt to rollback the resources failed. This value is only used for one-phase locations. NC = The resources had no changes for the current transaction. FC = A communications failure occurred for this location. It is not known whether resources at the location committed or rolled back. HC = The resources were heuristically committed. HR = The resources were heuristically rolled back. HM = Heuristic damage was detected at this location. Some of the resources at the location, or locations further downstream, committed while others rolled back. ER = An unexpected error occurred while communicating with this location. This is due to a hardware or software problem. The state of the resources is unknown. RI = We have not yet learned the state of the resources because resync is still ongoing.
97	Allocator flag	Char (1)	Indicates whether this is the allocator location, for example, the location that called the transaction program running on this system: Y = This location is the allocator. N = This location is not the allocator.
98	Remote last agent flag	Char (1)	Indicates whether this location was selected as the last agent if a commit request was performed to end this LUW: Y = This is the last agent. N = This is not the last agent. A last agent will not be selected at this location unless the Partner Role field in the HDR record is I or L.
99	Two-phase protocol	Char (1)	The two-phase commit protocol options supported at this location. 0 = Two-phase commit protocols are not supported. 1 = Two-phase commit presumed nothing protocols are supported. 2 = Two-phase commit presumed abort protocols are supported.
100	Resync initiator	Char (1)	If resync with this location is still ongoing (the Resource State field is RI), this value indicates whether the local location is initiating the resync attempts. I = The local system is initiating resync with this remote location. N = Resync is not being performed with this remote location. W = The local system is waiting for resync to be initiated from this remote location.
101	Voted reliable	Char (1)	Whether this location voted reliable during the commit of this LUW. Y = The location voted reliable. N = The location did not vote reliable.
102	OK to leave out	Char (1)	Whether this location indicated it may be left out of the next commit or rollback operation if no communications flows occur to that location during the next LUW. Y = The location indicated it may be left out. N = The location indicated it may not be left out.
103	Left out	Char (1)	Whether this location was left out of the LUW that was just committed or rolled back. Y = The location was left out. N = The location was not left out.
104	Initiator flag	Char (1)	Indicates whether this location is the initiator location, i.e. the location that sent the commit or rollback request to this system. Y = The location is the initiator. N = The location is not the initiator. The system cannot determine the initiator location if the initiator does not support two-phase commit protocols. This field will always be set to N for locations that do not support two-phase commit protocols.
105	Reserved	Char (24)	Reserved for future use.
1The format for this field is in the description.

 

Moving and renaming objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, Q QM, Q QN) journal entries

Relative offset	Field	Format	Description
Specific values for this entry type:
	Journal identifier (JOJID)	Char (10)	Records for the entries will have a journal identifier. The JID is not provided with the *TYPE1, *TYPE2, and *TYPE3 formats. It can be used with the QJORJIDI API.
Entry-specific data. This data appears as one field in the standard output formats:
1	Object name before	Char (10)	The name of the object before the object was moved or renamed.
11	Library name before	Char (10)	The name of the library before the object was moved or renamed.
21	Member name before	Char (10)	The name of the member before it was moved or renamed. This field is blank if the object is not a physical database file.
31	Object name after	Char (10)	The name of the object after the object was moved or renamed.
41	Library name after	Char (10)	The name of the library after the object was moved or renamed.
51	Member name after	Char (10)	The name of the member after it was moved or renamed. This field is blank if the object is not a physical database file.
61	Internal data	Char (*)	Internal system information. This field does not apply to E EM, E EN, Q QM, or Q QN entries.

 

Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Object name	Char (10)	The name of the object that was operated on.
11	Library name	Char (10)	The name of the library for the object that was operated on.
21	Member name	Char (10)	The name of the member that was operated on, if applicable. This field is blank if it does not apply.
31	Reserved	Char (30)	Reserved.
109	Change field type	Char (1)	The type of Change file operation: 0 = SQL ALTER TABLE 1 = CHGPF, CHGLF, or CHGSRCPF CL command 2 = Miscellaneous change file operations 3 = SQL DELETE FROM table (without a WHERE clause) The type of Change Trigger operation: 4 = Disable Trigger 5 = Enable Trigger 6 = Miscellaneous change trigger operations This field is not applicable if the entry type is not CG or TG. If the journal entry is CT or MC, these subtype values are returned: 7 = Restore 8 = CPYF CRTFILE(*YES) or CRTDUPOBJ 9 = Other Create This field is not applicable if the entry type is not CG, CT, MC, or TG.
110	Reserved	Char (3)	Reserved.
113	Length of trigger library name	Bin (15)	The length of the trigger library name for a Change Trigger operation. Contains 0 if the Change Trigger operation includes multiple triggers. This field is not applicable if the entry type is not TG.
115	Offset to trigger library name	Bin (31)	The offset to the trigger library name for a Change Trigger operation from the beginning of the journal entry specific data. Contains hex zeros if the Change Trigger operation includes multiple triggers. This field is not applicable if the entry type is not TG.
119	Length of trigger name	Bin (15)	Length of the trigger name for a Change Trigger operation. Contains 0 if the Change Trigger operation includes multiple triggers. This field is not applicable if the entry type is not TG.
121	Offset to trigger name	Bin (31)	The offset to the trigger name for a Change Trigger operation from the beginning of the journal entry specific data. Contains hex zeros if the Change Trigger operation includes multiple triggers. This field is not applicable if the entry type is not TG.
	These fields only exist in V5R4 or later journal entries.
125	Object attribute	Char (10)	OIR attribute of the object (for example: PF, LF, etc.)
135	Number of based on physical files	Bin (15)	Number of based on physical files. This field is only applicable to logical file CT entries.
137	Offset to name of first based on physical file	Bin (31)	Offset to 20 byte field consisting of a 10 byte file name followed by 10 byte library name. The file name is the first based on physical file of the logical file. The offset is from the beginning of the journal entry specific data. This field is only applicable for logical file CT entries.
141	Next offset	Bin (15)	Offset from start of prior based on file name to the next based on file name. This field is only applicable for logical file CT entries.
143	Not logged indicator	Char (1)	This entry applies only to CT (create database file) and CG (change database file) entries. 0 = Not logged was not requested on either the CREATE or ALTER operation. 1 = NOT LOGGED request For a CT entry, journaling will be started for the members when the transaction is committed. For a CG entry, journaling was ended for the members and will be restarted when the transaction is committed or rolled back.
144	Reserved	Char (1)
145	Internal data	Char (*)	Internal system information.
Notes: This data does not apply to integrated file system objects. If the data for these entries exceeds 32 KB, then a pointer is returned to the actual data when the entry is retrieved using an option to return pointers. If the return pointer option is not used, then *POINTER is returned for the entry-specific data.

 

Object restored (B FR, D DZ, E EL, F MR, J RR, Q QZ) and receiver saved (J RS) journal entries

Relative offset	Field	Format	Description
Specific values for this entry type:
	Journal identifier (JOJID)	Char (10)	Records for the entries will have a journal identifier. The JID is not provided with the *TYPE1, *TYPE2, and *TYPE3 formats. It can be used with the QJORJIDI API.
Entry-specific data. This data appears as one field in the standard output formats:
1	Media type	Char (3)	The type of media used for the save or restore operation: DKT= Diskette OPT= Optical SAV= Save file TAP= Tape
4	First volume ID	Char (6)	The ID of the first volume used. The optical volume ID might contain up to 32 characters of which the first six characters are displayed.
10	Start save or restore date	Char (6)1	The date the save or restore operation was started. The date is in the format of the DATFMT attribute of the job that performed the save or restore operation.
16	Start save or restore time	Zoned (6,0)	The time the save or restore operation was started.
22	Update history	Char (1)	Whether the save history is updated: 0 = UPDHST(*NO) specified on save command. 1 = UPDHST(*YES) specified on save command.
23	Save file name	Char (10)	The name of the save file used for the operation. This field is blank if a save file was not used.
33	Save file library	Char (10)	The name of the library for the save file. This field is blank if a save file was not used.
43	Media file identifier2	Char (16)	File identifier for the integrated file system object on the media. This applies only to B FR entries.
59	Restored file identifier	Char (16)	File identifier for the restored integrated file system object. This applies only to B FR entries.
75	Restored over file identifier	Char (16)	File identifier for the integrated file system object that was restored over. This applies only to B FR entries.
See the Layouts for the fixed-length portion of journal entries of the journal entry for any information pertaining to the century of this date. In place of the media finder, the Q QZ entry has a 1-byte character (Char (1)) field with the following possible values to indicate if the contents of the data queue were restored: 0 = No 1 = Yes

 

Object saved (B FS, D DH, E ES, F MS, Q QY) journal entries

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Media type	Char (3)	The type of media used to save the object: DKT = Diskette OPT = Optical SAV = Save file TAP = Tape
4	First volume ID	Char (6)	The ID of the first volume used to save the object. The optical volume ID might contain up to 32 characters of which the first six characters are displayed.
10	Start save date	Char (6) 1	The date the save operation was started. The date is in the format of the DATFMT attribute of the job that saved the object.
16	Start save time	Zoned (6,0)	The time the save operation was started.
22	Update history	Char (1)	Whether the save history is updated: 0 = UPDHST(*NO) specified on save command. 1 = UPDHST(*YES) specified on save command.
23	Save file name	Char (10)	The name of the save file used for the operation. This field is blank if a save file was not used.
33	Save file library	Char (10)	The name of the library for the save file. This field is blank if a save file was not used.
43	Save active value	Char (10)	The value specified for the SAVACT parameter on the SAVOBJ, SAVCHGOBJ, SAV, or SAVLIB command.
53	Start save active date	Char (6) 1	For a save-while-active operation, this is the date when checkpoint processing was completed for the object. For a normal save operation, this is the same as the start date.
59	Start save active time	Zoned (6,0)	For a save-while-active operation, this is the time when checkpoint processing was completed for the object. For a normal save operation, this is the same as the start time.
65	Primary receiver name	Char (10)	The name of the first of dual receivers that contains the start-of-save entry.
75	Primary receiver Library	Char (10)	The name of the library containing the primary receiver.
85	Dual receiver name	Char (10)	The name of the second of dual receivers that contains the start-of-save entry. This entry is blank if only a single receiver was used when the start-of-save entry was added.
95	Dual receiver library	Char (10)	The name of the library containing the dual receiver. This entry is blank if only a single receiver was used when the start-of-save entry was added.
105	Sequence number of matching start-of-save entry	Zoned (10, 0)	For a save-while-active operation, the sequence number of the corresponding start-of-save entry. For a normal save operation, this is the sequence number of the current object saved entry. A -1 is returned if the sequence number is greater than 9 999 999 999. If -1, see Large sequence number of matching start-of-save entry.
115	File ID of object or reserved	Char (16)	The file identifier for the object for B FS entries, otherwise blank.4
131	Large sequence number of matching start-of-save entry	Char (20)	For a save-while-active operation, the sequence number of the corresponding start-of-save entry. For a normal save operation, this is the sequence number of the current object saved entry.
151	Library ASP device	Char (10)	The ASP device on which the library that contains the primary receiver resides.
161	Contents saved	Char(1)	Whether the contents of the data queue were saved: 0 = No 1 = Yes This field only applies to Q QY entries.
Notes: See the fixed-length portion of the journal entry for any information pertaining to the century of this date. If an object was saved using the save-while-active function, the saved copy of the object includes all of the changes found in the journal entries up to the corresponding object start of save-while-active entry. For more information see the layout for the Start of save-while-active (B FW, D DW, E EW, F SS, Q QX) journal entries. If an object was NOT saved using the save-while-active function, the saved copy of the object includes all of the changes found in the journal entries up to the corresponding object saved entry. For more information see the layout for Object saved (B FS, D DH, E ES, F MS, Q QY) journal entries.

 

Ownership change (E ZO, Q ZO) journal entries

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Old owner	Char (10)	The name of the old owner.
11	New owner	Char (10)	The name of the new owner.

Received data queue, has key (Q QL) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Reserved	Char (18)	Reserved for future use.
19	Key length	Bin (16)	The number of characters in the key.
21	Key order	Char (2)	The Key order is as follows: GT = Greater than LT = Less than NE = Not equal EQ = Equal GE = Greater than or equal LE = Less than or equal
23	Key	Char (*)	The data to be used to receive a message from the data queue.

ROLLBACK (C RB) journal entry

Relative offset	Field	Format	Description
Specific values for this entry type:
	Job name (JOJOB)	Char (10)	Blank if the entry was added during an IPL vary on of an independent disk pool.
	Program name (JOPGM)	Char (10)	Blank if the entry was added during an IPL or vary on of an independent disk pool.
	Flag (JOFLAG)	Char (1)	How the rollback operation was initiated and whether it was successful: 0 = All record-level changes were rolled back for a rollback operation initiated by a user. 1 = Not all record-level changes were successfully rolled back for a rollback operation initiated by a user. 2 = All record-level changes were rolled back for a rollback operation initiated by the operating system. 3 = Not all record-level changes were rolled back for a rollback operation initiated by the operating system.

Rollback ended early (C CN, F C1) journal entries

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	User profile	Char (10)	The user profile that requested to end the rollback.
11	Process	Char (26)	The process that requested to end the rollback.

RGZPFM (F RG) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	File name	Char (10)	The name of the file specified for the KEYFILE parameter on the RGZPFM command. If KEYFILE(*NONE) was specified, this field is blank.
11	Library name	Char (10)	The name of the library specified in the KEYFILE parameter of the RGZPFM command. If KEYFILE(*NONE) was specified, this field is blank.
21	Member name	Char (10)	The name of the member specified in the KEYFILE parameter of the RGZPFM command. If KEYFILE(*NONE) was specified, this field is blank.

 

Savepoint released (C SQ) and savepoint rolled back (C SU) journal entries

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Sequence number	Char (20)	The sequence number where the savepoint was established

Send data queue, has key (Q QK) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Data length	Bin (32)	The length of the Data field (which is the last field in the ESD of this journal entry). When replicating a data queue entry with this journal entry, this length field should be specified on the QSNDDTAQ API in association with the Data field below. See the details in the description of the Data field.
5	Offset to data	Bin (32)	Offset to the Data field (which is the last field in the ESD of this journal entry). The offset is calculated from the beginning of the entry-specific data (ESD).
9	Reserved	Char (2)	Reserved for future use.
11	Key length	Bin (16)	The number of characters in a key.
13	Reserved	Char (4)	Reserved for future use.
17	Key	Char (*)	A prefix added to an entry by its sender.
	Reserved	Char (*)	Padding to align fields.
Offset to data	Data	Char (*)	The first 16 bytes of the Data field are API information required by the Send Data Queue (QSNDDTAQ) API. When replicating a data queue entry with this journal entry, this entire Data field (including the 16 bytes of API information) must be passed to the QSNDDTAQ API when it is called with parameter eight (Data is from a journal entry) set to *YES. These 16 bytes are not placed on the data queue. The remainder of the Data field is placed on the data queue.

 

Send data queue, no key (Q QS) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Reserved	Char (28)	Reserved for future use.
29	Data length	Bin (32)	The length of the Data field (which is the last field in the ESD of this journal entry). When replicating a data queue entry with this journal entry, this length field should be specified on the QSNDDTAQ API in association with the Data field below. See the details in the description of the Data field.
33	Data	Char (*)	The first 16 bytes of the Data field are API information required by the Send Data Queue (QSNDDTAQ) API. When replicating a data queue entry with this journal entry, this entire Data field (including the 16 bytes of API information) must be passed to the QSNDDTAQ API when it is called with parameter eight (Data is from a journal entry) set to *YES. These 16 bytes are not placed on the data queue. The remainder of the Data field is placed on the data queue.

 

Start of save-while-active (B FW, D DW, E EW, F SS, Q QX) journal entries

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Media type	Char (3)	The type of media used to save the object: DKT = Diskette OPT = Optical SAV = Save file TAP = Tape
4	First volume ID	Char (6)	The ID of the first volume used to save the object. The optical volume ID might contain up to 32 characters of which the first six characters are displayed.
10	Start save date	Char (6) 1	The date the save operation was started. The date is in the format of the DATFMT attribute of the job that saved the object.
16	Start save Time	Zoned (6,0)	The time the save operation was started.
22	Update history	Char (1)	Whether the save history is updated: 0 = UPDHST(*NO) specified on the save command. 1 = UPDHST(*YES) specified on the save command.
23	Save file name	Char (10)	The name of the save file used for the operation. This field is blank if a save file was not used.
33	Save file library	Char (10)	The name of the library for the save file. This field is blank if a save file was not used.
43	Save active value	Char (10)	The value specified for the SAVACT parameter on the SAVOBJ, SAVCHGOBJ, SAV, or SAVLIB command.
53	Save active date	Char (6)1	For a save-while-active operation, this is the date when checkpoint processing was completed for the object. For a normal save operation, this is the same as the start date.
59	Save active Time	Char (6)	For a save-while-active operation, this is the time when checkpoint processing was completed for the object. For a normal save operation, this is the same as the start time.
65	Object file ID4	Char (16)	The file identifier of the integrated file system object. This applies only to B FW entries.
Notes: See the fixed-length portion of the journal entry for any information pertaining to the century of this date. If an object was saved using the save-while-active function, the saved copy of the object includes all of the changes found in the journal entries up to the corresponding object start of save-while-active entry. For more information see the layout for Start of save-while-active (B FW, D DW, E EW, F SS, Q QX) journal entries. If an object was NOT saved using the save-while-active function, the saved copy of the object includes all of the changes found in the journal entries up to the corresponding object saved entry. See the entry-specific data for Object saved (B FS, D DH, E ES, F MS, Q QY) journal entries. In place of the Object file ID, the Q QY entry has a 1-byte character (Char(1)) field with the following possible values to indicate if the contents of the data queue were saved: 0 = No 1 = Yes

 

Start journal (B JT, D JF, E EG, F JM, Q QB) journal entries

Relative offset	Field	Format	Description
Specific values for this entry type:
	Flag (JOFLAG)	Char (1)	Indicates the type of images selected: 0 = After images are journaled. 1 = Before and after images are journaled.
Entry-specific data. This data appears as one field in the standard output formats:
1	Omit journal entry	Char (1)	Indicates the value of the OMTJRNE parameter on the Start Journal command. 0 = No entries are omitted from journaling. 1 = Open and Close (*FILE), or Open, Close, and Force (*DIR or *STMF) entries are not journaled.
2	New object inherit journaling	Char (1)	Specifies whether journaling starts automatically for new objects created in the directory. 0 = No or does not apply 1 = Yes
3	Reserved	Char (6)	Reserved field
9	File identifier	Char (16)	The file identifier for the integrated file system object. This only applies to B JT entries.
25	Path name	Char (*)	The path name information optionally follows the file identifier. This only applies to BJT entries.

 

Usage limit changed (L LL) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Product ID	Char (7)	The ID of the product whose usage limit was changed.
8	License term	Char (6)	The term of the license.
14	Feature	Char (4)	The product feature code.
18	Previous usage limit	Zoned (6,0)	The usage limit before the change.
24	Current usage limit	Zoned (6,0)	The usage limit after the change.
30	Old expiration date	Char (7)	The expiration date before the change.
37	New expiration date	Char (7)	The expiration date after the change.

Usage limit exceeded (L LU) journal entry

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Product ID	Char (7)	The ID of the product whose usage limit was exceeded.
8	License term	Char (6)	The term of the license.
14	Feature	Char (4)	The product feature code.
18	Usage limit	Zoned (6,0)	The usage limit for the product.
24	Request flag	Char (1)	Whether the request was successful: 0 = License request was successful. 1 = License request was not successful.
25	Number of licensed users	Zoned (6,0)	The number of users currently licensed for the product.
31	Licensed user name	Char (26) x 100	The names of up to 100 users who are licensed for the product.

Update data area (E EA, E EB) journal entries

Relative offset	Field	Format	Description
Entry-specific data. This data appears as one field in the standard output formats:
1	Starting position	Bin (32)	Starting position of change as specified by the user (1 for decimal).
5	Length of change	Bin (32)	Length of change to be applied as specified by the user.
9	Number	Bin (32)	Number of decimal positions as specified by the user.
13	Offset to change	Bin (32)	Offset to change value field from the beginning of the entry-specific data (ESD).
17	Type	Char (10)	Type of data area. Data area types are *CHAR, *DEC, and *LGL.
	Padding for alignment	Char (*)	Padding to align fields.
Offset to change	Change value	Char (*)	Value of the change.

Common fields

The following tables contain fields of entry-specific data that are common to more than one journal entry layout.

 

Journal information

This table contains entry-specific data for journal information. For an explanation of these fields, see the Get Attributes (Qp0lGetAttr()) API.

Relative offset	Field	Format	Description
1	Journaling status	Char (1)	Indicates whether the object is journaled.
2	Options	Char (1)	The journaling options or attributes.
3	JID	Char (10)	The journal identifier.
13	Journal name	Char (10)	The journal name.
23	Journal library	Char (10)	The journal library.
33	Time journaling was last started	Bin (32)	Time journaling was last started.

 

Object name

This table contains entry-specific data for the name of an integrated file system object. For more information about the object name see Path name format in the API topic.

Relative offset	Field	Format	Description
1	Length	Bin (32)	The length of the object name field.
5	Path name CCSID	Bin (31)	The coded character set identifier (CCSID) for the object name.
9	Object name country ID	Char (2)	The country identifier for national language support.
11	Object name language ID	Char (3)	The language identifier for national language support.
14	Reserved	Char (3)	Reserved. This field contains all hex zeros.
17	Object name	Char (*)	The object name. The field is of variable length.

 

Path name

This table contains entry-specific data for the path name of an integrated file system object. For more information about the path name see Path name format in the API topic.

Relative offset	Field	Format	Description
1	Path indicator	Char (1)	The absolute or relative path indicator. This field uses one of the following values: 0 = The path contains an absolute path name. The Relative directory FID field is hex zeros. 1 = The path contains a relative path name. The Relative directory FID field is valid and can be used to form a complete path name.
2	Relative directory FID	Char (16)	If the path indicator is 1, this is the file identifier for the directory that contains the object indicated in the path name field. Otherwise, this will be zeros.
18	Path name CCSID	Bin (31)	The coded character set identifier (CCSID) for the path name.
22	Path name country ID	Char (2)	The country identifier for national language support.
24	Path name language ID	Char (3)	The language identifier for national language support.
27	Reserved	Char (3)	Reserved. This field contains all hex zeros.
30	Path name type	Bin (32)	The path name type uses one of the following values: 0 = The path name is a character string with a one byte delimiter. 2 = The path name is a character string with a two byte delimiter.
34	Path length	Bin (31)	The path length.
38	Path name delimiter	Char (2)	The path name delimiter.
40	Reserved	Char (10)	Reserved. Set to blanks.
50	Path name	Char (*)	The object path name. This field is of variable length.

 

Private authority information

This table contains entry-specific data for the private authority information that has been set for an integrated file system object when an object is created.

Relative offset	Field	Format	Description
1	User name	Char (10)	The name of the user profile whose authority is being granted.
11	Operation type	Char (3)	GRT = Grant authority.
14	Reserved	Char (7)	Reserved. Set to zeros.
21	Private authority	Char (12)	Private authorities assigned to the given user profile.

 

Private authorities for specified profile

Relative offset	Field	Format	Description
1	Object existence authority	Char (1)	Y = The specified profile has *OBJEXIST authority to the object. blank = The specified profile does not have *OBJEXIST authority to the object.
2	Object management authority	Char (1)	Y = The specified profile has *OBJMGT authority to the object. blank = The specified profile does not have *OBJMGT authority to the object.
3	Object operational authority	Char (1)	Y = The specified profile has *OBJOPR authority to the object. blank = The specified profile does not have *OBJOPR authority to the object.
4	Object alter authority	Char (1)	Y = The specified profile has *OBJALTER authority to the object. blank = The specified profile does not have *OBJALTER authority to the object.
5	Object reference authority	Char (1)	Y = The specified profile has *OBJREF authority to the object. blank = The specified profile does not have *OBJREF authority to the object.
6	Read authority	Char (1)	Y = The specified profile has *READ authority to the object. blank = The specified profile does not have *READ authority to the object.
7	Add authority	Char (1)	Y = The specified profile has *ADD authority to the object. blank = The specified profile does not have *ADD authority to the object.
8	Update authority	Char (1)	Y = The specified profile has *UPD authority to the object. blank = The specified profile does not have *UPD authority to the object.
9	Delete authority	Char (1)	Y = The specified profile has *DLT authority to the object. blank = The specified profile does not have *DLT authority to the object.
10	Exclude authority	Char (1)	Y = The specified profile has *EXCLUDE authority to the object. blank = The specified profile does not have *EXCLUDE authority to the object.
11	Execute authority	Char (1)	Y = The specified profile has *EXECUTE authority to the object. blank = The specified profile does not have *EXECUTE authority to the object.
12	Reserved	Char (1)	Reserved. Set to blank.

Symbolic link contents

Relative offset	Field	Format	Description
1	Contents included	Char (1)	Indicates if the entire symbolic link contents are included in the Contents field. The possible values are: 0 = The entire symbolic link contents cannot be included in the Contents field because the maximum possible has been exceeded. The symbolic link contents are truncated in this entry. 1 = The entire symbolic link contents are included in the Contents field.
2	Contents CCSID	Bin (31)	The coded character set identifier (CCSID) for the symbolic link contents.
6	Contents country ID	Char (2)	The country identifier for national language support for the symbolic link contents.
8	Contents language ID	Char (3)	The language identifier for national language support for the symbolic link contents.
11	Reserved	Char (3)	Reserved. This field contains all hex zeros.
14	Contents path type	Bin (32)	The possible values for the contents path type are: 0 = The path name is a character string with a one byte delimiter. 2 = The path name is a character string with a two byte delimiter.
18	Contents path length	Bin (31)	The path length for the symbolic link contents.
22	Contents path name delimiter	Char (2)	The path name delimiter for the symbolic link contents.
24	Reserved	Char (10)	Reserved. This field contains all hex zeros.
34	Symbolic link contents	Char (*)	The symbolic link contents. This field is of variable length.

Related concepts
Displaying and printing journal entries Considerations for entries which contain minimized entry-specific data File identifier considerations for working with integrated file system entries

Related reference
Set Attributes (Qp0lSetAttr()) API Get Attributes (Qp0lGetAttr()) API Send Data Queue (QSNDDTAQ) API Path name format