1 TERMS
 A utility to input a command file, presumably login.ful, and output
 two files:  file.COM and file.EXE, which together can define your
 symbols and logical names much faster than a command file alone.

 format:

      TERMS  command-file
2 Directives
 There are 3 special symbols which can be included, as comments, on
 command lines in order to enforce special handling by Terms:

   #COMMAND  will cause a definition to be left in the command file, even
             if it could have been transferred to the executable.

   #EXECUTE  will cause a definition to be transferred to the executable,
             even if it contains apostrophes or does not start with a $.

   #IGNORE   will cause a line to be ignored--neither compiled or left in
             the command file.

 All three may be abbreviated to 4 characters.
 For uses of these directives see Examples.
3 Examples
 $ IF "''F$USER()'" .NES. "[20,40]" THEN EXIT
 $ MYUIC :== "[20,40]"                                         !#COM

      In this case #com was used to preserve order, since the
      if statement cannot be compiled.

 $ DEFINE $X SYS$LOGIN
 ! $X IS DEFINED AS MY HOME DIRECTORY                           #command

      Here #com preserves a valued comment, which would normally
      be discarded.

 $ A :== RUN SYS$LOGIN:LOGIN.EXE                               !#ign

      This line will appear in the original command file, but not
      in the new file or in the executable which it runs.

 ! HERE :== "'F$LOG(""SYS$DISK"")''F$DIR()'"                      #EXEC

      This line would not be interpreted correctly in a command
      procedure, because we do not want the symbols translated.
      However, it is valuable when done in the executable.
2 Example
 Here is an example command file, called LOGIN.FUL:

 $ D :== DIR/SIZE=ALL/PROT
 $ DEFINE HOME _DRC1:[SIMON]
 $ MCR ULIB:[MISC]MOVE.EXE /DEFINE
 ! this defines all the move commands.
 $ CD :== MOVE/CHECK/FAST
 $ WRITE SYS$OUTPUT " Welcome to my account! "

 When run it through Terms, and now we have the original LOGIN.FUL,
 and also LOGIN.EXE and LOGIN.COM, which looks like this:

 $ RUN _DRC1:[SIMON]LOGIN.EXE;
 $ MCR ULIB:[MISC]MOVE.EXE /DEFINE
 $ WRITE SYS$OUTPUT " Welcome to my account! "
2 Location
 Note that the first line of the new command file will run the executable
 in the directory where the file was when Terms was originally used.

 You must alter this line with an editor if you move the files.

 Also note that you may move this line to anywhere you desire in the
 file, to change the order in which things are done.  It can even be
 nested inside an if-clause.
2 Restrictions
 Only the following will be transferred to the executable:
    1) global symbol definitions and logical name assignments
    2) lines beginning with "$" or containing the directive "#EXE"
    3) lines not containing the directives "#COM" or "#IGN"
 The last two allow the user to force items to remain in the com file, when
 needed to preserve order.

 Note that Terms does not enforce DCL restrictions on global symbols, in
 that a symbol may contain (and begin with) any character; even lines like
      $ 1 2 3 == "write sys$output ""1 2 3"""
 will be translated and defined exactly as they stand.  However, DCL might
 give you trouble when trying to reference them.

 Since the command file would get an error on the above example, it is
 best to comment it out and use the #EXE directive:
      ! 1 2 3 == "write sys$output ""1 2 3"""  !#exe
 so that it will be compiled, but the original command file may still
 be used.
2 Bugs
 There are several known bugs:
      1. very long symbol definitions can cause fatal errors.
      2. you cannot define numeric symbols, they are treated as strings.
      3. it does not always correctly trim trailing blanks.

2 Qualifiers
/LIST
 A diagnostic tool which will display each command and how it is parsed.
