/INITIALIZATION[=init-file] (default)
  /NOINITIALIZATION

  Determines the initialization file you want to use, if any.
  Processing this qualifier depends on the TPU application you are
  using.  An EVE initialization file contains a list of EVE commands
  you want executed, typically to set margins, tab stops, and other
  attributes, or to define keys that you do not otherwise save in a
  section file.

  You cannot use wildcards to specify the initialization file.  You can
  specify only one initialization file at a time.  Default file type is
  .EVE.

  There are three ways to specify the EVE initialization file you want
  to use:

  o  Name the initialization file EVE$INIT.EVE.

     By default, EVE first looks for this initialization file in your
     current directory.  If the file is not found there, EVE then looks
     for it in SYS$LOGIN (your top-level, login directory).  Thus, you
     can have different initialization files for different directories
     or subdirectories, and you can have a "standard" initialization
     file in SYS$LOGIN for editing in directories that do not have an
     EVE$INIT.EVE file.

  o  Define the EVE$INIT logical name to specify the initialization
     file.

     This lets you use that initialization file for all editing
     sessions---including when you invoke TPU within MAIL or other
     utilities---and lets you keep that file in any convenient
     directory or subdirectory.  Defining the logical name overrides
     the search for the EVE$INIT.EVE file.  If you omit parts of the
     file specification from the logical name definition---for example,
     if you do not specify a device (disk)---EVE supplies them from
     SYS$DISK:EVE$INIT.EVE or SYS$LOGINEVE$INIT.EVE.  You can put the
     definition in your LOGIN.COM file.  For example, the following
     commands define EVE$INIT as MYINIT.EVE in your top-level, login
     directory and then invoke EVE using that initialization file:

        $ DEFINE EVE$INIT sys$login:myinit
        $ EDIT/TPU

  o  Use /INITIALIZATION= and specify the initialization file on the
     command line.

     This overrides any definition of the EVE$INIT logical name and
     overrides the default search for the EVE$INIT.EVE file.  If you
     omit parts of the file specification---for example, if you do not
     specify a device (disk)---EVE supplies them first from the logical
     name (if defined), and then from SYS$DISK:EVE$INIT.EVE or
     SYS$LOGINEVE$INIT.EVE.  For example, the following command invokes
     EVE, using an initialization file named MYINIT.EVE in your
     current, default directory:

        $ EDIT/TPU /INITIALIZATION=myinit

  If you do not want an initialization file executed, use
  /NOINITIALIZATION---typically if you defined the EVE$INIT logical
  name or created an EVE$INIT.EVE file but do not want it executed for
  a particular editing session.  Also, /NOINITIALIZATION makes startup
  faster because EVE then does not search for an initialization file
  and does not have to parse commands at startup.

  At startup, EVE executes an initialization file (if any) after TPU
  loads the section file and executes a command file (if any).  Thus,
  you can use an initialization file in conjunction with a TPU
  command file.  Settings and key definitions in an initialization file
  override those in a section file or command file.  When you invoke
  EVE, commands in an initialization file for margins, tab stops, and
  other buffer settings apply to the MAIN buffer (or buffers initially
  created from your input files) and to an EVE system buffer named
  $DEFAULTS$.  Buffers created during the session will have the same
  settings as $DEFAULTS$.  For more information, use the online help in
  EVE and read the topic called Defaults.

  If a command in an initialization file is incomplete---for example,
  if a command requires a file name, search string, or other parameter
  ---EVE prompts you for the required information before going on.  You
  can also execute an initialization file during an EVE session by
  using the @ command (at sign).  This is useful to execute a series of
  related commands or to set attributes or define keys for particular
  kinds of editing.

  An initialization file is somewhat slower than a section file or
  TPU command file, depending on the number of commands to be
  executed.  If you want to define several keys, you should save them
  in a section file.  For more information, see the Extensible
  Versatile Editor Reference Manual or use the online help in EVE and
  read the topic called Initialization Files.