Layouts for variable-length portion of journal entries

• 01 = Partial transactions exist due to restore.
• 02 = Partial transactions exist because a rollback was ended early.

• 0 = Command completed normally.
• 1 = Command completed abnormally.

• 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

• Y = Yes
• N = No

• Y = Yes
• N = No

• Y = Yes
• N = No

• Y = Yes
• N = No

• Y = Yes
• N = No

• Y = Yes
• N = No

• Y = User has *OBJEXIST authority to the object.
• blank = User does not have *OBJEXIST authority to the object.

• Y = User has *OBJMGT authority to the object.
• blank = User does not have *OBJMGT authority to the object.

• Y = User has *OBJOPR authority to the object.
• blank = User does not have *OBJOPR authority to the object.

• Y = User has *PUBLIC authority to the object.
• blank = User does not have *PUBLIC authority to the object.

• Y = User has *READ authority to the object.
• blank = User does not have *READ authority to the object.

• Y = User has *ADD authority to the object.
• blank = User does not have *ADD authority to the object.

• Y = User has *UPD authority to the object.
• blank = User does not have *UPD authority to the object.

• Y = User has *DLT authority to the object.
• blank = User does not have *DLT authority to the object.

• Y = User has *EXCLUDE authority to the object.
• blank = User does not have *EXCLUDE authority to the object.

• Y = User has *EXECUTE authority to the object.
• blank = User does not have *EXECUTE authority to the object.

• Y = User has *OBJALTER authority to the object.
• blank = User does not have *OBJALTER authority to the object.

• Y = User has *OBJREF authority to the object.
• blank = User does not have *OBJREF authority to the object.

• GRT = Grant.
• RPL = Grant with replace.
• RVK = Revoke.

• 1 = IMAGES
• 2 = OMTJRNE
• 3 = INHERIT

• IMAGES(*BOTH)
• IMAGES(*AFTER)
• OMTJRNE(*NONE)
• OMTJRNE(*OPNCLOSYN)
• INHERIT(*YES)
• INHERIT(*NO)

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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.

• Y = The previous primary group authority to the object was revoked.
• blank = The previous primary group authority to the object was not revoked.

• 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.

• *CHAR - character
• *DEC - decimal
• *LOG - logical

• *LIBCRTAUT
• *CHANGE
• *ALL
• *EXCLUDE
• *NAME

• N = Force is not done
• Y = Force is done

• F = FIFO queue
• K = Keyed queue
• L = LIFO queue

• N = Do not include ID
• Y = Include ID

• S = Standard data queue

• -1 = *MAX16MB
• -2 = *MAX2GB

The settings for this field are:

• 0 = no storage released
• 1 = storage is released

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

• I = File opened for input
• blank = Input not specified

• O = File opened for output
• blank = Output not specified

• U = File opened for update
• blank = Update not specified

• D = File opened for delete
• blank = Delete not specified

• Y = Journaling will be started
• blank = Journaling will not be started

• D = Changed DLO authority
• O = Changed object authority

• A = Change authorization.

• Y = User has *OBJEXIST authority to the object.
• blank = User does not have *OBJEXIST authority to the object.

• Y = User has *OBJMGT authority to the object.
• blank = User does not have *OBJMGT authority to the object.

• Y = User has *OBJOPR authority to the object.
• blank = User does not have *OBJOPR authority to the object.

• Y = User has *PUBLIC authority to the object.
• blank = User does not have *PUBLIC authority to the object.

• Y = User has *READ authority to the object.
• blank = User does not have *READ authority to the object.

• Y = User has *ADD authority to the object.
• blank = User does not have *ADD authority to the object.

• Y = User has *UPD authority to the object.
• blank = User does not have *UPD authority to the object.

• Y = User has *DLT authority to the object.
• blank = User does not have *DLT authority to the object.

• Y = User has *EXCLUDE authority to the object.
• blank = User does not have *EXCLUDE authority to the object.

• Y = User has *EXECUTE authority to the object.
• blank = User does not have *EXECUTE authority to the object.

• Y = User has *OBJALTER authority to the object.
• blank = User does not have *OBJALTER authority to the object.

• Y = User has *OBJREF authority to the object.
• blank = User does not have *OBJREF authority to the object.

• GRT = Grant
• RPL = Grant with replace
• RVK = Revoke

• A = Change owner

• A = Change primary group profile

• Y = New primary group has *OBJEXIST authority to the object.
• blank = New primary group does not have *OBJEXIST authority to the object.

• Y = New primary group has *OBJMGT authority to the object.
• blank = New primary group does not have *OBJMGT authority to the object.

• Y = New primary group has *OBJOPR authority to the object.
• blank = New primary group does not have *OBJOPR authority to the object.

• Y = New primary group has *OBJALTER authority to the object.
• blank = New primary group does not have *OBJALTER authority to the object.

• Y = New primary group has *OBJREF authority to the object.
• blank = New primary group does not have *OBJREF authority to the object.

• Y = New primary group has *READ authority to the object.
• blank = New primary group does not have *READ authority to the object.

