The GT.M Journaling facility has impact on a number of components:
DSE - used to examine current journaling configuration and historical statistics
GDE - used to set up default journaling characteristics for database regions
MUPIP JOURNAL - used to process journal files for recovery or analysis
MUPIP JOURNAL -ROLLBACK - used to recover databases when replication is enabled - relies on journal files
MUPIP BACKUP - used to make database backups - can initiate new journal files
MUPIP SET -JOURNAL - used to modify journaling characteristics, and to initiate new journal files
MUPIP SET -REPLICATION - used to modify replication characteristics - replication requires journaling
GT.M compiler - supports language features (with run-time system support) to examine journaling status and, when journaling is on, affect journaling behavior
GT.M run-time system - creates journal file entries; may create new journal files or turn off journaling under some circumstances;
In order to use journaling you should familiarize yourself with the tools. One critical choice is deciding whether and how to use journal fences. Another is how to manage the journal files in coordination with an appropriate database backup scheme. Whether or not to use replication affects these choices.
The following sections address these journaling topics in more detail.