EDIT ──┬────────────┬──>
        ├─> number ──┤
        └─> typebox (*) ───────┘

 Calls an editor that lets you modify the SQL statements you have
 issued within a terminal session.  You can use the editor in the
 normal fashion to modify your previous interactive SQL statements,
 construct your next statement or group of statements, or include a
 file with other statements.  SQL executes the statements in the
 editing buffer when you exit.

 SQL supports three editors:

  o  EDT, which is the default SQL editor

  o  The VAX Text Processing Utility (VAXTPU) editors, such as EVE.
     See the subtopic SQLEDIT for more information.

  o  The VAX Language-Sensitive Editor (LSE), which is based on VAXTPU
     and provides templates that guide you in entering syntactically
     correct statements.  See the subtopics SQLEDIT and LSE for more
     information.

Additional information available:

SQLEDITLSE

More

 The number argument to the EDIT statement specifies the number of
 previous command lines you want to edit.  The default is 1.

 The asterisk argument specifies that SQL put the last n command lines
 in the editing buffer, where n is determined by the SET EDIT KEEP
 statement.  The default is 20.

 You do not need to do anything to specify EDT as the editor to use
 within interactive SQL.  To use VAXTPU, it must be installed on your
 system, and you must define the logical name SQL$EDIT.  To use LSE,
 it must be installed on your system, and you must define the logical
 names SQL$EDIT and LSE$ENVIRONMENT:

 $ ! To specify VAXTPU as your editor in interactive SQL:
 $ DEFINE SQL$EDIT TPU
 $ !
 $ ! To specify LSE as your editor in interactive SQL:
 $ DEFINE SQL$EDIT LSE
 $ DEFINE LSE$ENVIRONMENT -
 _$ SYS$COMMON:[SYSLIB]LSE$SYSTEM_ENVIRONMENT.ENV

 Then, when you type EDIT in an SQL session, SQL calls the editor
 specified by the SQL$EDIT logical name.  If SQL$EDIT is not defined,
 or is defined to be something other than TPU or LSE, then SQL invokes
 the EDT editor when you issue the EDIT statement.  If SQL cannot find
 the VAXTPU or LSE shareable image, it invokes EDT.

 SQL provides two LSE templates, one for interactive SQL and one for
 module language.  You can invoke the interactive templates from
 within SQL or from DCL level.

 To invoke the interactive templates from within SQL, you must:


  o  Use the DCL DEFINE command to define LSE as the chosen editor:

     $ DEFINE SQL$EDIT LSE

  o  Use the DCL DEFINE command to define the LSE environment:

     $ DEFINE LSE$ENVIRONMENT -
     _$ SYS$COMMON:[SYSLIB]LSE$SYSTEM_ENVIRONMENT.ENV

  o  Invoke SQL and enter the EDIT statement.  This automatically
     invokes the SQL interactive LSE templates.


 To invoke the the SQL templates at DCL level, type LSE followed by
 the name of the file you want to edit.  The file type determines the
 set of templates that LSE uses.  To use the interactive SQL
 templates, specify a file type of SQL; to use the SQL module language
 templates, specify a file type of SQLMOD.  For example, you can type
 the following commands:

 $ ! To invoke the LSE templates for interactive SQL at DCL level:
 $ LSE SAMPLE.SQL
 $ ! To invoke the LSE templates for SQL module language:
 $ LSE SAMPLE.SQLMOD

 Note that the module language templates can only be invoked at DCL
 level.