EXPORT SCHEMA -+-> AUTHORIZATION auth-id -+-+
                +-> FILENAME file-spec ----+ |
                +-> PATHNAME path-name ----+ |
 +-------------------------------------------+
 +-> INTO file-spec -+--------------------------+--> ;
                     +- WITH -+-> EXTENSIONS ---+
                              +-> NOEXTENSIONS -+
                              +-> DATA ---------+
                              +-> NO DATA ------+

Additional information available:

AUTHORIZATIONFILENAMEPATHNAMEWITH_EXTENSIONSWITH_DATA

INTO file-specMore Information

 Specifies the source database files to be compressed and written
 to an .RBR file.

 AUTHORIZATION specifies the authorization identifier of an
 already-declared schema.  If the schema you want to export is
 already declared, specifying AUTHORIZATION avoids the overhead
 of a second attachment to the schema and the locking that
 attachment entails.

 Specifies the source database files to be compressed and written
 to an .RBR file.

 FILENAME and PATHNAME both identify the database root file
 associated with the schema.  If you specify a data dictionary
 path name, the pathname indirectly specifies the root file.
 EXPORT does not change any definitions in the data dictionary,
 so there is no difference in the effect of the PATHNAME and
 FILENAME arguments.

 Specifies the name for the .RBR file EXPORT creates.
 Optionally, the file specification can include a device and
 directory specification.

 Makes a copy of a database in an intermediate, compressed form.
 Use the IMPORT statement to rebuild an Rdb/VMS database from the
 compressed .RBR file created by EXPORT.

 You use EXPORT with IMPORT to make changes to Rdb/VMS databases
 that cannot be made any other way.  EXPORT unloads a database to
 an .RBR file.  IMPORT recreates the database with changes not
 allowed through ALTER statements:

  o  Convert a single-file database to multifile and vice versa

  o  Create an empty target database that uses the same data
     definitions as a source database by copying the metadata,
     but not the data, from the source to the target

  o  Change root file parameters you cannot change with ALTER
     SCHEMA:

  o  Change storage area parameters you cannot change with ALTER
     SCHEMA

  o  Reload tables with existing rows to take advantage of
     newly-created hashed indexes

  o  Reload tables to take advantage of new or changed storage
     maps

  o  Convert a database from another DSRI-compliant
     implementation to an Rdb/VMS database.  For instance, the
     Rdb/ELN EBRP utility creates an .RBR file you can use with
     the IMPORT statement to create an Rdb/VMS database.

 Specifies the source database files to be compressed and written
 to an .RBR file.

 FILENAME and PATHNAME both identify the database root file
 associated with the schema.  If you specify a data dictionary
 path name, the pathname indirectly specifies the root file.
 EXPORT does not change any definitions in the data dictionary,
 so there is no difference in the effect of the PATHNAME and
 FILENAME arguments.

 Specifies whether the .RBR file created by the EXPORT statement
 includes extensions that are compatible only with Rdb/VMS
 Version 3.0 or later database systems.  WITH EXTENSIONS is the
 default.

 The only time you need to specify WITH NOEXTENSIONS is if the
 database system through which you will rebuild the .RBR file
 into a database is:

  o  Rdb/VMS Version 2.3 or earlier

  o  Any verson of Rdb/ELN


 The WITH NOEXTENSIONS option is not compatible with CDD/Plus
 dictionary databases (CDD$DATABASE.RDB).  If you attempt to
 export a CDD$DATABASE.RDB database, SQL issues an error message
 stating that the NOEXTENSIONS option is not valid for CDD/Plus
 dictionary databases.

 Specifies whether the .RBR file includes the data and metadata
 contained in the database (WITH DATA), or the metadata only
 (WITH NO DATA).  The default is WITH DATA.

 When you specify the WITH NO DATA option, the EXPORT statement
 copies metadata from the source database to an .RBR file.  Use
 the IMPORT statement to generate an empty database whose
 metadata is identical to that of the source database.

 The WITH NO DATA option is not compatible with CDD/Plus
 dictionary databases (CDD$DATABASE.RDB).  If you attempt to
 export a CDD$DATABASE.RDB database, SQL issues an error message
 stating that the NO DATA option is not valid for CDD/Plus
 dictionary databases.