BGIN

Written to the journal file to mark the beginning of local work done by a transaction branch. This checkpoint is written when a database transaction is initiated if JOURNAL RETRIEVAL is specified in the system generation, or when the first update occurs, otherwise.

ENDJ

Written to the journal file during a commit operation to mark the successful completion of a transaction branch.

COMT

Written to the journal file during a commit operation to mark the successful completion of a transaction branch. A COMT is similar to an ENDJ checkpoint except that it enables work done after the commit to be recorded on the journal file using the same local identifier (LID).

ABRT

Written to the journal file during a backout operation to mark the abnormal completion of a transaction branch.

AREA

Written for each area readied by an explicit DML READY command or readied automatically by the DBMS.

RTSV

Written automatically to the journal file each time CA IDMS/DB encounters an error while executing an SQL or physical DDL statement that updated the database. During recovery, CA IDMS/DB rolls back to the journal record designated by the RTSV checkpoint record.

TIME

Written to a journal each time the journal's buffer is initialized. However, the time and date fields contain binary zeros until the journal buffer is written to the journal file.

BFOR

Written to a journal each time a record is updated and carries the image of that record before the change was made

AFTR

Written to a journal each time a record is updated and carries the image of that record after the change was made

CKPT

Written to a journal to mark the simultaneous successful completion of multiple branches of a local transaction. This checkpoint is used to coordinate the commit of a local transaction involving multiple branches.

USER

Written to a journal via the WRITE JOURNAL command issued by a user program

JSEG

Written to a journal at the beginning of each disk journal segment. This record identifies the transactions that were active when that journal segment was started.

DSEG

Written periodically to the journal to identify the transactions that are active at a given point in time.

DCOM

Written to the journal file during a two-phase commit operation to mark the successful completion of a distributed transaction. It is written to the coordinator's journal file at the start of the second phase of the commit operation and to a participant's journal file when it is informed that its changes should be committed.

DBAK

Written to the journal file during a two-phase commit operation to mark the abnormal completion of a distributed transaction. It is written to the coordinator's journal file during the first phase of the commit operation as soon as it is determined that the transaction's changes should be backed out and to a participant's journal file when it is informed that its changes should be backed out.

DFGT

Written to the journal file at the end of a two-phase commit operation to mark the end of the distributed transaction. It is written to a coordinator's or participant's journal file if any other distributed checkpoint (DCOM, DBAK, DPND, and DIND) had been previously written for the transaction.

DIND

Written to a participant's journal file during a two-phase commit operation to note that the participant is prepared to commit its portion of the distributed transaction. The participant will wait for a directive from the coordinator as to whether to complete the commit operation or to back out changes.

DPND

Written to the journal file during a two-phase commit operation to mark an interim result for a distributed transaction. It may be written for several reasons, such as when a participant is forced to complete a transaction heuristically or when a coordinator is unable to communicate with a participant during the second phase of the commit operation.