• Y = New primary group has *ADD authority to the object.
• blank = New primary group does not have *ADD authority to the object.

• Y = New primary group has *UPD authority to the object.
• blank = New primary group does not have *UPD authority to the object.

• Y = New primary group has *DLT authority to the object.
• blank = New primary group does not have *DLT authority to the object.

• Y = New primary group has *EXECUTE authority to the object.
• blank = New primary group does not have *EXECUTE authority to the object.

• Y = New primary group has *EXCLUDE authority to the object.
• blank = New primary group does not have *EXCLUDE authority to the object.

• Y = The previous primary group authority to the object was revoked.
• blank = The previous primary group authority to the object was not revoked.

The format indicator is set to the following:

• 0 = The original layout of this journal entry (FORMAT1)

• 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.

• 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.

• 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.

• 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.

• 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.

• Y = Indicates that the target was replaced.
• blank = Indicates that the target did not exist before this operation.

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.

• 0 = *DFT (default)
• 1 = *DLT (delete)

• 0 = Object was synchronized with journal
• 1 = Object was not synchronized with journal

• 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.

• API = API Commitment resource record

• 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.

• 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.

• 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.

• Char (10): exit program name
• Char (10): exit program library

• 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)

• 2 = This is a two-phase resource (API resources are always two-phase resources).

• 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.

• 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.

• Y = This resource is to be selected as the last agent.
• N = This resource is not to be selected as the last agent.

• Y = Remote resources are allowed with this resource.
• N = Remote resources are not allowed with this resource.

• Y = This resource will hold save-while-active requests.
• N = This resource will not hold save-while-active requests.

• DDL = SQL Object Change record.

• 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.

• 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.

• 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.

• 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

• 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)

• 2 = This is a two-phase resource (DDL resources are always two-phase resources).

• 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.

• DDM = Remote Database file record.

• 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.

• 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.

• 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.

• Char (10): DDM file name
• Char (10): DDM file library name

• 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

• O = The DDM file was open.
• C = The DDM file was closed.

• 1 = This is a one-phase resource.
• 2 = This is a two-phase resource.

• 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.

• HDR = Header record.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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

• A = Activation group level commitment definition.
• E = Explicitly named commitment definition.
• J = JOB 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.

• 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)

• Char (10): Journal name
• Char (10): Journal library

• 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.

• 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.

• 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.

• 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

• 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:

1. 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.
2. 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.

• 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.

• 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.

• 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.

• R = Rollback if problems occur.
• C = Commit if problems occur.

• N = Do not allow a read-only vote.
• Y = Allow a read-only vote.

• W = Wait to allow normal processing of the LUW to complete.
• R = Rollback during ENDJOB.
• C = Commit during ENDJOB.

• 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.

• S = The system is allowed to select a last agent.
• N = The system is not allowed to select a last agent.

• Y = Accept the vote reliable indicator from agents during commit operations.
• N = Do not accept the vote reliable indicator from agents during commit operations.

• Y = Wait for outcome of resynchronization.
• N = Do not wait for outcome of resynchronization.

Bin(31) format identifier
Bin(31) global transaction identifier length
Bin(31) branch qualifier length
Char (128) XID value

• LCL = Local location record.

• 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.

• 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.

• 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.

• 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.

• 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)

• Y = It is the default journal.
• N = It is not the default journal.

• 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.

• 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.

• 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.

• 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

• 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.

• 1 = The resources are one-phase.
• 2 = The resources are two-phase.

• 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.

• 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.

• Y = This location is the allocator.
• N = This location is not the allocator.

• Y = This is the last agent.
• N = This is not the last agent.

• 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.

• 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.

• Y = The location voted reliable.
• N = The location did not vote reliable.

• Y = The location indicated it may be left out.
• N = The location indicated it may not be left out.

• Y = The location was left out.
• N = The location was not left out.

• Y = The location is the initiator.
• N = The location is not the initiator.

• 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.

• DKT= Diskette
• OPT= Optical
• SAV= Save file
• TAP= Tape

• 0 = UPDHST(*NO) specified on save command.
• 1 = UPDHST(*YES) specified on save command.

• DKT = Diskette
• OPT = Optical
• SAV = Save file
• TAP = Tape

• 0 = UPDHST(*NO) specified on save command.
• 1 = UPDHST(*YES) specified on save command.

• 0 = No
• 1 = Yes

• GT = Greater than
• LT = Less than
• NE = Not equal
• EQ = Equal
• GE = Greater than or equal
• LE = Less than or equal

• 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.

• DKT = Diskette
• OPT = Optical
• SAV = Save file
• TAP = Tape

• 0 = UPDHST(*NO) specified on the save command.
• 1 = UPDHST(*YES) specified on the save command.

• 0 = After images are journaled.
• 1 = Before and after images are journaled.

• 0 = No entries are omitted from journaling.
• 1 = Open and Close (*FILE), or Open, Close, and Force (*DIR or *STMF) entries are not journaled.

• 0 = No or does not apply
• 1 = Yes

• 0 = License request was successful.
• 1 = License request was not successful.