The value n may be 1 or 0:
If FreezeOnError=1 (true) then, on a journal file I/O error, the Journal daemon freezes journaling immediately. The Journal daemon unfreezes journaling after it succeeds with the failed I/O operation. As soon as the error occurs all global activities that are normally journaled are blocked, which causes other jobs to hang; typically until you resolve the journaling problem. While Caché is hanging, you can take corrective measures, such as freeing up space on a full disk or switching the journal to a new working disk. This prevents the loss of journal data at the expense of system availability.
If FreezeOnError=0 (false), then Caché does not freeze on a journal file I/O error. Caché disables journaling if it is not able to recover in a timely manner from the error. This prevents the system from hanging. Journaling is first retried, and then disabled, while Caché continues running. If journaling is disabled, you want to backup your databases as soon as possible. Running without journaling is a calculated risk, as it means the activity that occurs during this period cannot be restored. If Journaling is disabled, you MUST restart it. Ways to restart it include running the ^JRNSTART routine or selecting option 1, Begin Journaling, from the ^JOURNAL routine menu. See the “Start Journaling Using ^JRNSTART” section for details.
If FreezeOnError=0 and you are shadowing to another system and a journal error occurs, then the shadow may fall out of sync with the master.
For details, see the section “Journal I/O Errors” in the “Journaling” chapter of the Caché Data Integrity Guide.
0 or 1. The default is 0.
On the page System Administration > Configuration > System Configuration > Journal Settings, in the FreezeOnError box, choose Yes (true) or No (false).