Disabling Journaling for Filing Operations

Under certain circumstances, it may be useful or necessary to disable journaling for filing operations, such as object saves and deletes. There are two ways to do this:

When you open an object (typically with %OpenIdOpens in a new tab or %OpenOpens in a new tab), specify a concurrency value of 0. However, if the object is already open with a higher concurrency value, then specifying a concurrency of 0 is not effective.
Suspend object filer transaction processing for the current process. To do this, call $system.OBJ.SetTransactionMode(0) (which is the SetTransactionModeOpens in a new tab method of the %SYSTEM.OBJOpens in a new tab class; you can invoke it through the special $system object). The SetTransactionMode method takes a value of 0 or 1: 0 turns off object filer transactions and 1 turns them on. Note that this setting affects the entire process, not just the current filing operation.

Important:

While certain circumstances call for disabling journaling, make sure that this is necessary before doing it. Otherwise, there may be a journal that does not include all the data required, which can result in the permanent loss of data.