/sys$common/syshlp/helplib.hlb EDIT, /TPU, Logical Names  *Conan The Librarian (sorry for the slow response - running on an old VAX)

  You can define the following logical names for DECTPU and EVE startup
  files and other features instead of having to use command-line
  qualifiers:

  Logical names          Definitions and usage
  ---------------------------------------------------------------------
  EVE$INIT               EVE initialization file, typically to set
                         margins, tab stops, and other attributes, or
                         to define keys.  See help on /INITIALIZATION.

  EVE$KEYPAD             EVE keypad.  This logical lets you choose
                         between the various keypads.  Valid
                         equivalence names are EDT, EVE, NUMERIC,
                         VT100, and WPS.  If the logical name is not
                         defined, the keypad defaults to EVE which
                         gives the VT100 keypad on VT100 terminals or
                         the NUMERIC keypad on VT200 and later
                         terminals.  This logical name overrides any
                         keypad setting saved in a section file.  Users
                         can override the effect of this logical name
                         by setting the keypad in their initialization
                         file or command file.  This logical name has
                         no equivalent qualifier.

                         If you extend EVE with your own keypad, you
                         can also define the logical name to be the
                         name of your keypad.  For example, assume you
                         have created a keypad named SIMPLE, and have a
                         procedure named EVE_SET_KEYPAD_SIMPLE that
                         sets the keypad.  If you define the logical
                         name to be SIMPLE, EVE will invoke your keypad
                         during startup.

  TPU$CHARACTER_SET      Character set to use to display characters
                         having the 8th bit set.  This affects how
                         DECTPU converts text to lowercase or
                         uppercase, and how it removes diacritical
                         marks from text.  See help on /CHARACTER_SET.

  TPU$COMMAND            DECTPU command file to extend EVE, set up a
                         special text-processing environment for batch
                         editing, or create your own application.  See
                         help on /COMMAND.

  TPU$DEBUG              DECTPU debug file to be compiled and executed
                         when you use /DEBUG.  Defining TPU$DEBUG does
                         not automatically run the debug file when you
                         invoke DECTPU.

  TPU$DISPLAY_MANAGER    Screen display or interface.  See help on
                         /DISPLAY or /INTERFACE.

  TPU$JOURNAL            Directory for buffer-change journal files.
                         Does not apply to keystroke journal files.
                         Default is SYS$SCRATCH.  See help on /JOURNAL.

  TPU$SECTION            Section file---either a customized version of
                         EVE or an application you created.  Default is
                         EVE$SECTION.TPU$SECTION, the standard EVE
                         section file.  See help on /SECTION.

  TPU$WORK               Work file which DECTPU uses to swap memory for
                         editing very large files.  See help on /WORK.

  Defining TPU$COMMAND or EVE$INIT makes startup faster than having the
  editor search for the respective default file.  For example, if there
  is an EVE initialization file you want to use for all or most editing
  sessions, you should define EVE$INIT to specify that file, rather
  than have EVE search for the EVE$INIT.EVE file.  You can put the
  definitions in your LOGIN.COM file.

  To override a definition, use the relevant command-line qualifier.
  For example, if you defined TPU$COMMAND but want to use a different
  command file for a particular editing session, use /COMMAND= and
  specify the command file; or if you do not want a command file used
  for a particular editing session, use /NOCOMMAND.