/JOURNAL

 /JOURNAL[=journal-file] (default)
 /NOJOURNAL

 Determines the type of journaling, if any.  Journaling records your
 edits so that if a system failure interrupts your editing session,
 you can recover your work.  Processing this qualifier depends on the
 TPU application you are using.

 Normally, journal files are deleted when you exit or quit.  If a
 system failure occurs during your editing session, such as a break in
 communications between your terminal and computer, the journal files
 are saved.  For information about recovering your work, see help on
 /RECOVER.

 +--------------------------  NOTE  --------------------------+
 | Journal files record information about the text you edit.  |
 | Therefore, if you are editing confidential data, make sure |
 | the journal files, as well as the text files, are secure.  |
 +------------------------------------------------------------+

 There are two types of journaling, as follows:

 o  Buffer-change journaling creates a journal file for each text
    buffer.  This is the EVE default.  Buffer-change journaling works
    on DECwindows or character-cell terminals.  The journal file name
    derives from the name of the file or buffer being edited and the
    file type .TPU$JOURNAL---for example:

       Text buffers          Buffer-change journal files
       -------------------------------------------------
       MAIN                  MAIN.TPU$JOURNAL
       JABBER.TXT            JABBER_TXT.TPU$JOURNAL
       GUMBO_RECIPE.RNO      GUMBO_RECIPE_RNO.TPU$JOURNAL
       NEW TEST DATA         NEW_TEST_DATA.TPU$JOURNAL
       * TEMP *              __TEMP__.TPU$JOURNAL

    Buffer-change journal files are created in the directory defined
    by the TPU$JOURNAL logical name.  Default is SYS$SCRATCH, which is
    usually your top-level, login directory.  Because buffer-change
    journal files may be quite large---even larger than the files you
    edit---you may want to define TPU$JOURNAL as a different disk and
    directory.

    Some editing operations may be slower because of buffer-change
    journaling, depending on the type or extent of changes, such as
    cutting a large box, or pasting a large amount of text from the
    DECwindows clipboard.

 o  Keystroke journaling creates a single journal file for the editing
    session, regardless of the number of buffers you create.  The
    journal file records every keystroke in the editing session,
    whether text or commands.  To enable keystroke journaling, use
    /JOURNAL= and specify the journal file you want created.  You
    cannot use wildcards to specify the keystroke journal file.
    Default file type is .TJL.

    For example, the following command invokes TPU creating a
    keystroke journal file named MYJOURNAL.TJL in your current,
    default directory:

       $ EDIT/TPU /JOURNAL=myjournal

    Keystroke journaling does NOT work on DECwindows and has other
    restrictions affecting recovery (see help on /RECOVER).  Keystroke
    journaling is useful to reproduce a problem (for example, if you
    want to submit an SPR) or to journal an editing session in which
    you create LEARN sequences and define keys interactively.

 If you use keystroke journaling, EVE also creates a buffer-change
 journal file for each text buffer.  This double journaling may slow
 performance, depending on the kind of edits you make.  To disable
 buffer-change journaling for a particular buffer or for all your
 buffers, use SET NOJOURNALING commands during your editing session.

 If you do not want any journaling, use /NOJOURNAL, which disables
 both keystroke journaling and buffer-change journaling.  This may
 make startup and some editing operations faster but risks losing your
 work if a system failure occurs during the editing session.
 Typically you use /NOJOURNAL if you are also using /NOMODIFY,
 /NOOUTPUT, /READ_ONLY, or /NOWRITE to view a file without making any
 changes.  If you invoke EVE with /NOJOURNAL, you can enable buffer-
 change journaling during your editing session by using SET JOURNALING
 commands.

 For more information about journaling and recovery, see the
 Extensible Versatile Editor Reference Manual or use the online help
 in EVE and read the topic called Journal Files.

 +-----------------------------  NOTE  ------------------------------+
 | Although journaling and recovery are quite reliable, the last few |
 | edits before a system failure may be lost.  The safest way to     |
 | protect your work against a system failure is to write out your   |
 | edits frequently---particularly during all-day editing sessions.  |
 +-------------------------------------------------------------------+