The following section describes the SET /JOURNAL= options.
![[Note]](images/note.png)
|
Note |
|---|---|
|
This option list is a super set of the journal-option-list available through GDE. |
Every MUPIP SET /JOURNAL command on a database file which specifies an ON or OFF journal-activation option causes the values of all explicitly specified journal-file-options to be stored in the database overriding any previously established characterstics for those options.
|
|
Note |
|---|---|
|
If both /JOURNAL and /NOJOURNAL are specified in the same command line, the last of these specifications on the line takes effect. |
A new journal file can be created in the following three ways:
-
Explicitly, by specifying a MUPIP SET /JOURNAL=ON command
-
Implicitly, when the AUTOSWITCHLIMIT (discussed later in the following section) for the current journal file is reached
-
Implicitly, when the first process to open the current journal file detects that it was not cleanly terminated
Whenever GT.M creates a new journal file, it uses any values for journal-file-options explicitly specified in the command line for the new journal file and takes all journal-file-options that are not explicitly specified from the existing journal file characteristics for the corresponding database file.
|
|
Note |
|---|---|
|
MUPIP SET supports qualifiers (like /ACCESS_METHOD etc.) to change non-journaling characteristics of database file(s). If these qualifiers are specified along with the /JOURNAL qualifier, MUPIP SET modifies the non-journaling characteristics first and the journaling characteristics second. Command execution stops when it encounters an error. If MUPIP SET encounters an error in processing the command line or the non-journaling characteristics, it makes no changes to any characteristics. However, if MUPIP SET encounters an error in processing the journaling characteristics, the non-journaling characteristics get successfully changed. |
The journal-option-list may include: