Journaling is a process that ensures the logical and physical consistency of a database under conditions where system or process failure might otherwise cause damage. A database can have both physical integrity, so that all globals can be referred to correctly, and logical integrity, where the database is not only physically correct but logically consistent from an application perspective.

GT.M journaling is required to implement ACID (atomic, consistent, isolated, and durable) transactions. The journaling operation is controlled by MUPIP.

GT.M lets you journal all or some of your database files and to restore them, if necessary, in either a forward or backward direction. For more information, refer to the "GT.M Journaling" chapter.