DEC DATATRIEVE Version 7.1 supports a text-file based dictionary in
       addition to Oracle CDD/Repository. This new functionality has
       been added for customers who have to buy Oracle CDD/Repository
       just as a prerequisite for DEC DATATRIEVE. From now on they will
       be able to avoid this dependency because a simple alternative
       storage for DEC DATATRIEVE objects is available.

       DEC DATATRIEVE Version 7.1 is able to work without Oracle
       CDD/Repository while keeping its current functionalities for
       the following commands and statements:

       o  DEFINE

          -  DOMAIN

          -  DATABASE

          -  RECORD (clauses FROM FIELD and FROM GROUP are also
             supported)

          -  PROCEDURE

          -  TABLE

          -  PORT

          -  PLOT

       o  READY domains and databases

       o  Execute (:) procedures

       o  Use of tables in VIA expressions

       o  Use of records in WITH_FORM statements

       o  Use of plots with PLOT statements

       o  DELETE

       o  EDIT with all clauses related to dictionary objects

       o  EXTRACT with all clauses related to dictionary objects

       o  PURGE

       o  REDEFINE

       o  SET

          -  DICTIONARY

          -  PLOTS

       o  SHOW

          -  ALL, DATABASES, DICTIONARIES, DICTIONARY, DOMAINS, PLOTS,
             PROCEDURES, RECORDS, TABLES

          -  path-name

          -  PRIVILEGES for path-name

       o  Directory Services for DECwindows Motif interface and Windows
          Client Dictionary Browsers

       o  ACL control

          -  DEFINEP

          -  DELETEP

          -  SHOWP

             Some customers are interested in associating ACLs to
             definitions that define the access control for the defined
             objects (data) rather than the definition (metadata).

       DEC DATATRIEVE Version 7.1 does not support:

       o  WITH RELATIONSHIPS clauses in DEFINE.

          This is a specific clause for CDO objects. No strict
          dependency relationship is supported for text file
          definitions. This is the same as for DMU objects.

       o  CDD$DATABASE objects.

          They are specific CDO objects.

       o  READY of CODASYL DBMS databases and domains based on them.

          CODASYL DBMS support still requires the use of Oracle
          CDD/Repository. Even if Oracle CODASYL DBMS Version 6.1 no
          longer requires Oracle CDD/Repository, DEC DATATRIEVE depends
          on Oracle CDD/Repository to get DBMS matadata because no
          direct access to DBMS provides the same info.

       o  CDO command.

          This is explicitly targetted to a linked CDO image

       o  General support of fields is not offered (no DEFINE FIELD),
          since it should be restricted to CDO repositories because
          fields as individual elements are not supported by DMU
          dictionaries. However the capability of defining global fields
          (fields that are stored by themselves) is interesting. Oracle
          CDD/Repository users currently can define them via the CDO
          utility and access them via the FROM FIELD clause.