The EDIT commands perform the following functions:

  o  Invoke the Access Control List Editor  to  create  or  modify  an
     access control list for an object (see /ACL).

  o  Invoke the EDT screen-oriented editor (see /EDT).

  o  Invoke the FDL  editor  to  create  and  modify  File  Definition
     Language files (see /FDL).

  o  Invoke the SUMSLP batch-oriented editor to update a single  input
     file with multiple files of edit commands (see /SUM).

  o  Invoke the TECO editor (see /TECO).

  o  Invoke the TPU editor (see /TPU).

Additional information available:

/ACL/EDT/FDL/SUM/TECO/TPU

  Invokes the Access Control List (ACL) Editor to create or modify
  an access control list for a specified object.  For a complete
  description of the VMS Access Control List Editor, including
  information about the EDIT/ACL command and its qualifiers, see the
  VMS Access Control List Editor Manual.

  The /ACL qualifier is required.

  Format:


    EDIT/ACL  file-spec

Additional information available:

ParameterCommand QualifiersExamples

 object-spec

  Specifies the object whose access control list is to be created or
  edited using the ACL editor.  If the access control list does not
  exist, it is created.

  If the object is a file, the ACL editor does not provide a default
  file type.  If you omit the file type, it is presumed to be null.
  The specified file must be a disk file on a Files-11 Structure
  Level 2 formatted volume.  If the object is a directory, specify a
  file specification with the file type of DIR. If the object type is
  not a file,  you must specify the object type with the /OBJECT=type
  qualifer.

  No wildcard characters are allowed in the object specification.

Additional information available:

/JOURNAL/KEEP/MODE/OBJECT/RECOVER

 /JOURNAL[=file-spec]
 /NOJOURNAL

  Controls whether a journal file is created for the editing
  session.  By default, the ACL editor keeps a journal file that
  contains a copy of the ACL editor keypad actions made during  the
  editing  session.  The /JOURNAL qualifier controls the creation of
  a journal file for the editing session.  If you specify /NOJOURNAL,
  no journal file is generated.  If you omit the qualifier or specify
  /JOURNAL, a journal file is created.  If you omit the journal file
  specification,  by default, the journal file is named
  input-file-spec.JOU.

  No wildcard characters are allowed in the journal file
  specification.

  If your editing session ends abnormally,  you can invoke the ACL
  editor again and recover the changes made during the aborted
  session by simply specifying the /RECOVER qualifier and, if
  necessary, providing the name of the journal file, should it differ
  from the default name.

 /KEEP=(option[,...])

  Controls whether or not the session's journal file or recovery
  journal file will be deleted.  By default the session's journal
  file is deleted once an ACL editing session ends normally; by
  default, the recovery journal file is deleted once the ACL editing
  session is successfully restored.  The /KEEP qualifier allows you
  to save either the journal or the recovery journal file.  You can
  specify one or both of the following options:

  JOURNAL       Specifies that the journal file for this session is
                not to be deleted when the editing session terminates
                normally.

  RECOVER       Specifies that the journal file used for recovery is
                not to be deleted when the editing session has been
                successfully restored.

 /MODE=option

  Specifies the level of prompting to be used during the editing
  session.   By default, the ACL editor selects the prompting mode.
  Use the /MODE qualifier to specify one of these prompt options:

  PROMPT        Specifies that where possible the selected field
                within the ACE is initially filled with the first of a
                list of items that may apply to the field.

  NOPROMPT      Specifies that no prompting is used by the ACL editor.

 /OBJECT=type
 /OBJECT=FILE

  Specifies the type of the object whose ACL is being edited. By
  default, the ACL editor assumes that the object whose ACL is being
  edited is a file.  If the object is not a file, you must specify
  the object type with the /OBJECT qualifier.  The following keywords
  may be specified with /OBJECT:

  FILE                   Specifies that the object type is a file or a
                         directory file.

  DEVICE                 Specifies that the object type is a device.

  SYSTEM_GLOBAL_SECTION  Specifies that the object type is a system
                         global section.

  GROUP_GLOBAL_SECTION   Specifies that the object type is a group
                         global section.

  LOGICAL_NAME_TABLE     Specifies that the object type is a system
                         logical name table.

 /RECOVER[=file-spec]
 /NORECOVER

  Determines whether or not the ACL editor restores the file's ACL
  from a journal file prior to starting the editing session. The
  /RECOVER qualifier specifies that the ACL editor should restore the
  ACL from the journal file specified by input-file-spec.JOU. This
  operation restores the ACL to the state it was in when a previous
  ACL editing session ended abnormally.

  If the journal file has a file name other than input-file-spec.JOU,
  specify it with the /RECOVER qualifier.

  1.   $ EDIT/ACL/JOURNAL=SAVEACL MYFILE.DAT
          .
          .
          .
       User creates ACL until system crashes
          .
          .
          .
       $ EDIT/ACL/JOURNAL=SAVEACL/RECOVER=SAVEACL MYFILE.DAT
          .
          .
          .
       ACL is restored and user proceeds with editing until done
          .
          .
          .
         ^Z
       $

  The user initiates the ACL editing session by specifying that the
  journal file SAVEACL.JOU be saved if the session ends abnormally.
  The session proceeds until aborted by a system crash. To recover
  from the aborted editing session,  and continue with additional
  edits, the user issues the second EDIT/ACL command.   This session
  begins by restoring the session with the journal SAVEACL.JOU.  Once
  the editing session proceeds to a normal completion (with a
  Ctrl/Z), the journal file SAVEACL.JOU is deleted.

  2.   $ EDIT/ACL MYFILE.DAT
       (IDENTIFIER=[360,7],ACCESS=NONE)
       (IDENTIFIER=[360,*],ACCESS=READ+WRITE)
          .
          .
          .
       User edits the ACL.
          .
          .
          .
         ^Z
       $

  In this example the owner of the file MYFILE.DAT wants to modify
  the file's access control list.  A journal file called MYFILE.JOU
  is automatically created to record the ACL.  By default the editor
  enters prompt mode.  The system displays the two existing ACEs in
  this ACL.

  The user wants to change the UIC from [360,7]  to  [360,17].   The
  user makes the correction, presses the Enter key on the keypad, and
  then exits with Ctrl/Z.  Since this is a normal exit, the  journal
  file MYFILE.JOU is automatically deleted.

   Invokes the Digital Standard Editor (EDT) interactive text editor.
   The /EDT qualifier is not required, because EDT is the VMS default
   editor.

   Format

     EDIT  filespec

Additional information available:

PARAMETERQUALIFIERS

Examples

filespec
   Specifies the file to be created or edited using EDT. If the file
   does not exist, it is created by EDT.

   EDT does not provide a default file type when creating files; if
   you do not include a file type, it is null. The file must be a
   disk file on a Files-11 formatted volume.

   No wildcard characters are allowed in the file specification.

Additional information available:

/COMMAND/CREATE/JOURNAL/OUTPUT/READ_ONLY
/RECOVER

      /COMMAND[=filespec]
      /NOCOMMAND

   Determines whether or not EDT uses a startup command file. The
   /COMMAND file qualifier should be followed by an equal sign (=)
   and the specification of the command file. The default file type
   for command files is EDT. No wildcard characters are allowed in
   the file specification.

   The following command line invokes EDT to edit a file named
   MEMO.DAT and specifies that EDT use a startup command file named
   XEDTINI.EDT:

     $ EDIT/COMMAND=XEDTINI.EDT MEMO.DAT

   If you do not include the /COMMAND=command file qualifier, EDT
   looks for the EDTSYS logical name assignment. If EDTSYS is
   not defined, EDT processes the systemwide startup command file
   SYS$LIBRARY:EDTSYS.EDT. If this file does not exist, EDT looks for
   the EDTINI logical name assignment. If EDTINI is not defined, EDT
   looks for the file named EDTINI.EDT in your default directory. If
   none of these files exists, EDT begins your editing session in the
   default state.

   To prevent EDT from processing either the systemwide startup
   command file or the EDTINI.EDT file in your default directory,
   use the /NOCOMMAND qualifier as follows:

     $ EDIT/NOCOMMAND MEMO.DAT

      /CREATE (default)
      /NOCREATE

   Controls whether EDT creates a new file when the specified input
   file is not found.

   Normally, EDT creates a new file to match the input file
   specification if it cannot find the requested file name in the
   specified directory. When you use the /NOCREATE qualifier in the
   EDT command line and type a specification for a file that does
   not exist, EDT displays an error message and returns to the DCL
   command level as follows:

     $ EDIT/NOCREATE NEWFILE.DAT
     Input file does not exist
     $

      /JOURNAL[=journal-file]
      /NOJOURNAL

   Determines whether EDT keeps a journal during your editing
   session. A journal contains a record of the keystrokes you enter
   during an editing session. The default file name for the journal
   is the same as the input file name. The default file type is
   JOU. The /JOURNAL qualifier enables you to use a different file
   specification for the journal.

   The following command line invokes EDT to edit a file named
   MEMO.DAT and specifies the name SAVE.JOU for the journal:

     $ EDIT/JOURNAL=SAVE MEMO.DAT

   If you are editing a file from another directory and want the
   journal to be located in that directory, you must use the /JOURNAL
   qualifier with a file specification that includes the directory
   name. Otherwise, EDT creates the journal in the default directory.

   The directory that is to contain the journal should not be write-
   protected.

   To prevent EDT from keeping a record of your editing session, use
   the /NOJOURNAL qualifier in the EDT command line as follows:

     $ EDIT/NOJOURNAL MEMO.DAT

   Once you have created a journal, enter the EDT/RECOVER command to
   execute the commands in the journal. No wildcard characters are
   allowed in the file specification.

      /OUTPUT=output-file
      /NOOUTPUT

   Determines whether EDT creates an output file at the end of your
   editing session. The default file specification for both the input
   file and the output file is the same. Use the /OUTPUT qualifier to
   give the output file a different file specification from the input
   file.

   The following command line invokes EDT to edit a file named
   MEMO.DAT and gives the resulting output file the name OUTMEM.DAT:

     $ EDIT/OUTPUT=OUTMEM.DAT MEMO.DAT

   You can include directory information as part of your output file
   specification to send output to another directory as follows:

     $ EDIT/OUTPUT=[BARRETT.MAIL]MEMO.DAT MEMO.DAT

   The /NOOUTPUT qualifier suppresses the creation of an output
   file, but not the creation of a journal. If you decide that you do
   not want an output file, you can use the /NOOUTPUT qualifier as
   follows:

     $ EDIT/NOOUTPUT MEMO.DAT

   A system interruption does not prevent you from re-creating your
   editing session because a journal is still being maintained. To
   save your editing session, even when you specify /NOOUTPUT, use
   the line mode command WRITE to put the text in an external file
   before you end the session.

   No wildcard characters are allowed in the file specification.

      /READ_ONLY
      /NOREAD_ONLY (default)

   Determines whether EDT keeps a journal and creates an output file.
   With the /NOREAD_ONLY qualifier, EDT maintains the journal and
   creates an output file when it processes the line mode command
   EXIT. Using the /READ_ONLY qualifier has the same effect as
   specifying both the /NOJOURNAL and /NOOUTPUT qualifiers.

   The following command line invokes EDT to edit a file named
   CALENDAR.DAT, but does not create a journal or an output file:

     $ EDIT/READ_ONLY CALENDAR.DAT

   Use the /READ_ONLY qualifier when you are searching a file and do
   not intend to make any changes to it. To modify the file, use the
   line mode command WRITE to save your changes. Remember, however,
   that you have no journal.

      /RECOVER
      /NORECOVER (default)

   Determines whether EDT reads a journal at the start of the editing
   session.

   When you use the /RECOVER qualifier, EDT reads the appropriate
   journal and processes whatever commands it contains. The
   appropriate syntax is as follows:

     $ EDIT/RECOVER MEMO.DAT

   If the journal file type is not JOU or the file name is not the
   same as the input file name, you must include both the /JOURNAL
   qualifier and the /RECOVER qualifier as follows:

     $ EDIT/RECOVER/JOURNAL=SAVE.XXX MEMO.DAT

   Because the /NORECOVER qualifier is the default for EDT, you do
   not need to specify it in a command line.

   1.  $ EDIT/OUTPUT=NEWFILE.TXT OLDFILE.TXT
           1       This is the first line of the file OLDFILE.TXT.
       *

     This EDIT command invokes EDT to edit the file OLDFILE.TXT.
     EDT looks for the EDTSYS logical name assignment. If EDTSYS
     is not defined, EDT processes the systemwide startup command
     file SYS$LIBRARY:EDTSYS.EDT. If this file does not exist, EDT
     looks for the EDTINI logical name assignment. If EDTINI is
     not defined, EDT looks for the file named EDTINI.EDT in your
     default directory. If none of these files exists, EDT begins
     your editing session in the default state. When the session
     ends, the edited file has the name NEWFILE.TXT.

   2.  $ EDIT/RECOVER OLDFILE.TXT

     This EDIT command invokes EDT to recover from an abnormal
     exit during a previous editing session. EDT opens the file
     OLDFILE.TXT, and then processes the journal OLDFILE.JOU. Once
     the journal has been processed, the user can resume interactive
     editing.

  Invokes the VMS FDL Editor (EDIT/FDL) to create and modify  File
  Definition  Language  (FDL)  files.  The /FDL qualifier is required.
  For a complete  description  of  the  FDL  Utility,  including  more
  information  about  the EDIT/FDL command and its qualifiers, see the
  FDL Facility in the VMS File Definition Language Facility Manual.

  Format:


    EDIT/FDL  file-spec

Additional information available:

ParameterCommand QualifiersExamples

 file-spec

  Specifies the FDL file to be created, modified, or optimized by  the
  editing session.  The default file type is FDL.

Additional information available:

/ANALYSIS/CREATE/DISPLAY/EMPHASIS/GRANULARITY/NOINTERACTIVE
/NUMBER_KEYS/OUTPUT/PROMPTING/RESPONSES
/SCRIPT

 /ANALYSIS=fdl-file-spec

  Specifies the FDL file (generated by the Analyze/RMS_File Utility) to
  be used in the optimize script.

 /CREATE

  Allows you to create an output FDL file that does not exist without
  receiving a message from EDIT/FDL stating that the file will be
  created.

 /DISPLAY=graph-option

  Specifies the type of graph you want displayed.  Legal graph options
  are:

  LINE    Produces a graph of bucket size versus index depth as a
          two-dimensional plot.

  FILL    Produces a graph of bucket size versus load fill percent
          versus index depth.

  KEY     Produces a graph of bucket size versus key length versus
          index depth.

  RECORD  Produces a graph of bucket size versus record size versus
          index depth.

  INIT    Produces a graph of bucket size versus initial load record
          count versus index depth.

  ADD     Produces a graph of bucket size versus additional record
          count versus index depth.

  LINE is the default.

 /EMPHASIS=tuning-bias

  Allows you to choose between smaller buffers and flatter files.
  Legal options for the tuning-bias parameter are:

  FLATTER_FILES    Generally increases bucket size.  The bucket size,
                   in turn, controls the number of levels in the index
                   structure.  If a larger bucket size eliminates one
                   level,  then you should use this option.  At some
                   point, however, the benefit of having fewer levels
                   will  be offset by the cost of scanning through the
                   larger buckets.

  SMALLER_BUFFERS  Generally decreases the amount of memory you have
                   to  use.  Sequential files usually require only two
                   buffers.

  FLATTER_FILES is the default.

 /GRANULARITY=n

  Allows you to divide an indexed file into a specified number of
  areas.  The default is three areas.

 /NOINTERACTIVE

  Causes EDIT/FDL to execute the Optimize script without a terminal
  dialog.   You must have previously issued the ANALYZE/RMS_FILE/FDL
  command, specifying your existing RMS data file as the target file.
  If data is missing, EDIT/FDL uses the defaults.

 /NUMBER_KEYS=n

  Allows you to specify the number of keys in your indexed file.  You
  can define up to 255 keys.  The default is one key.

 /OUTPUT=fdl-file-spec

  Identifies an output file for storing the results of the EDIT/FDL
  session.   If you omit the /OUTPUT qualifier, the output FDL file
  will have the same name and file type as the input file with a
  version number one higher than the highest existing version of the
  file.

  The default file type is FDL.

 /PROMPTING=prompt-option

  Specifies the level of menu prompting to be used during the terminal
  session.  The valid prompt options are:

  BRIEF  Selects a terse level of prompting.

  FULL   Provides more detailed information about each menu question.

  By  default, EDIT/FDL chooses either BRIEF or FULL prompting
  depending  on the terminal class and line speed.  High-speed video
  terminals will get FULL, while nonscope terminals and terminals
  operating at less than 2400 baud get BRIEF.

 /RESPONSES=response-option

  Allows you to select how you want to respond to script questions.
  Legal options include:

  AUTOMATIC  Indicates that you automatically want all script default
             responses to be used.  If you select this option, you can
             use the /NOINTERACTIVE qualifier to cause EDIT/FDL to be
             executed automatically.

  MANUAL     Indicates that you want to provide all script responses.
             No default responses are automatically used.

  The default is AUTOMATIC.

 /SCRIPT=script-title
 /NOSCRIPT

  Controls whether to select a logically grouped sequence of questions
  for EDIT/FDL to ask.  Valid script titles are:

  ADD_KEY     Allows you to model or add to the attributes of a new
              index.

  DELETE_KEY  Allows you to remove attributes from the highest index
              of your file.

  INDEXED     Begins  a  dialog in which you are prompted for
              information about the indexed data file to be created
              from the FDL file.  EDIT/FDL supplies values for certain
              attributes.

  OPTIMIZE    Requires that you use the analysis information from an
              FDL file that was created with the Analyze/RMS_File
              Utility.  The FDL file itself is one of the inputs to
              the Edit/FDL Utility.  In other words, you may tune the
              parameters of all your indexes using the file statistics
              from ANALYZE/RMS_FILE.

  RELATIVE    Begins a dialog in which you are prompted for
              information about the relative data file to be created
              from the FDL file.  EDIT/FDL supplies values for certain
              attributes.

  SEQUENTIAL  Begins a dialog in which you are prompted for
              information about the sequential data file to be created
              from the FDL file.  EDIT/FDL supplies values for certain
              attributes.

  TOUCHUP     Begins a dialog in which you are prompted for
              information about the changes you wish to make to an
              existing index.

  The default is /NOSCRIPT.

  1.   $ EDIT/FDL INDEX

  This command creates or modifies an FDL file named INDEX.FDL.

  2.   $ EDIT/FDL/OUTPUT=NEWINDEX INDEX

  This command begins a session in which the contents of INDEX.FDL are
  read into the FDL editor and can then be modified.  A file named
  NEWINDEX.FDL is created, and INDEX.FDL is not changed.

  Invokes the SUMSLP batch-oriented editor to update source files.
  You enter text changes and editing commands in update files.  SUMSLP
  merges the update files containing the changes with the source file
  that you specify, and gives you a record of the changes in the form
  of an audit trail.

  For more information, see the VMS SUMSLP Utility Manual.

  Format:


  EDIT/SUM  file-spec

Additional information available:

ParameterCommand QualifiersPositional QualifierExample

 file-spec

  Specifies the source file to be edited.

Additional information available:

/LISTING/OUTPUT/HEADER

 /LISTING[=file-spec]

  Determines whether a sequence-numbered listing file, showing the
  original and inserted lines and an audit trail, is produced during
  the editing process. If you do not include a file specification,
  the listing file takes the same name as the input file, with a file
  type of LIS. By default, no listing file is produced.

 /OUTPUT[=file-spec]

  Specifies the output file to be used in the editing session.  If you
  do not include a file specification, the output file has the same
  name and type as the input file, with a version number one higher
  than the highest existing version.

 /HEADER/OUTPUT=file-spec

  Determines whether the output file is created as a VFC format
  sequential file with the line insert number and audit trail
  information in the record header block (RHB) for the records.

Additional information available:

/UPDATE

 /UPDATE[=(update-file-spec[,...])]

  Indicates the file or files containing the editing commands and
  changes to be applied to the input source file.   The default file
  type of these files is UPD.

  EDIT/SUM FILE1.MAR/UPDATE=(UPD1A,UPD1B.ENH)

  The input source file FILE1.MAR is updated with the merged contents
  of SUMSLP update files UPD1A.UPD and UPD1B.ENH.

   Invokes the TECO interactive text editor. The /TECO qualifier is
   required.

   Format

     EDIT/TECO  [filespec]

     EDIT/TECO/EXECUTE=command-file  [argument]

Additional information available:

PARAMETERQUALIFIERSEXAMPLES

filespec
   Specifies the file to be created or edited using the TECO editor.
   If the file does not exist, it is created by TECO, unless you
   specify the /NOCREATE qualifier. No wildcard characters are
   allowed in the file specification.

   If you specify the /MEMORY qualifier (default) without a file
   specification, TECO edits the file identified by the logical name
   TEC$MEMORY. If TEC$MEMORY has no equivalence string, or if the
   /NOMEMORY qualifier is specified, TECO starts in command mode and
   does not edit an existing file.

   If you specify the /MEMORY qualifier and a file specification, the
   file specification is equated to the logical name TEC$MEMORY.

Additional information available:

/COMMAND/CREATE/EXECUTE/MEMORY/OUTPUT/READ_ONLY

      /COMMAND[=filespec]
      /NOCOMMAND

   Controls whether a startup command file is used. The /COMMAND
   file qualifier may be followed by an equal sign (=)  and the
   specification of the command file. The default file type for
   command files is TEC.

   The following command line invokes TECO to edit a file named
   MEMO.DAT and specifies that TECO use a startup command file named
   XTECOINI.TEC:

     $ EDIT/TECO/COMMAND=XTECOINI.TEC MEMO.DAT

   If you do not include the /COMMAND qualifier, or if you enter
   /COMMAND without specifying a command file, TECO looks for the
   TEC$INIT logical name assignment. If TEC$INIT is not defined, no
   startup commands are executed.

   The logical name TEC$INIT can equate either to a string of TECO
   commands or to a dollar sign followed by a file specification.
   If TEC$INIT translates to a string of TECO commands, the string
   is executed; if it translates to a dollar sign ($)  followed by
   a file specification, the contents of the file are executed as a
   TECO command string. For further information, see the PDP-11 TECO
   Editor Reference Manual.

   To prevent TECO from using any startup command file, use the
   /NOCOMMAND qualifier as follows:

     $ EDIT/TECO/NOCOMMAND MEMO.DAT

   No wildcards are allowed in the file specification.

      /CREATE (default)
      /NOCREATE

   Creates a new file when the specified input file cannot be
   found. If the /MEMORY qualifier is specified and no input file
   is specified, the file created is the one specified by the logical
   name TEC$MEMORY. Normally, TECO creates a new file to match the
   input file specification if it cannot find the requested file name
   in the specified directory. When you use the /NOCREATE qualifier
   in the TECO command line and type a specification for a file that
   does not exist, TECO displays an error message and returns you to
   the DCL command level. The /CREATE and /NOCREATE qualifiers are
   incompatible with the /EXECUTE qualifier.

      /EXECUTE=command-file [argument]

   Invokes TECO and executes the TECO macro found in the command
   file. The argument, if specified, appears in the text buffer
   when macro execution starts. Blanks or special characters must
   be enclosed in quotation marks (" ").  For detailed information
   on the use of TECO macros, see the PDP-11 TECO Editor Reference
   Manual.

   The /EXECUTE qualifier is incompatible with the /CREATE and
   /MEMORY qualifiers.

      /MEMORY (default)
      /NOMEMORY

   Specifies that the last file you edited with TECO, identified by
   the logical name TEC$MEMORY, will be the file edited if you omit
   the file specification to the EDIT/TECO command.

      /OUTPUT=output-file
      /NOOUTPUT (default)

   Controls how the output file is named at the end of your editing
   session. By default, the output file has the same name as
   the input file but is given the next higher available version
   number. Use the /OUTPUT qualifier to give the output file a file
   specification different from the input file.

   The following command line invokes TECO to edit a file named
   MEMO.DAT and gives the resulting output file the name OUTMEM.DAT:

     $ EDIT/TECO/OUTPUT=OUTMEM.DAT MEMO.DAT

   You can include directory information as part of your output file
   specification to send output to another directory as follows:

     $ EDIT/TECO/OUTPUT=[BARRET.MAIL]MEMO.DAT MEMO.DAT

   No wildcard characters are allowed in the file specification.

      /READ_ONLY
      /NOREAD_ONLY (default)

   Controls whether an output file is created. By default, an output
   file is created; the /READ_ONLY qualifier suppresses the creation
   of the output file.

   1.  $ EDIT/TECO/OUTPUT=NEWFILE.TXT OLDFILE.TXT

     This EDIT command invokes the TECO editor to edit the
     file OLDFILE.TXT. TECO looks for the TEC$INIT logical name
     assignment. If TEC$INIT is not defined, TECO begins the editing
     session without using a command file. When the session ends,
     the edited file has the name NEWFILE.TXT.

   2.  $ EDIT/TECO/EXECUTE=FIND_DUPS "TEMP, ARGS, BLANK"

     In this example, the /EXECUTE qualifier causes the TECO macro
     contained in the file FIND_DUPS.TEC to be executed, with the
     argument string "TEMP, ARGS, BLANK" located in the text buffer.

 Invokes the VAX Text Processing Utility (TPU).  By default, this runs
 an editor called EVE (for Extensible VAX Editor).

 Format:

    EDIT/TPU[/qualifier...] [input-file]

 For example, the following command invokes TPU (running EVE) to
 create or edit a file named JABBER.TXT in your current, default
 directory:

    $ EDIT/TPU jabber.txt

 For information about TPU programming, see the VAX Text Processing
 Utility Manual.  For information about EVE, see the Guide to VMS Text
 Processing or the EVE Reference Manual, or use the online help in
 EVE.

Additional information available:

EVE EditorExamplesLogicalsParameterQualifiers

/COMMAND/CREATE/DEBUG/DISPLAY/INITIALIZATION
/INTERFACE/JOURNAL/MODIFY/OUTPUT/READ_ONLY
/RECOVER/SECTION/START_POSITION/WORK/WRITE

 The Extensible VAX Editor (EVE) is a general-purpose text editor
 created with TPU--in effect, the default TPU application.  You can
 use EVE on DECwindows or character-cell terminals (VT300, VT200, or
 VT100 series).  EVE reads and writes standard ASCII text files.

 Using EVE, you can do the following:

 o  Perform basic text editing and formatting operations
 o  Create or edit one or more files in an editing session
 o  Use multiple buffers and windows, and resize the windows
 o  Define keys, create learn sequences, and set EDT or WPS keypad
 o  Select boxes or linear ranges for cut-and-paste or other edits
 o  Use either VMS-style or ULTRIX-style wildcards to search text
 o  Execute DCL commands, such as DIRECTORY, from within the editor
 o  Run DECspell to check selected text or an entire buffer
 o  Spawn subprocesses or attach to other processes
 o  Compile and execute TPU procedures to extend EVE
 o  Add or delete menu items for the DECwindows interface
 o  Save your customizations for future sessions
 o  Use initialization files at startup or during an editing session
 o  Recover your work in case of a system failure during a session
 o  Get online help on commands, keys, menu items, and other topics

 To invoke EVE, use the EDIT/TPU command.  By default, this runs the
 standard EVE section file--EVE$SECTION.TPU$SECTION.  (See help on
 /SECTION.) You may want to create a symbol for invoking EVE by
 putting the following line in your LOGIN.COM file:

    $ eve :== EDIT/TPU    !  my symbol to invoke EVE

 If you specify an input file on the EDIT/TPU command line, EVE
 creates a buffer using the file name and file type for the buffer
 name, copies the file into that buffer, and displays it in the main
 window.  If the file does not exist--for example, if you are
 creating a new file--the buffer is empty.  If you do not specify an
 input file, EVE creates an empty buffer named Main.  See help on
 Parameters.

 By default, EVE tries to execute an initialization file named
 EVE$INIT.EVE in your current directory or in SYS$LOGIN (your top-
 level, login directory).  See help on /INITIALIZATION.

 Also, by default, EVE creates a buffer-change journal file for each
 buffer you create, so that if a system failure occurs during your
 editing session, you can recover your text.  See help on /JOURNAL.

  To enter EVE commands, press DO or PF4, type the command, and press
  RETURN.  For a keypad diagram and help on defined keys, press the
  HELP key (on VT100-series terminals, press PF2).  To exit from EVE,
  press F10 or Ctrl/Z.

 For more information about EVE, see the Guide to VMS Text Processing
 or the EVE Reference Manual, or use the online help in EVE, which
 provides "informational" topics on various features in addition to
 help on commands and keys.  In particular, you may want to read the
 following topics:

    New Features
    New User
    EDT Conversion
    EDT Differences
    WPS Differences

 For information about using EVE on DECwindows, see the DECwindows
 Desktop Applications Guide, or read the EVE help topic called
 DECwindows Differences.

 The source files for EVE are available in SYS$EXAMPLES.  For a list
 of the EVE source files, use the following command:

    $ DIRECTORY SYS$EXAMPLES:EVE$*.TPU

 1.  $ EDIT/TPU

     Invokes TPU.  By default, this runs EVE, creating an empty buffer
     named Main.  You can then simply start typing and editing, or you
     can specify the file you want to edit by using the GET FILE,
     OPEN, or OPEN SELECTED command.

 2.  $ EDIT/TPU /INTERFACE=DECWINDOWS

     Invokes TPU, running EVE, with the DECwindows interface.  For
     more information, see help on /DISPLAY or /INTERFACE.

 3.  $ EDIT/TPU jabber.txt

     Edits a file named JABBER.TXT in your current, default directory.
     If the file exists, EVE displays the text in the main window; if
     you are creating a new file, the main window is empty.

 4.  $ EDIT/TPU *.txt

     EVE lets you use logical names and wildcards to specify the input
     file.  If more than one file matches your request, EVE shows a
     list of the matching files to choose from--in this case, a list
     of files with the type .TXT.  If no file matches, EVE creates an
     empty buffer named Main.

 5.  $ EDIT/TPU memo.txt /RECOVER

     Recovers the text of MEMO.TXT by using a buffer-change journal
     file named MEMO_TXT.TPU$JOURNAL.  See help on /RECOVER.

 6.  $ DEFINE TPU$SECTION sys$login:mysection
     $ EDIT/TPU

     Defines the default section file as MYSECTION.TPU$SECTION in your
     top-level, login directory, and then invokes TPU using that
     section file, instead of the standard EVE section file.  See help
     on /SECTION.

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

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

 TPU$COMMAND            TPU 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              TPU debugger file to be compiled and executed
                        when you use /DEBUG.  Defining the logical
                        name does not automatically run the debugger
                        file when you invoke TPU.

 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
                        definition is EVE$SECTION.TPU$SECTION, the
                        standard EVE section file.  See help on
                        /SECTION.

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

 Defining the logical name for a command file or initialization file
 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 an
 EVE$INIT.EVE.  You can put the definition in your LOGIN.COM file.

 To override a definition, use the relevant command-line qualifier.
 For example, if you defined TPU$COMMAND and 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.

 input-file

 The text file you want to edit or create.  The file must be a disk
 file on a Files-11 formatted volume.  There is no default file type
 --if you do not specify a file type, the file type is null.
 Processing the input file depends on the TPU application you are
 using.  EVE handles the input file as follows:

 o  If you do not specify an input file, EVE creates an empty buffer
    named Main.  You can then simply start typing and editing, or you
    can specify the file you want to edit or create by using the GET
    FILE, OPEN, or OPEN SELECTED command.

 o  If you specify an input file, EVE creates a buffer using the file
    name and file type as the buffer name.  If the file exists, EVE
    copies it into the buffer and displays the text in the main
    window.  For example, the following command edits a file named
    JABBER.TXT:

       $ EDIT/TPU jabber.txt
       24 lines read from DISK$1:[ALICE]JABBER.TXT;4

    If the file does not exist--that is, if you are creating a new
    file--the buffer is empty.

 o  EVE lets you use logical names and wildcards to specify the file
    --for example, *.TXT.  You can create and edit more than one file
    in an editing session, but you can specify only one input file on
    the command line.  If more than one file matches your request, EVE
    displays a list of the matching files so you can choose the one
    you want.  For more information, use the online help in EVE and
    read the topic called Choices Buffer.

 o  If the input file you specify is ambiguous, EVE delays applying
    the following qualifiers (or their defaults) until after you
    resolve the ambiguity:

       /[NO]MODIFY
       /[NO]OUTPUT
       /[NO]READ_ONLY
       /START_POSITION
       /[NO]WRITE

 o  If you use a search list to specify the input file or use
    wildcards for the device (disk) or directory (such as [...]), EVE
    gets the first matching file.  If none of the files in the search
    list exists, EVE creates an empty buffer using the first file name
    in the search list (unless you used /NOCREATE).

 Qualifier Format                  Default
 ---------------------------------------------------------------------
 /[NO]COMMAND[=command-file]       /COMMAND=TPU$COMMAND.TPU

 /[NO]CREATE                       /CREATE

 /[NO]DEBUG[=debug-file]           /NODEBUG

 /[NO]DISPLAY[=interface]          /DISPLAY=CHARACTER_CELL

 /[NO]INITIALIZATION[=init-file]   /INITIALIZATION=EVE$INIT.EVE

 /INTERFACE[=interface]            /INTERFACE=CHARACTER_CELL

 /[NO]JOURNAL[=journal-file]       /JOURNAL

 /[NO]MODIFY                       /MODIFY

 /[NO]OUTPUT[=output-file]         /OUTPUT

 /[NO]READ_ONLY                    /NOREAD_ONLY

 /[NO]RECOVER                      /NORECOVER

 /[NO]SECTION[=section-file]       /SECTION=TPU$SECTION

 /START_POSITION=(row[,column])    /START_POSITION=(1,1)

 /WORK[=work-file]                 /WORK=SYS$SCRATCH:TPU$WORK.TPU$WORK

 /[NO]WRITE                        /WRITE

 NOTE:  Some of these qualifiers and their defaults are EVE-specific.
        Other TPU applications may handle the qualifiers differently.
        For more information, see the VAX Text Processing Utility
        Manual.

 /COMMAND[=command-file] (default)
 /NOCOMMAND

 Determines the TPU command file you want to use, if any.  A command
 file contains procedures and executable statements to extend the
 editor.  For example, you can use a command file to create additional
 EVE commands, define keys, or set attributes.  You can also use a
 command file to set up a special text-processing environment for
 creating your own TPU application or for batch editing.

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

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

 o  Name the command file TPU$COMMAND.TPU.

    By default, TPU looks for this command file in your current
    directory.  Thus, you can have a different command file for each
    directory.

 o  Define the logical name TPU$COMMAND to specify the command file.

    This lets you use that command file for all editing sessions,
    including when you invoke TPU within MAIL, and lets you keep that
    file in any convenient directory.  Defining the logical name
    overrides the search for the TPU$COMMAND.TPU file.  You can put
    the definition in your LOGIN.COM file.  For example, the following
    commands define TPU$COMMAND as MYPROCS.TPU in your top-level,
    login directory and then invoke TPU using that command file:

       $ DEFINE TPU$COMMAND sys$login:myprocs
       $ EDIT/TPU

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

    This overrides any definition of the logical name TPU$COMMAND and
    overrides the default search for the TPU$COMMAND.TPU file.  For
    example, the following command invokes TPU, using a command file
    named MYPROCS.TPU in your current, default directory:

       $ EDIT/TPU /COMMAND=myprocs

 If the command file you specify either with /COMMAND or by defining
 TPU$COMMAND is not found, the editing session is aborted returning
 you to the DCL level.

 If you do not want a command file executed, use /NOCOMMAND, typically
 if you defined the logical name TPU$COMMAND or created a
 TPU$COMMAND.TPU file.  Also, /NOCOMMAND makes startup faster because
 TPU then does not search for a command file and does not have to
 compile and execute code startup.

 At startup, TPU compiles and executes the command file, if one is
 being used, after loading a section file (if any) and before EVE
 executes an initialization file (if any).  Thus, procedures,
 settings, and key definitions in a command file override those in the
 section file.  For more information about command files, see the VAX
 Text Processing Utility Manual, or use the online help in EVE and
 read the topic called Command Files.

 In EVE, you can create or update a command file by using the SAVE
 ATTRIBUTES command to save menu definitions for the DECwindows
 interface and most global settings ("attributes").  For more
 information, see the EVE Reference Manual, or use the online help in
 EVE and read the topic called Attributes.

   /CREATE   (default)
   /NOCREATE

 Determines whether a buffer is created when the input file is not
 found.  Processing this qualifier depends on the TPU application you
 are using.

 For EVE, the default is /CREATE.  If the input file does not exist,
 EVE creates a buffer using the input file name and file type as the
 buffer name; or if you do not specify an input file, EVE creates an
 empty buffer named Main.

 Use /NOCREATE to avoid invoking the editor in case you mistype the
 input file specification, or to edit only an existing file.  Thus, if
 the input file is not found, the editing session is aborted, and you
 are returned to the DCL level, as in the following example:

    $ EDIT/TPU old.dat /NOCREATE
    Input file does not exist: OLD.DAT;
    $

   /DEBUG[=debug-file]
   /NODEBUG            (default)

 Determines whether you run a TPU debugger to test procedures for an
 application you are creating.  TPU compiles and executes the
 debugger file--before executing TPU$INIT_PROCEDURE.

 Using /DEBUG without specifying a debugger file runs the default TPU
 debugger (TPU$DEBUG.TPU), which provides commands to manipulate
 variables and to control program execution.  To start editing the
 code in the file you are debugging, use the GO command.  For more
 information about the debugger, read the comments in the
 TPU$DEBUG.TPU source file in SYS$SHARE, or see the VAX Text
 Processing Utility Manual, or use the online help in EVE:

    Command: HELP TPU Debugger

 There are two ways to specify a debugger file of your own:

 o  Define the logical name TPU$DEBUG to specify the debugger file,
    and then use EDIT/TPU/DEBUG.

    Defining the logical name does NOT by itself run the debugger when
    you invoke TPU.  It only specifies which debugger file is run when
    you use /DEBUG.  You can put the definition in your LOGIN.COM
    file.

 o  Use /DEBUG= and specify the debugger file on the command line.

    For example, the following command edits a file named MYPROCS.TPU,
    using a debugger file named MYDEBUG.TPU:

       $ EDIT/TPU myprocs.tpu /DEBUG=mydebug

 TPU assumes the debugger file is in SYS$SHARE.  If your debugger file
 is stored elsewhere, specify the device (disk) and directory of the
 debugger file.  You cannot use wildcards to specify the debugger
 file.  You can use only one debugger file at a time.  The default
 file type is .TPU.

 /DISPLAY[={CHARACTER_CELL (default) | DECWINDOWS}]
 /NODISPLAY

 Determines the type of screen display, if any.  /DISPLAY is the same
 as /INTERFACE.

 For example, the following command invokes TPU with the DECwindows
 interface:

    $ EDIT/TPU /DISPLAY=DECWINDOWS

 Then, if DECwindows is available, TPU displays the editing session in
 a separate window on your workstation screen, and enables DECwindows
 features---for example, the EVE screen layout then includes a menu
 bar and scroll bars, and you can use MB1 to move the cursor and
 select text.  If DECwindows is not available, TPU works as if on a
 character-cell terminal.  For information about using EVE on
 DECwindows, see the DECwindows Desktop Applications Guide, or use the
 online help in EVE and read the topic called DECwindows Differences.

 To specify your preferred display, you can define the logical name
 TPU$DISPLAY_MANAGER as either CHARACTER_CELL or DECWINDOWS.  However,
 as a general rule, do NOT define this logical as DECWINDOWS, because
 TPU should be initialized only once using the DECwindows interface.
 Because of this restriction, utilities calling TPU multiple times,
 such as using the editor within MAIL, would fail.

 Use /NODISPLAY for batch jobs or when you are using an unsupported
 terminal.  For batch jobs, you typically use a TPU command file or
 EVE initialization file, as in the following example, which uses a
 command file named BATCH.TPU:

    $ EDIT/TPU /NODISPLAY /COMMAND=batch

 This batch file should comprise a complete editing session, including
 EXIT or QUIT.  Note that some EVE commands cannot be used in batch
 because they prompt for a key press or other interactive response.

 /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 EVE initialization file for particular
    directories, 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 logical name EVE$INIT to specify the initialization
    file.

    This lets you use that initialization file for all editing
    sessions, including when you invoke EVE within MAIL, and lets you
    keep that file in any convenient directory.  Defining the logical
    name overrides the search for the EVE$INIT.EVE file.  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 logical name EVE$INIT and
    overrides the default search for the EVE$INIT.EVE file.  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 logical name EVE$INIT
 or created an EVE$INIT.EVE file.  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,
 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 (or first) buffer 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 set attributes or
 define keys for particular kinds of editing, or to execute a series
 of related commands.

 An initialization file is somewhat slower than a section file or
 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 EVE Reference Manual, or use the
 online help in EVE and read the topic called Initialization Files.

 /INTERFACE[={CHARACTER_CELL (default) | DECWINDOWS}]

 Same as /DISPLAY---determines the interface or screen display you
 want.  For example, the following command invokes TPU with the
 DECwindows interface:

    $ EDIT/TPU /INTERFACE=DECWINDOWS

 Then, if DECwindows is available, TPU displays the editing session in
 a separate window on your workstation screen, and enables DECwindows
 features---for example, the EVE screen layout includes a menu bar and
 scroll bars, and you can use MB1 to move the cursor and select text.
 If DECwindows is not available, TPU works as if on a character-cell
 terminal.  For information about using EVE on DECwindows, see the
 DECwindows Desktop Applications Guide, or use the online help in EVE
 and read the topic called DECwindows Differences.

 /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 Buffer           Buffer-Change Journal File
       ------------------------------------------------
       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
       * SCRATCH *           __SCRATCH__.TPU$JOURNAL

    Buffer-change journal files are created in the directory defined
    by the logical name TPU$JOURNAL.  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 disk and directory
    other than SYS$SCRATCH.

    Some editing operations may be slower because of buffer-change
    journaling, depending on the type or extent of changes, such as
    including a large file into the buffer 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.  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 enable 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 with /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 EVE
 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.  |
 +-------------------------------------------------------------------+

 /MODIFY   (default)
 /NOMODIFY

 Determines whether you can modify the main (or first) buffer.  Does
 not affect other buffers you create during the editing session.

 By default, TPU allows the buffer to be modified--that is, you can
 edit text in the buffer, and exiting writes out the buffer to a file,
 if the buffer has been modified (unless you used /NOWRITE or
 /READ_ONLY).  Use /NOMODIFY to view a file without making any
 changes.  You can then use cursor-movement commands but cannot change
 the text.

 For EVE, using /READ_ONLY or /NOWRITE makes the buffer unmodifiable
 unless you also use /MODIFY.  For example, the following command
 edits a file named PRACTICE.TXT, making the buffer read-only and
 making it modifiable, so you can practice editing or test procedures
 without writing out a file:

    $ EDIT/TPU practice.txt /READ_ONLY /MODIFY

 In EVE, the status line shows whether the buffer is unmodifiable.  If
 the buffer is modifiable, the status line shows the mode (insert or
 overstrike).  You can change the modification attribute of the buffer
 during your editing session by using the SET BUFFER command.

 /OUTPUT[=output-file] (default)
 /NOOUTPUT

 Determines the output file, if any, for the main (or first) buffer.
 Does not affect other buffers you create during the editing session.

 By default, the output file has the same specifications as the input
 file with a version number one higher than the highest version of the
 input file, or version 1 if you are creating a new file.

 Use /OUTPUT= and specify a file if you want the output file written
 in a different directory or to have a different name or file type.
 For example, the following command edits a file named ROUGH.LIS in
 your current, default directory, and, on exiting, writes the output
 file to FINAL.TXT in your top-level, login directory:

    $ EDIT/TPU rough.lis /OUTPUT=sys$login:final.txt

 You cannot use wildcards to specify the output file.  If you omit
 parts of the output file specification, such as the device (disk) or
 directory, TPU uses the corresponding parts of the input file
 specification, if there is one.

 Using /OUTPUT= and specifying an output file modifies the buffer, so
 that even if you make no changes to the text, exiting writes out the
 buffer to a file.

 For EVE, using /NOOUTPUT sets the Main (or first) buffer to read-only
 (sometimes called write-locked), so that exiting does not write out
 that buffer to a file.  This is useful to view a file without making
 any changes.  If you change your mind and want to write out the
 buffer before exiting, use the WRITE FILE, SAVE FILE, or SAVE FILE AS
 command.  Also, you can change the read/write attribute of the buffer
 during your editing session by using the SET BUFFER command.

 /READ_ONLY
 /NOREAD_ONLY (default)

 Determines whether exiting writes the main (or first) buffer to a
 file.  Does not affect other buffers you create during the editing
 session.

 /READ_ONLY is the same as /NOWRITE.  For EVE, this makes the Main (or
 first) buffer write-locked and also makes it unmodifiable, unless you
 used /MODIFY.  Use /READ_ONLY to view a file without making any
 changes.  For example, the following command lets you view a file
 named STAFFMEMO.TXT, so you can use cursor-movement commands but
 cannot change the text:

    $ EDIT/TPU staffmemo.txt /READ_ONLY

 /NOREAD_ONLY is the same as /WRITE.  On exiting, EVE writes out the
 Main (or first) buffer to a file if the buffer has been modified.  If
 necessary, EVE prompts you for the output file name.

 In EVE, the status line shows whether the buffer is read-only or
 write.  Also, you can change the read/write and modification
 attributes of the buffer during your editing session by using the SET
 BUFFER command.

 /RECOVER
 /NORECOVER (default)

 Determines whether TPU recovers your edits by reading the journal
 file from the interrupted editing session.  (See help on /JOURNAL.)

 There are two ways to recover your edits, depending on the type of
 journaling you used:

 o  If you used buffer-change journaling, which is the EVE default,
    you recover one buffer at time and you can recover buffers from
    different editing sessions.  For example, the following command
    invokes EVE to recover the text of a file named JABBER.TXT:

       $ EDIT/TPU jabber.txt /RECOVER

    This is the same as invoking EVE and using the following command:

       Command: RECOVER BUFFER jabber.txt

    If there is more than one buffer-change journal file with the same
    name--for example, you may have two or more MAIN.TPU$JOURNAL
    files from different editing sessions--the recovery uses the
    highest version number available.  To recover several text
    buffers, one after another, use the RECOVER BUFFER ALL command.

    Recovery with a buffer-change journal file restores only your text
    --it does not restore settings, key definitions, and other
    customizations and it does not restore the contents of the Insert
    Here buffer or other system buffers.  The recovery is usually
    quite fast.  New text or other changes are then journaled.

    The recovery does not re-create deleted files.  If you deleted or
    renamed the source file associated with a buffer-change journal,
    the recovery fails.  The source file is either the file initially
    read into the buffer (if any), or the last version of the file
    written from the buffer before the system failure.

 o  If you used keystroke journaling, you recover your editing session
    by reissuing the command for the original, aborted editing session
    --including all qualifiers--and adding /RECOVER.  EVE then
    recovers your editing session in a "player piano" fashion.  For
    example, the following commands invoke TPU creating a keystroke
    journal file, and then, after a system failure, recover the
    editing session:

       $ EDIT/TPU /JOURNAL=myjournal.tjl
                  .
                  .
       ***  system failure  ***
                  .
                  .
       $ EDIT/TPU /JOURNAL=myjournal.tjl /RECOVER

    Typically, after the recovery, you exit to save your edits.

 Keystroke journaling does not work on DECwindows and has other
 restrictions, as follows.  These restrictions do NOT apply to buffer-
 change journaling.

 o  To recover your edits with a keystroke journal file, all relevant
    files must be in the same state as at the start of the session
    being recovered--including any files you wrote out (saved) before
    the system failure.  Therefore, before doing the recovery, you
    should rename the saved versions or move them to a different
    directory, to ensure that the recovery uses the original versions
    of the files.

 o  Check that logical names for your section file, command file, and
    initialization file are defined as for the original editing
    session, and that the recovery will use the correct version of
    these files.

 o  Check that the following terminal settings are the same as when
    you began the original editing session, because they may affect
    how your keystrokes are replayed:

       Device_Type
       Edit_mode
       Eightbit
       Page
       Width

 o  Recovery with a keystroke journal file may fail or may not work
    properly if you used Ctrl/C during the original editing session.
    Ctrl/C is not recorded in the keystroke journal file.  Therefore,
    when you recover your edits, an operation that was canceled with
    Ctrl/C is replayed without interruption; this is likely to affect
    how the remaining keystrokes are replayed.

 o  If you used EVE as a "kept" editor, the keystroke journal file
    records ATTACH, DCL, and SPAWN commands in EVE, but does not
    record operations done in the other process or subprocess.  If
    these other operations affected any files used in the original
    editing session---for example, if you spawned a subprocess from
    EVE and then purged, renamed, deleted, or modified any relevant
    files---the recovery may fail or may not work properly.

 o  If you used the EVE command DCL, the recovery may fail or may not
    work properly, particularly if you cut a file name from a
    directory list in the DCL buffer and pasted it into an EVE
    command line.  The keystroke recovery replays the operations, but
    the directory list or the file name may not be the same as in the
    original session.

 For more information about journaling and recovery, see the EVE
 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.  |
 +-------------------------------------------------------------------+

 /SECTION[=section-file] (default)
 /NOSECTION

 Determines the section file you want to use, if any.  A section file
 contains, in binary form, key definitions, compiled procedures, and
 other extensions.  Effectively, the section file is the TPU
 application you run--whether a customized version of EVE or an
 application you have created.

 TPU assumes the section file is in SYS$SHARE.  If your section file
 is stored elsewhere, specify the device (disk) and directory of the
 section file.  You cannot use wildcards to specify the section file.
 You use only one section file at a time.  Default file type is
 .TPU$SECTION.

 The default section file is defined systemwide by the logical name
 TPU$SECTION, which specifies the standard EVE section file
 (EVE$SECTION.TPU$SECTION).

 There are two ways to specify the section file you want to use:

 o  Define the logical name TPU$SECTION to specify the section file.

    This lets you use that section file for all editing sessions,
    including when you invoke TPU within MAIL.  Your definition
    overrides the systemwide default.  You can put the definition in
    your LOGIN.COM file.  For example, the following commands define
    the default section file as MYSECTION.TPU$SECTION in your top-
    level, login directory, and then invoke TPU using that section
    file instead of the standard EVE section file:

       $ DEFINE TPU$SECTION sys$login:mysection
       $ EDIT/TPU

 o  Use /SECTION= and specify the section file on the command line.

    This overrides any definition of the TPU$SECTION logical name,
    whether a definition of your own or the systemwide default.  For
    example, the following command invokes TPU, using a section file
    named MYSECTION.TPU$SECTION in your top-level, login directory:

       $ EDIT/TPU /SECTION=sys$login:mysection

 If you use /NOSECTION, TPU does not use any section file.  This
 prevents even the default EVE interface from being used.  TPU will be
 unusable unless you specify a command file with procedures and
 executable statements that set up a text-processing environment.  Use
 /NOSECTION when you are creating your own application without using
 EVE as a base, or with /NODISPLAY for batch editing.

 At startup, TPU first loads a section file, if one is being used,
 before compiling and executing a command file (if any) and before EVE
 executes an initialization file (if any).  Thus, procedures,
 settings, and key definitions in a command file or initialization
 file override those in a section file.

 To create a section file, do either of the following:

 o  In EVE, use the SAVE EXTENDED EVE command.  For example, the
    following command creates a section file named
    MYSECTION.TPU$SECTION in your current, default directory:

       Command: SAVE EXTENDED EVE mysection
       DISK$1:[USER]MYSECTION.TPU$SECTION;1 created
       903 procedures, 1168 variables, 621 keys saved

 o  In a TPU command file, use the SAVE built-in, usually at the end
    of the command file.  For example, the following statements create
    a section file named MYSECTION.TPU$SECTION in your top-level,
    login directory and then exit:

       SAVE ("sys$login:mysection"); ! create the section file
       EXIT;                         ! done---end of command file

 A section file is cumulative; it saves the current key definitions
 and other customizations--and those already in the section file you
 are using.  In EVE, the section file saves the following:

    *  Compiled procedures
    *  Global settings ("attributes")
    *  Key definitions and LEARN sequences
    *  Menu definitions for the DECwindows interface

 A section file usually does NOT save the following:

    *  Margins, tab stops, and other buffer settings
    *  Width or number of windows
    *  Contents of system buffers, such as the Insert Here buffer

 For more information, see the VAX Text Processing Utility Manual or
 EVE Reference Manual, or use the online help in EVE and read the
 topic called Section Files.

 /START_POSITION=(row[,column])

 Determines the row and column where the cursor first appears in the
 main (or first) buffer.

 For EVE, the default start position is 1,1, which is the upper left
 corner of the Main (or first) buffer--row 1, column 1.  Does not
 affect the initial cursor position when you create other buffers
 during the editing session, and does not limit the buffer size.

 Use /START_POSITION to begin editing at a particular line (or row) or
 at a particular character position (or column), such as when you want
 to skip over a standard heading in a file, or if a batch log file or
 error message tells you there is an error on a given line of a
 program, you can specify that line number as the starting row, so
 that when you edit the program source file, the cursor moves directly
 to that line.  For example, the following command edits a file named
 TEST.COM, putting the cursor on line 10, column 5:

    $ EDIT/TPU test.com /START_POSITION=(10,5)

 If you simply want to begin editing at the start of a particular line
 in the input file, you can omit the second parameter (the column) and
 need not use parentheses.

 /WORK[=work-file]

 Determines the work file TPU uses to swap memory for editing
 very large files.  The work file is a temporary file, which is
 automatically deleted when you exit.  Also, the work file is
 invisible---that is, it does not appear in the directory listing,
 although it does take up a file slot.

 You cannot use wildcards to specify the work file.  There is one work
 file per editing session.  Default file type is .TPU$WORK.

 By default, VAXTPU creates a work file named TPU$WORK.TPU$WORK in
 SYS$SCRATCH, which is usually your top-level, login directory.  There
 are two ways to specify a different work file:

 o  Define the logical name TPU$WORK to specify the work file.

    This is useful if you want the work file created in an area other
    than SYS$SCRATCH, such as on a larger disk.  You can put the
    definition in your LOGIN.COM file.

 o  Use /WORK= and specify the work file you want created or the
    device (disk) and directory for the work file.

    This overrides any definition of the TPU$WORK logical name.  For
    example, the following command invokes TPU, specifying the work
    file to be MYWORK.TPU$WORK:

       $ EDIT/TPU /WORK=mywork

 /WRITE   (default)
 /NOWRITE

 Determines whether exiting writes the main (or first) buffer to a
 file.  Does not affect other buffers you create during the editing
 session.

 /WRITE is the same as /NOREAD_ONLY.  On exiting, EVE writes out the
 Main (or first) buffer to a file if the buffer has been modified.  If
 necessary, EVE prompts you for the output file name.

 /NOWRITE is the same as /READ_ONLY.  For EVE, this makes the Main (or
 first) buffer write-locked and also makes it unmodifiable, unless you
 used /MODIFY.  Use /NOWRITE to view a file without making any
 changes.  For example, the following command lets you view a file
 named STAFFMEMO.TXT, so you can use cursor-movement commands but
 cannot change the text:

    $ EDIT/TPU staffmemo.txt /NOWRITE

 In EVE, the status line shows whether the buffer is read-only or
 write.  Also, you can change the read/write and modification
 attributes of the buffer during your editing session by using the SET
 BUFFER command.