- BLACKBOX      - more detailed information about fatal errors    [ March 1987 ]

  If a fatal error occurs, DBAG keeps some information that can be usefull to
  reproduce and fix the error in a  "black box" file in the user's disk space,
  named "DBAG.BKB".
- EDITING       - fast call to VMS editors EDT and TPU            [ March 1987 ]

  The new commands EDT and TPU implement  direct calls to the VMS editors EDT
  and TPU. Of course, the general DBAG command "vms edit a.b" or "vms tpu a.b"
  can be used as well to call the editors,  but the new commands "edt a.b" or
  "tpu a.b" do it faster.
- CRIPTING      - information in a data base can be cripted or not[ March 1987 ]

  Now, when defining a data base structure (CREATE command),  you can specify
  that the information is to be stored cripted, eg unreadable, or cripted, eg
  ascii. The data bases created before March 1987 are cripted.

  The  command "MODIFY STRUCTURE" can be used to  change  the "recording mode"
  of a data base. Note that one data base is handled  more  efficiently if it
  is NOT cripted.
- DELETED       - the data base records can't be deleted/recalled  [ June 1987 ]

  You can't delete/recall records from a data base anymore; the corresponding
  commands DELETE/RECALL have been discontinued.  For that reason,  searching
  on  a  data  base  (display/search  commands)  is  now  handled  much  more
  efficiently.
- COMMAND FILES - extension .BAT accepted for command files   [ September 1987 ]

  Two standard extensions are now accepted for the DBAG command files: ".CMD"
  and ".BAT".
- KILL COMMAND  - use KILL command to suppress records        [ September 1987 ]

  A new command is available (KILL) to suppress records from a data base.
  Note that the contents of  such records ARE LOST  FOREVER.  Its record
  numbers will be normally re-used when  "appending"  new records to the
  base, unless you have decided not to re-use them.   This option can be
  set when creating a data base structure (CREATE command) and  modified
  using the MODIFY STRUCTURE command.
- DELIMITED     - DELIMITED keyword has been suppressed         [ October 1987 ]

  The keyword DELIMITED has been discarded. The default keyword for standard
  ascii files is now  "DBAG",  and the default extension ".DBA",  instead of
  "DELIMITED" and ".DEL".
- DISPLAY       - display any field of other data base          [ October 1987 ]

  For a field whose type is "other data base" ( db$ ), it's now possible to
  specify the field you want to see of the o.d.b.  Use the CREATE or MODIFY
  STRUCTURE command to set or change it at will.  

  If you want to  see  more than one field at a time, define as many fields
  "o.d.b" as you need.
- EMPTY FIELDS  - empty fields can be searched                 [ November 1987 ]

  Use the keyword EMPTY to select records with empty fields. Examples: "EDIT
  ALL FOR %2 = EMPTY" to edit all records with field 2 empty;  "DISPLAY  ALL
  FOR .NOT. %2 = EMPTY" to display all the records with field 2 non-empty.
- RECALL or UP  - get a command from the command buffer        [ November 1987 ]

  The RECALL command (same as UP command) allows you to search the command
  buffer for whatever you type.  Example: "RECALL search datab cars" looks
  for a previous command starting by "search datab cars".
- UNLOAD/RELOAD - fast data base unloading/reloading              [ March 1988 ]

  Instead of the APPEND command, you can use the UNLOAD/RELOAD commands  to
  unload or reload ALL records of a data base to/from a disk file (the file
  format is SDF).
- NOCHECK       - don't validate input data read from file        [ March 1988 ]

  To speed up the APPEND, RELOAD or REPLACE commands, you can include the
  NOCHECK option:  the data read from file will NOT be checked  ( at your
  own risk !).
- ERRORSTOP     - stop on errors (append/reload commands)         [ March 1988 ]

  DBAG will stop on errors when appending, reloading or replacing data from
  a disk file and ask user to confirm.  Issue the command SET ERRORSTOP OFF
  if you don't want to stop on errors.
- PROTECTIONS   - protect data base fields                        [ March 1988 ]

  Field protection capability has been added to the DBAG system. For any data
  base, you can use the DBPROT program to create a protection file. Then,  an
  entry into that protection file should be added for any user name accessing
  the data base. The user profile entry establish, in a field basis, the type
  of access allowed: "read only", "read/write" or "no access".
  The protection file is named "base.PPN".
- BUGS          - known bugs                                      [ March 1988 ]

  * FOR (and JFOR) expressions may be evaluated incorrectly if # (record#)
    appears within a multilple logical condition, e.g. "DISPLAY ALL FOR
    # > 103 .OR. # <= 10".