A commit cycle is the time from one commitment boundary to the next. The system assigns a commit cycle identifier to associate all of the journal entries for a particular commit cycle together. Each journal that participates in a transaction has its own commit cycle and its own commit cycle identifier.
The commit cycle identifier is the journal sequence number of the C SC journal entry written for the commit cycle. The commit cycle identifier is placed in each journal entry written during the commit cycle. If more than one journal is used during the commit cycle, the commit cycle identifier for each journal is different.
You can specify that the fixed-length portion of the journal entry includes transaction information by specifying the Logical Unit of Work (*LUW) value for the Fixed-Length Data (FIXLENDTA) parameter of the Create Journal (CRTJRN) or Change Journal (CHGJRN) command. By specifying the FIXLENDTA (*LUW) parameter, the fixed-length portion of each C SC journal entry will contain the Logical Unit of Work ID (LUWID) of the current transaction. Likewise for XA transactions, if you specify the FIXLENDTA (*XID) parameter, the fixed-length portion of each C SC journal entry will contain the XID of the current transaction. The LUWID or XID can help you find all the commit cycles for a particular transaction if multiple journals or systems are involved in the transaction.
You can use the Send Journal Entry (QJOSJRNE) API to write journal entries for API resources. You have the option of including the commit cycle identifier on those journal entries.
You can use the commit cycle identifier to apply or remove journaled changes to a commitment boundary using the Apply Journaled Changes (APYJRNCHG) command or the Remove Journaled Changes (RMVJRNCHG) command. These limitations apply: