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 TPU editor (see /TPU).

Additional information available:

/ACL/EDT/FDL/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 VAX/VMS Access  Control  List  Editor,  including
  information  about  the EDIT/ACL command and its qualifiers, see the
  VAX/VMS Access Control List Editor Reference Manual.

  The /ACL qualifier is required.

  Format:


    EDIT/ACL  file-spec

Additional information available:

ParametersCommand 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].   After
  the user makes the correction, presses ENTER 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 VAX EDT interactive text editor.  The /EDT qualifier  is
  not required, because EDT is the VAX/VMS default editor.

  Format:


    EDIT  file-spec

Additional information available:

ParametersCommand QualifiersExamples

 file-spec

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

  The EDT editor 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[=file-spec]
 /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.

  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

  No wildcard characters are allowed in the file specification.

 /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 /NOCREATE in the EDT
  command line and type a specification  for  a  file  that  does  not
  exist,  EDT  prints  an  error  message  and  returns you 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  file  during  your  editing
  session.   The default file name for the journal file 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 file.

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

  If you are editing a  file  from  another  directory  and  want  the
  journal  file  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 file in the
  default directory.

  The directory that is to contain the  journal  file  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 file, use the /RECOVER qualifier  to
  have EDT process the commands contained in the journal file.

  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 file.  If you are testing some
  edits and are not  sure  you  want  an  output  file,  you  can  use
  /NOOUTPUT as follows:
       $ EDIT/NOOUTPUT MEMO.DAT

  A system interruption will not  prevent  you  from  recreating  your
  editing  session  because  a journal file is still being maintained.
  If you decide you want to save your editing session, you can do  so,
  even  though you specified /NOOUTPUT, by using 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 file and  creates  an  output
  file.  With the default /NOREAD_ONLY, EDT maintains the journal file
  and creates an output file when it processes the line  mode  command
  EXIT.   Using  the  /READ_ONLY  qualifier  is  like  using  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 file or an output file:
       $ EDIT/READ_ONLY CALENDAR.DAT

  Use /READ_ONLY when you are searching a file.  If you then  want  to
  modify  the  file,  use  the  line  mode  command WRITE to save your
  changes.  Remember, however, that you have no journal file.

 /RECOVER
 /NORECOVER (default)

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

  When you use the  /RECOVER  qualifier,  EDT  reads  the  appropriate
  journal  file  and  processes  whatever  commands  it contains.  The
  appropriate syntax 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 /NORECOVER 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  the  EDT  editor  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 the EDT editor to recover from an abnormal
  exit  during  a  previous  editing  session.   EDT  opens  the  file
  OLDFILE.TXT, and then processes the journal file OLDFILE.JOU.   Once
  the  journal  file  has  been  processed, you can resume interactive
  editing.

  Invokes the VAX/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  VAX/VMS  File  Definition  Language  Facility
  Reference Manual.

  Format:


    EDIT/FDL  file-spec

Additional information available:

ParametersCommand 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 VAX Text Processing Utility (VAXTPU).  By  default,  the
  Extensible VAX Editor (EVE) is used as the interface for VAXTPU.  To
  invoke VAXTPU with the EDT Keypad  Emulator  interface,  define  the
  logical TPUSECINI to point to the section file for that interface as
  follows:
       $ DEFINE TPUSECINI EDTSECINI

  Format:


    EDIT/TPU  [file-spec]

Additional information available:

ParametersCommand QualifiersExamples

 file-spec

  Specifies the file to be created or edited using one of  the  VAXTPU
  editing  interfaces.   If  the  file you specify does not exist, the
  VAXTPU interfaces provide a buffer in which to create the file.   If
  you  write  out the contents of the buffer (either with the built-in
  procedure WRITE_FILE or by exiting from the editor), VAXTPU  creates
  the file in the appropriate directory.

  If you do not provide a file specification as a parameter  when  you
  invoke  VAXTPU,  when  you try to leave the editor, you are prompted
  for a file name for any buffer that you modified.

  VAXTPU does not provide a default file type when creating files.  If
  you  do  not  specify  a file type, the file type is null.  The file
  must be a disk file on a Files-11 formatted volume.

  Whether or not VAXTPU recognizes wildcard characters as  a  part  of
  the input file specification depends on the interface you are using.
  EVE handles wildcard characters if there is a single match  for  the
  wildcard  character.   Otherwise,  EVE prompts within the editor for
  possible file names.  EVE treats multiple files in a search list  in
  the same way as multiple files in a wildcard specification.  The EDT
  Keypad Emulator does not recognize wildcard characters.

Additional information available:

/COMMAND/CREATE/DISPLAY/JOURNAL/OUTPUT/READ_ONLY
/RECOVER/SECTION

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

  Determines whether VAXTPU reads  a  user-written  command  file  for
  initialization purposes.  The default file type for command files is
  TPU.  By default, VAXTPU tries to read a file called TPUINI.TPU from
  your default directory.  You can use a full file specification after
  the qualifier /COMMAND or define the logical name TPUINI to point to
  a command file other than the default one.

  To prevent VAXTPU from processing a command file, use the  qualifier
  /NOCOMMAND.   Using /NOCOMMAND when you do not want to use a command
  file decreases startup time by eliminating the search for a  command
  file.

 /CREATE (default)
 /NOCREATE

  Controls whether VAXTPU creates a new file when the specified  input
  file  is  not  found.   The  interface  that is layered on VAXTPU is
  responsible for processing this qualifier.  The  interface  can  get
  information  on  whether the qualifier was specified when VAXTPU was
  invoked by using the built-in procedure GET_INFO, for example, x  :=
  GET_INFO (COMMAND_LINE, "create").  For information on GET_INFO, see
  Section 4 of the VAX Text Processing Utility Reference Manual.

  By default, the VAXTPU interfaces  provide  a  buffer  in  which  to
  create  a file.  If you write out the contents of the buffer (either
  with the built-in  procedure  WRITE_FILE  or  by  exiting  from  the
  editor), VAXTPU creates a new file for the input file specification.
  When you use the qualifier /NOCREATE and enter a file  specification
  that  does  not  exist,  EVE  and  the EDT Keypad Emulator clear the
  screen, display an error message, and return you to the DCL  command
  level as follows:

       $ EDIT/TPU/NOCREATE NEWFILE.DAT
         Input file does not exist: DISK$:[USER]NEWFILE.DAT;
       $

 /DISPLAY[=file-spec] (default)
 /NODISPLAY

  Determines whether a VAXTPU session is run from a supported terminal
  and  uses  terminal  functions  such  as  the screen display and the
  keyboard.  By default your VAXTPU session is  run  with  the  screen
  management  file, TPU$CCTSHR.EXE, for terminals that respond to ANSI
  control functions and that operate in ANSI mode.

  VAXTPU expects sessions to be run from a supported  terminal  unless
  you specify /NODISPLAY.  If an unsupported input device is used when
  /DISPLAY is active, VAXTPU returns an error message and the  session
  is  terminated.   (See Appendix B of the VAX Text Processing Utility
  Reference Manual for information on terminals supported by VAXTPU.)

  The qualifier /NODISPLAY causes VAXTPU  to  run  without  using  the
  screen  display  and  the keyboard functions of a terminal.  Use the
  qualifier /NODISPLAY under the following conditions:

  o  When running VAXTPU procedures in a batch job

  o  When using VAXTPU on an unsupported terminal

  If you use /NODISPLAY, window and screen manipulation  commands  and
  key  definitions  cause  errors.   Initialization files that contain
  screen manipulation commands (ADJUST_WINDOW, CREATE_WINDOW, MAP) and
  key  definitions  can  run  when  the  /NODISPLAY feature is active.
  However, the commands are meaningless  and  may  even  return  error
  messages  in  the  batch  log file or on your screen.  Use a special
  initialization file (either a section file or a  command  file)  for
  sessions  in  which  you  use  the  qualifier /NODISPLAY.  This file
  should not include key definitions or screen  manipulation  commands
  (except  for  READ_LINE, MESSAGE, and LAST_KEY, which work with some
  restrictions).  See the descriptions of READ_LINE  and  LAST_KEY  in
  Section  4 of the VAX Text Processing Utility Reference Manual for a
  list of the restrictions.  The file  should  be  a  complete  VAXTPU
  session; it should end with the command EXIT or the command QUIT.

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

  Determines whether VAXTPU keeps  a  journal  file  of  your  editing
  session  so  that  you can recover from an interrupted session.  The
  interface that is layered on VAXTPU is  responsible  for  processing
  this  qualifier.   The  interface can get information on whether the
  qualifier was  specified  when  VAXTPU  was  invoked  by  using  the
  built-in   procedure   GET_INFO,   for   example,   x   :=  GET_INFO
  (COMMAND_LINE, "journal").  For information on GET_INFO, see Section
  4 of the VAX Text Processing Utility Reference Manual.

  By default, the VAXTPU interfaces maintain a journal file  that  has
  the  same  name  as  the  input  file and the file type TJL.  If you
  invoke VAXTPU without a file specification, the default name for the
  journal  file  is  TPU.TJL.   Use a full file specification with the
  qualifier /JOURNAL to specify a different name for the journal file.

  If you edit a file from another directory and you want  the  journal
  file  to  be  located  in that directory, you must use the qualifier
  /JOURNAL with a file specification that includes the directory name.
  Otherwise,  the  VAXTPU  interfaces  create  the journal file in the
  default directory.

  Once you create a journal file, invoke  VAXTPU  with  the  qualifier
  /RECOVER to cause VAXTPU to process the journal file.

  To prevent VAXTPU from keeping  a  journal  file  for  your  editing
  session, use the qualifier /NOJOURNAL.

 /OUTPUT=output-file (default)
 /NOOUTPUT

  Determines whether VAXTPU creates an output file at the end of  your
  editing  session.   The  interface  that  is  layered  on  VAXTPU is
  responsible for processing this qualifier.  The  interface  can  get
  information  on  whether the qualifier was specified when VAXTPU was
  invoked with the built-in procedure  GET_INFO,  for  example,  x  :=
  GET_INFO (COMMAND_LINE, "output").  For information on GET_INFO, see
  Section 4 of the VAX Text Processing Utility Reference Manual.

  By default, the VAXTPU interfaces use the  same  file  specification
  for  both the input file and the output file.  The output file has a
  version number one higher than the highest existing version  of  the
  input  file.  Use a file specification with the qualifier /OUTPUT to
  specify a file name that is different from the input file.  You  can
  include   directory   information   as  part  of  your  output  file
  specification to send output to another directory.

  The qualifier /NOOUTPUT suppresses the creation of an  output  file,
  but  not  the creation of a journal file.  If you invoke VAXTPU with
  /NOOUTPUT and then decide you want an output file, use  the  command
  WRITE  FILE  in EVE, or the built-in procedure WRITE_FILE in the EDT
  Keypad Emulator interface before you  end  the  editing  session  to
  write out the contents of a buffer.

 /READ_ONLY
 /NOREAD_ONLY (default)

  Determines whether VAXTPU keeps a journal file and creates an output
  file  from  the  contents  of  the  main buffer.  With /NOREAD_ONLY,
  VAXTPU maintains a journal file and creates an output file from  the
  contents of the main buffer if you modified it.

  Using  the  qualifier  /READ_ONLY  is  like  using   the   qualifier
  /NOJOURNAL  for  the editing session and the qualifier /NOOUTPUT for
  the main buffer.  When  you  specify  /READ_ONLY,  VAXTPU  does  not
  maintain  a  journal file for your editing session, and the NO_WRITE
  attribute is set for the main buffer.   When  a  buffer  is  set  to
  NO_WRITE,  the  contents  of the buffer are not written out when you
  leave VAXTPU.  Both the built-in procedures EXIT and  QUIT  end  the
  editing session without creating a new file from the contents of the
  main buffer (even if you modified it).

  Use  the  qualifier  /READ_ONLY  when  you  are  merely  reading  or
  searching  a  file.   If  you  change your mind and want to save any
  edits you make to the file, use the command WRITE FILE  in  EVE,  or
  the  built-in  procedure  WRITE_FILE  in  the EDT Keypad Emulator to
  write the modified buffer to an external file.   Remember,  however,
  that you do not have a journal file.

 /RECOVER
 /NORECOVER (default)

  Determines whether VAXTPU reads a journal file at the  start  of  an
  editing session.

  When you use the qualifier /RECOVER, VAXTPU  reads  the  appropriate
  journal  file  and  processes whatever commands it contains.  If the
  journal file type is not TJL, or if the file name is not the same as
  the   input   file   name,  you  must  include  both  the  qualifier
  /JOURNAL=journal-file and the qualifier /RECOVER.

  When you recover a session, all files must be in the same  state  as
  they  were at the start of the editing session being recovered.  All
  terminal characteristics must also be in the same state as they were
  at  the  start  of  the  editing  session  being  recovered.   Check
  especially the following terminal characteristics:

       Device_Type
       Edit_mode
       Eightbit
       Page
       Width

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

  Determines whether VAXTPU reads a special initialization  file  that
  is  stored  in binary form.  The default file type for section files
  is  TPU$SECTION.   By  default,  VAXTPU  tries  to  read  the   file
  SYS$LIBRARY:TPUSECINI.TPU$SECTION, the section file that creates the
  EVE editing  interface.   You  can  specify  a  different  file  for
  initialization  purposes  by  defining the logical name TPUSECINI to
  point to a section file other than the default  one.   This  is  the
  preferred  method.   However,  you  can  also  supply  a  full  file
  specification for the qualifier /SECTION.

  The file  used  as  the  value  for  /SECTION=section-file  must  be
  compiled  by  running the source code version of your initialization
  file through VAXTPU and then  using  the  built-in  procedure  SAVE.
  This process converts the file to the proper binary form.

  If  you  specify  /NOSECTION,  VAXTPU  does  not   read   a   binary
  initialization  file.   If  no  section file is read, and no command
  file is read, VAXTPU will not have a user interface and no keys will
  be  defined.   In this state, the only way to exit from VAXTPU is by
  pressing CTRL/Y.

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

  Invokes VAXTPU to edit the file  OLDFILE.TXT.   By  default,  VAXTPU
  uses the section file SYS$LIBRARY:TPUSECINI.TPU$SECTION that creates
  the EVE editing interface.  VAXTPU then tries to  read  the  command
  file TPUINI.TPU in your default directory.  If you do not define the
  logical name TPUINI to point to a user-written command file, and  if
  you  do  not have a file named TPUINI.TPU in your default directory,
  VAXTPU does not read a command file.  If you modify the main  buffer
  and  then use the command EXIT to end the session, the modified file
  is named NEWFILE.TXT.

  2.   $ EDIT/TPU/SECTION=EDTSECINI OLDFILE.TXT

  Invokes VAXTPU with  the  EDT  Keypad  Emulator  editing  interface.
  VAXTPU  makes  a copy of the file OLDFILE.TXT available for editing.
  If you modify the main buffer, when you  use  the  command  EXIT  to
  leave  the editing session, VAXTPU creates a new version of the file
  with a version number one higher than the highest  existing  version
  number for that file.

  3.   $ EDIT/TPU/SECTION=DISK$USER:[SMITH]VT100INI

  Causes VAXTPU to read the section file VT100INI.TPU$SECTION.

  4.   $ EDIT/TPU/RECOVER OLDFILE.TXT

  Invokes VAXTPU with the EVE editing interface  to  recover  from  an
  abnormal  exit  during a previous editing session.  VAXTPU opens the
  file OLDFILE.TXT and then processes the  journal  file  OLDFILE.TJL.
  Once the journal file has been processed, you can resume interactive
  editing.

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

  Invokes VAXTPU with the EVE editing interface  to  recover  from  an
  abnormal  exit  during  a  previous  session.  VAXTPU opens the file
  MEMO.DAT and then processes the journal file SAVE.XXX.