Additional information available:

/ACL/EDT/FDL/TPU

 Invokes the ACL editor.

 Format
  EDIT/ACL file-spec

Additional information available:

ParametersQualifiers

 object-name
  Name of object whose access control list is being edited. The
  file must be a disk file on a Files-11 Structure Level 2 formatted
  volume.

 /ACL
  Indicates invocation of the ACL editor.  This qualifier is required.
 /JOURNAL[=file-spec] (default)
  /NOJOURNAL
  Specifies whether or not the ACL editor keeps a journal file during an
  editing session and the specification of that journal file. File-spec
  defaults to the name of the file being edited and a file type of JOU.
 /KEEP=(option,...)
  Specifies that the ACL editor save the journal file(s) if the editing
  session terminates normally. (If the editing session terminates
  abnormally, the journal files are saved regardless of the /KEEP
  qualifier.) Possible options are:

  +---------+----------------------------------------------------+
  | JOURNAL | Save the journal file for the current session      |
  +---------+----------------------------------------------------+
  | RECOVER | Save the journal file used to restore the access   |
  |         | control list before beginning the current session  |
  +---------+----------------------------------------------------+
 /MODE=option
  Specifies whether or not the ACL editor prompts for field values.
  Specify option as PROMPT (default) or NOPROMPT.
 /OBJECT=type
  Specifies the type of object whose ACL is being edited.  Possible types
  are:

  +-----------------------+----------------------------------------+
  | FILE                  | Specifies that the object is a file    |
  |                       | (the default)                          |
  +-----------------------+----------------------------------------+
  | DEVICE                | Specifies that the object is a device  |
  +-----------------------+----------------------------------------+
  | GROUP_GLOBAL_SECTION  | Specifies that the object is a group   |
  |                       | global section                         |
  +-----------------------+----------------------------------------+
  | LOGICAL_NAME_TABLE    | Specifies that the object is a logical |
  |                       | name table                             |
  +-----------------------+----------------------------------------+
  | SYSTEM_GLOBAL_SECTION | Specifies that the object is a system  |
  |                       | global section                         |
  +-----------------------+----------------------------------------+

 /RECOVER[=file-spec]
  /NORECOVER (default)
  Specifies whether or not a journal file is executed before the editing
  session begins. File-spec defaults to the name of the file being
  edited and a file type of JOU.

Invokes the EDT editor.

Format
 EDIT [/qualifiers] file spec [/qualifiers]

Additional information available:

ParameterQualifiers

file-spec
 Specification of file being edited.

Additional information available:

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

 /NOCOMMAND
 Specifies whether or not EDT executes a start-up command file before
 the editing session begins and the specification of that command file.
 The default is /COMMAND=[default-directory]EDTINI.EDT.

 /NOCREATE
 Controls whether EDT creates a new file when the specified input file
 is not found. The default is /CREATE.

 /NOJOURNAL
 Specifies whether or not EDT keeps a journal file during an editing
 session and the specification of that journal file. The default is
 /JOURNAL=file-name.JOU, where file-name is the name of the file being
 edited.

 /NOOUTPUT
 Specifies whether or not EDT creates an output file during the editing
 session and the specification of that file. The default is
 /OUTPUT=input file specification, where the version number becomes the
 highest for that file specification.

 /NOREAD_ONLY
 Specifies whether or not both an output file and a journal file are
 created. The default is /NOREAD_ONLY.

 /NORECOVER
 Specifies whether or not a journal file is executed before the editing
 session begins. If the name of the journal file is different from that
 of the input file, you must specify it with the /JOURNAL qualifier.
 The default is /NORECOVER.

Invokes the FDL (File Definition Language) editor to create
and/or modify FDL files.  See Section FDL for more
information on the FDL editor.

Format
 EDIT/FDL file-spec

 Requires the Program Development Tools Option.

Additional information available:

ParameterQualifiers

file-spec
 Specification of the FDL file to be created, modified, or
 optimized; the default file type is FDL.  If the file does not
 exist, EDIT/FDL displays a message indicating that the file
 will be created and then creates it.

Additional information available:

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

 Specifies the FDL analysis file (generated by ANALYZE/RMS/FDL)
 to be used in the optimize script;  the default file type is FDL.

 Creates the FDL file specified as the command parameter.  EDIT/FDL
 does not attempt to open the specified file before creating it and
 does not issue the message stating that the file will be created.

 Specifies the type of graph to be displayed.  Keywords are:

 +--------+---------------------------------------------------------+
 | ADD    | Bucket size versus additional record count versus index |
 |        | depth                                                   |
 +--------+---------------------------------------------------------+
 | FILL   | Bucket size versus load fill percent versus index depth |
 +--------+---------------------------------------------------------+
 | INIT   | Bucket size versus initial load record count versus     |
 |        | index depth                                             |
 +--------+---------------------------------------------------------+
 | KEY    | Bucket size versus key length versus index depth        |
 +--------+---------------------------------------------------------+
 | LINE   | Default;  bucket size versus index depth                |
 +--------+---------------------------------------------------------+
 | RECORD | Bucket size versus record size versus index depth       |
 +--------+---------------------------------------------------------+

 Allows you to choose either smaller buffers or flatter files.
 Keywords are:

 +-----------------+---------------------------------------------------+
 | FLATTER_FILES   | Default.  Generally increases bucket size.        |
 |                 | The bucket size controls the number of levels     |
 |                 | in the index structure.  If a larger bucket size  |
 |                 | eliminates one level, 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.                                 |
 +-----------------+---------------------------------------------------+

 Divides an indexed file into a specified number (n) of areas;
 the default is 3 areas.

 Causes EDIT/FDL to execute the optimize script without a terminal
 dialog.  Requires that you use the /ANALYSIS qualifier to specify
 an FDL analysis file previously created using the
 ANALYZE/RMS_FILE/FDL command.

 Specifies the number of keys in your indexed file.  You can
 define up to 255 keys; the default is 1 key.

 Specifies an output file.  The default is the file name of the
 input file with a version number one higher than that of the
 input file.  The default file type is FDL.

 Specifies the level of prompting to be used during the interactive
 editing session.  Keywords are:

 +-------+----------------------------------------------------------+
 | BRIEF | Lists the possible responses                             |
 +-------+----------------------------------------------------------+
 | FULL  | Default (unless your terminal is hard-copy or operating  |
 |       | at a speed of less than 2400 baud); lists the possible   |
 |       | responses, each followed by a brief explanation          |
 +-------+----------------------------------------------------------+

 Selects mode of response to script questions.  Keywords are:

 +-----------+--------------------------------------------------------+
 | AUTOMATIC | Where a script question has a default answer, EDIT/FDL |
 |           | responds for you using that default.                   |
 +-----------+--------------------------------------------------------+
 | MANUAL    | Default.  EDIT/FDL allows you to respond to all script |
 |           | questions.                                             |
 +-----------+--------------------------------------------------------+

 /NOSCRIPT (default)
 Selects a script, or sequence of questions, for EDIT/FDL to ask.
 Script titles are:

 +------------+--------------------------------------------------------+
 | ADD_KEY    | Model or add to the attributes of a new index.         |
 +------------+--------------------------------------------------------+
 | DELETE_KEY | Remove attributes from the highest index of your file. |
 +------------+--------------------------------------------------------+
 | INDEXED    | Create an FDL file that describes an indexed data      |
 |            | file.  EDIT/FDL supplies values for certain            |
 |            | attributes.                                            |
 +------------+--------------------------------------------------------+
 | OPTIMIZE   | Create an FDL file that can be used to tune an         |
 |            | existing indexed file.  Requires that you use the      |
 |            | /ANALYSIS qualifier to specify an FDL analysis file    |
 |            | previously created using the ANALYZE/RMS_FILE/FDL      |
 |            | command.                                               |
 +------------+--------------------------------------------------------+
 | RELATIVE   | Create an FDL file that describes a relative data      |
 |            | file.  EDIT/FDL supplies values for certain            |
 |            | attributes.                                            |
 +------------+--------------------------------------------------------+
 | SEQUENTIAL | Create an FDL file that describes a sequential data    |
 |            | file.  EDIT/FDL supplies values for certain            |
 |            | attributes.                                            |
 +------------+--------------------------------------------------------+
 | TOUCHUP    | Modify the attributes of an existing index.            |
 +------------+--------------------------------------------------------+

Invokes the VAX Text Processing Utility (VAXTPU) with the Extensible VAX
Editor (EVE) interface.

Format
  $ EDIT/TPU [file-spec]

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

Additional information available:

SummaryParameterQualifiers

 VAXTPU is a text processing utility, two major features of which are
 high performance and extensibility.  The screen oriented text processing
 features of VAXTPU are targeted to the VT200 and VT100 families of
 terminals, but they can be used on other ANSI CRTs.  VAXTPU can also be
 used to do batch mode text processing.

 EVE is the default interface when you invoke VAXTPU. It has features such
 as multiple windows, multiple processes, and learn sequences.

 The VAXTPU EDT Keypad Emulator interface provides all of the functions
 of the EDT keypad and binds these functions to the same keys that EDT
 uses.  It also has a limited set of EDT line mode commands.

 For information on EVE and the EDT Keypad Emulator, see the MicroVMS
 User's Manual.  There is on-line HELP about VAXTPU and the interface
 you are using from within the interface.

file-spec
 Specification of the file being edited.  If you do not supply a file
 specification, VAXTPU prompts you for one when you leave the utility
 if you have modified any buffers.

Additional information available:

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

 /NOCOMMAND
 Determines whether VAXTPU executes a command file before the editing
 session begins.  File-spec defaults to TPUINI.TPU in your default
 directory.  You can override the default by defining the logical name
 TPUINI to point to a different file, or by specifying a different
 file-spec after /COMMAND.

 /NOCREATE
 Determines whether VAXTPU provides a buffer in which to create a new
 file when the specified input file is not found.

 /NODISPLAY
 Determines whether a VAXTPU session is run from a supported terminal
 and uses terminal functions such as the screen display and keyboard.
 By default, your VAXTPU session is run with the screen management file,
 SYS$SHARE: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.

 /NOJOURNAL
 Determines whether VAXTPU keeps a journal file during an editing session.
 The default is /JOURNAL=filename.TJL, where filename is the name of the
 file being edited.

 /NOOUTPUT
 Determines whether VAXTPU creates an output file at the end of an
 editing session.  The interface that is layered on VAXTPU is responsible
 for processing this qualifier.  The default is /OUTPUT=input-file-spec,
 where the file name and type remain unchanged and the version number is
 one higher than the highest existing version of the input file.

 /NOREAD_ONLY (default)
 Determines whether both an output file and a journal file are created.
 With the default, /NOREAD_ONLY, VAXTPU maintains a journal file in case
 an interruption occurs, and if you have modified the main buffer,
 creates an output file when the EXIT command is issued.  Use the
 /READ_ONLY qualifier when you want the main buffer set to NO_WRITE; for
 example, when you want to look at a file and do not intend to make any
 changes to it.  When you use the /READ_ONLY qualifier, enter the QUIT
 command to leave VAXTPU.  You can use the WRITE FILE in EVE, or the
 WRITE_FILE built-in procedure in the EDT Keypad Emulator to write out a
 buffer that is set to NO_WRITE.

 /NORECOVER (default)
 Determines whether a journal file is executed before the editing
 session begins.  If the name of the journal file is different from
 that of the input file, you must use both /RECOVER and /JOURNAL, and
 must specify the name of the journal file with the /JOURNAL qualifier.

 /NOSECTION
 Determines whether VAXTPU reads a initialization file that is stored
 in binary form. File-spec defaults to SYS$LIBRARY:TPUSECINI.TPU$SECTION,
 the section file that creates the EVE interface. You can specify a
 different file for initialization purposes by defining the logical name
 TPUSECINI to point to a different section file.  This is the preferred
 method.  However, you can also supply a full file specification for
 /SECTION.